[fuel-menu] Force save settings despite errors
Bug #1579053 reported by
Bartłomiej Piotrowski
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Confirmed
|
Wishlist
|
Fuel Sustaining | ||
Bug Description
Fuel Menu ships with many "sanity" checks responsible for preventing regular users from shooting himself in the foot after they deployed OpenStack. Evaluation of these conditionals is determined by function get_deployment_
As a deployment engineer, I might want to run fuel-menu manually after Fuel installation to tweak settings before I start OpenStack deployment. Fuel Menu should allow me to enforce new settings despite errors by either "I know what I'm doing" button or super cow powers command line flag.
| Changed in fuel: | |
| assignee: | nobody → Fuel Sustaining (fuel-sustaining-team) |
| importance: | Undecided → Medium |
| status: | New → Confirmed |
| tags: | added: area-python |
| tags: | added: customer-found |
Revision history for this message
| Maksim Malchuk (mmalchuk) wrote | #1 |
| tags: | added: module-fuelmenu |
| Changed in fuel: | |
| importance: | Medium → Wishlist |
To post a comment you must log in.
This is actually not a bug but feature.