Taskmanager writes guestagent conf to wrong place
Bug #1309030 reported by
Greg Lucas
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack DBaaS (Trove) |
Fix Released
|
Wishlist
|
Duk Loi |
Bug Description
The guest images produced by kick-start are putting the trove-guestagen
However, the task manager writes to /etc/trove-
Per hub_cap's comments here: https:/
Changed in trove-integration: | |
assignee: | nobody → Greg Lucas (glucas-q) |
status: | New → In Progress |
Changed in trove-integration: | |
importance: | Undecided → Medium |
milestone: | none → juno-1 |
summary: |
- Kick-start images put guestagent conf in wrong place + Taskmanager writes guestagent conf to wrong place |
Changed in trove: | |
milestone: | none → juno-3 |
Changed in trove: | |
milestone: | juno-3 → juno-rc1 |
Changed in trove: | |
assignee: | Greg Lucas (glucas-q) → Duk Loi (duktesora) |
Changed in trove: | |
assignee: | Duk Loi (duktesora) → Denis M. (dmakogon) |
Changed in trove: | |
milestone: | kilo-1 → kilo-2 |
Changed in trove: | |
assignee: | Denis M. (dmakogon) → Duk Loi (duktesora) |
Changed in trove: | |
milestone: | kilo-2 → kilo-3 |
Changed in trove: | |
status: | Fix Committed → Fix Released |
Changed in trove: | |
milestone: | kilo-3 → 2015.1.0 |
To post a comment you must log in.
Arguably, the task manager should be writing to '/etc/trove/ trove-guestagen t.conf' instead.
Either way, we should be consistent between what the task manager does during create and how trove-integration sets up guest images.