Provisiong is still running after stopping

Bug #1629301 reported by ElenaRossokhina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Vladimir Sharshov

Bug Description

Detailed bug description:
I configured cluster and stopped deployment as described below. Process was stoped successfully (main_tab.png), but nodes seem to be under provisioning. After more then 30 minutes I see progress bar on the nodes tab (nodes_tab.png)

Steps to reproduce:
1. Create new environment
2. Choose Neutron, VLAN
3. Choose Ceph for volumes
4. Choose Murano
5. Add 3 controller
6. Add 1 compute
7. Add 3 ceph
8. Verify networks
9. Start deployment
10. Stop deployment during provisioning
11. Wait until nodes become 'Pending addition' (FAIL)
12. Deploy the environment again
13. Verify networks
14. Run OSTF tests

Expected results:
Nodes become expected state
Actual result:
All nodes keep provisioning state, provision task is still running (but with constant progress), stop_deployment task is ready with progress 100

 shotgun2 short-report
cat /etc/fuel_build_id:
 495
cat /etc/fuel_build_number:
 495
cat /etc/fuel_release:
 9.0
cat /etc/fuel_openstack_version:
 mitaka-9.0
rpm -qa | egrep 'fuel|astute|network-checker|nailgun|packetary|shotgun':
 python-fuelclient-9.0.0-1.mos356.noarch
 fuel-provisioning-scripts-9.0.0-1.mos8861.noarch
 rubygem-astute-9.0.0-1.mos774.noarch
 fuelmenu-9.0.0-1.mos275.noarch
 python-packetary-9.0.0-1.mos151.noarch
 fuel-bootstrap-cli-9.0.0-1.mos291.noarch
 fuel-setup-9.0.0-1.mos6357.noarch
 shotgun-9.0.0-1.mos90.noarch
 fuel-nailgun-9.0.0-1.mos8861.noarch
 fuel-agent-9.0.0-1.mos291.noarch
 fuel-library9.0-9.0.0-1.mos8605.noarch
 fuel-mirror-9.0.0-1.mos151.noarch
 fuel-ostf-9.0.0-1.mos946.noarch
 nailgun-mcagents-9.0.0-1.mos774.noarch
 fuel-ui-9.0.0-1.mos2814.noarch
 fuel-utils-9.0.0-1.mos8605.noarch
 network-checker-9.0.0-1.mos77.x86_64
 fuel-migrate-9.0.0-1.mos8605.noarch
 fuel-notify-9.0.0-1.mos8605.noarch
 fuel-release-9.0.0-1.mos6357.noarch
 fuel-misc-9.0.0-1.mos8605.noarch
 fuel-9.0.0-1.mos6357.noarch
 fuel-openstack-metadata-9.0.0-1.mos8861.noarch

'fuel task' and 'fuel node' output http://paste.openstack.org/show/583616/
shotgun full report http://paste.openstack.org/show/583617/
diagnostic snapshot https://drive.google.com/open?id=0B2ag_Bf-ShtTWHN3QmsyVW1HVVk

Revision history for this message
ElenaRossokhina (esolomina) wrote :
Revision history for this message
ElenaRossokhina (esolomina) wrote :
Revision history for this message
Alexander Kurenyshev (akurenyshev) wrote :

UPD: this environment is under VBox Windows 10

Changed in fuel:
importance: Undecided → High
assignee: nobody → Fuel Sustaining (fuel-sustaining-team)
milestone: none → 9.1
Revision history for this message
Stanislaw Bogatkin (sbogatkin) wrote :

It is a pretty like a question to astute. Moved to Vladimir S.

Changed in fuel:
assignee: Fuel Sustaining (fuel-sustaining-team) → Vladimir Sharshov (vsharshov)
Changed in fuel:
status: New → Confirmed
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
milestone: 9.1 → 9.2
Revision history for this message
Vladimir Sharshov (vsharshov) wrote :

I could not reproduce this bug. It can be connected with https://bugs.launchpad.net/fuel/+bug/1645612/comments/2

In 10.0 release we will change provision mechanism: from 10.0 provision become graph and stop mechanism will work the same way as for deployment.

Changed in fuel:
status: Confirmed → Incomplete
Changed in fuel:
milestone: 9.2 → 9.3
Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Marking as Invalid, because of no activity for more than a month.

Changed in fuel:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.