rabbitmq cluster goes ACTIVE but is unusable after initial boot
Bug #1453351 reported by
Min Pae
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cue |
Fix Committed
|
Critical
|
Unassigned | ||
Bug Description
The rabbitmq cluster, when booted, starts up rabbitmq services to the point where the cluster goes ACTIVE, but the cluster becomes unusable after some time (~3 minutes in the cluster where this was observed, but not quantified beyond that). It seems like the service is being reset and restarted several times beyond the initial time it is "supposed" to be reset/restarted. From observation the os-collect-config service is still running even though it is being disabled in the post-configure step. This would explain the repeated reset/restarts observed in the rabbitmq logs.
| Changed in cue: | |
| status: | New → Fix Committed |
| status: | Fix Committed → New |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cue (master) | #1 |
| Changed in cue: | |
| status: | New → Fix Committed |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit f91bc8965b50c21
Author: Min Pae <email address hidden>
Date: Fri May 8 21:42:57 2015 -0700
configure and start rabbitmq VMs from userdata
Configuring and starting rabbitmq with os-apply-config and
os-
regularly reset and restarted. We want rabbitmq to be reset and started
once at initial boot and not past that. Moving the config generation
and service startup logic to the userdata script that is supplied by Cue
at VM creation time.
Closes-Bug: 1453351
Change-Id: I2971c196e0cc10