Unpublishing Fuel created m1.flavors breaks Openstack lifecycle management
Bug #1658685 reported by
Andres Toomsalu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Sustaining | ||
| Mitaka |
Invalid
|
Medium
|
Fuel Sustaining | ||
| Newton |
Invalid
|
Medium
|
Fuel Sustaining | ||
Bug Description
We needed to unpublish Fuel created m1.* generation flavors (in order to hide them from customers) - and we achieved this by setting their access to private (admin tenant).
Next run of configuration changes with Fuel (post-install Openstack config changes) failed, leaving CTRL node(s) in error state - as it seems CTRL nodes puppet recipes depend directly from m1.flavors being public.
Expected result for us would be that Fuel generated m1.flavors do not have hard dependency to be public (as it is a bit wrong to expect that these flavors suite for everybody).
| Changed in fuel: | |
| milestone: | none → 9.3 |
| assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
| importance: | Undecided → Medium |
| Changed in fuel: | |
| milestone: | 9.x-updates → 11.0 |
| status: | New → Confirmed |
| tags: | added: area-library |
Revision history for this message
| Oleksiy Molchanov (omolchanov) wrote | #1 |
| Changed in fuel: | |
| status: | Confirmed → Incomplete |
| Changed in fuel: | |
| status: | Incomplete → Invalid |
To post a comment you must log in.
Please attach diagnostic snapshot, I was unable to reproduce.