If you don't choose any new role for added node after deploy, button "Deploy Changes" becomes enabled
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Anastasia Palkina |
Bug Description
"build_id": "2014-10-
"ostf_sha": "de177931b53fbe
"build_number": "31",
"auth_required": true,
"api": "1.0",
"nailgun_sha": "33654affeeaca0
"production": "docker",
"fuelmain_sha": "598122bd61175a
"astute_sha": "6a11a7c481d116
"feature_groups": ["mirantis"],
"release": "6.0",
"release_versions": {"2014.2-6.0": {"VERSION": {"build_id": "2014-10-
"fuellib_sha": "598f2b7212f686
1. Create any environment
2. Start deployment. It should be successful
3. Button "Deploy Changes" is disabled. It is right
3. Add new node with role 'Compute'
4. Check this new node and click button "Edit role"
5. Uncheck checkbox 'Compute'. Node becomes 'Unallocated'
6. Click button "Apply Changes"
7. Button "Deploy Changes" becomes enable. But should be disable because there are no new nodes in environment
Changed in fuel: | |
importance: | Undecided → Medium |
Can't reproduce the issue. Seems like it was fixed in related requests. Nastya, could you please verify this ticket?