"no changes to deploy" message when deploy "Changed environment configuration"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Committed
|
High
|
Bulat Gaifullin | ||
Mitaka |
Fix Released
|
High
|
Bulat Gaifullin | ||
Newton |
Fix Committed
|
High
|
Bulat Gaifullin |
Bug Description
Liberty on Ubuntu 14.04 liberty-9.0
fuel-9.
Steps to reproduce:
1 Open Fuel UI https://<master_ip>:8443
2 Enter username: admin and password: admin to the appropriate fields
3 Click “Log In” button
4 Click “Connect Later” button
5 Click “New OpenStack Environment” block
6 Click "Next" button without changing default settings and at the end click "Create" button
7 New environment should open on "Dashboard" tab
8 Add nodes: 1 controller nodes and 1 compute nodes
9 Click "Deploy changes", and push "deploy" button on warning pop-up. Wait for deploy finished
10 Click "Settings" tab, choose "OpenStack Services" section.
11 Click "Install Sahara" check box
13 Go to Dashboard. Click "Deploy changes"
14 Click "Deploy"
Expected results:
Successfully install "Sahara" component
Actual result:
No installation happened, pop up message "No changes to deploy" showed.
Changed in fuel: | |
status: | New → Confirmed |
importance: | Undecided → High |
milestone: | none → 9.0 |
tags: |
added: area-python removed: area-ui |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
tags: | added: team-enhancements |
Changed in fuel: | |
assignee: | Fuel Python Team (fuel-python) → Bulat Gaifullin (bgaifullin) |
Changed in fuel: | |
assignee: | Roman Prykhodchenko (romcheg) → Bulat Gaifullin (bgaifullin) |
Changed in fuel: | |
assignee: | Bulat Gaifullin (bgaifullin) → Vladimir Kuklin (vkuklin) |
Changed in fuel: | |
assignee: | Vladimir Kuklin (vkuklin) → Bulat Gaifullin (bgaifullin) |
Changed in fuel: | |
assignee: | Bulat Gaifullin (bgaifullin) → Vladimir Kuklin (vkuklin) |
Changed in fuel: | |
assignee: | Vladimir Kuklin (vkuklin) → Bulat Gaifullin (bgaifullin) |
unfortunately, I can't attach the diagnostic snapshot, for this bug. Got "timeout error" each time I try post it.