User cannot change settings after unsuccessful deployment
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Vladimir Kuklin | ||
Mitaka |
Fix Released
|
High
|
Vladimir Kuklin |
Bug Description
If deployment has failed user cannot change cluster settings(all settings are locked on UI).
Scenario:
1. create a cluster with 1 Controller for example
2. do some changes for deployment failure (I used incorrect CIDR for public net)
Expected results:
user can change cluster setting on UI after deployment failure
Actual result:
all settings are locked on UI after deployment failure
Version:
cat /etc/fuel_build_id:
152
cat /etc/fuel_
152
cat /etc/fuel_release:
9.0
cat /etc/fuel_
mitaka-9.0
rpm -qa | egrep 'fuel|astute|
fuel-misc-
python-
fuel-9.
fuel-provision
fuelmenu-
fuel-ui-
fuel-migrate-
fuel-ostf-
shotgun-
python-
fuel-bootstrap
fuel-nailgun-
fuel-setup-
rubygem-
fuel-mirror-
fuel-openstack
fuel-notify-
fuel-release-
nailgun-
network-
fuel-utils-
fuel-library9.
fuel-agent-
Changed in fuel: | |
milestone: | none → 9.0 |
assignee: | nobody → Fuel Python Team (fuel-python) |
importance: | Undecided → High |
tags: | added: area-python |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Vladimir Kuklin (vkuklin) |
Changed in fuel: | |
status: | Fix Committed → In Progress |
no longer affects: | fuel/newton |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
Changed in fuel: | |
status: | In Progress → Fix Committed |
(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:
steps to reproduce
For more detailed information on the contents of each of the listed sections see https:/ /wiki.openstack .org/wiki/ Fuel/How_ to_contribute# Here_is_ how_you_ file_a_ bug