rabbitmq instance is not writing metadata at boot
Bug #1453266 reported by
Min Pae
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cue |
Fix Committed
|
Medium
|
Unassigned | ||
Bug Description
Metadata for os-apply-config is supposed to be populated by a userdata supplied by Cue upon VM boot. The directory that the userdata script is trying to drop metadata in to seems to not exist at boot time, resulting in the entire process to fail and os-apply-config never happening.
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to cue (master) | #1 |
| Changed in cue: | |
| status: | New → Fix Committed |
| Changed in cue: | |
| importance: | Undecided → Medium |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit ed020e4e443d7be
Author: Min Pae <email address hidden>
Date: Fri May 8 13:23:36 2015 -0700
fix rabbitmq userdata template to create metadata
A metadata file is created by the install_rabbit.sh script, which is
being supplied by userdata properly. However, the directory that the
script tries to populate does not seem to exist. Fixing script template
to create the entire directory hierarchy rather than just the specific
directory.
Change-Id: I3160d0a1dc2902
Closes-Bug: 1453266