Several deployment tasks stuck in running state
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Critical
|
Vladimir Sharshov | ||
Mitaka |
Fix Released
|
Critical
|
Vladimir Sharshov |
Bug Description
Several deplyment tasks never switch from running to ready state after successful deployment.
Steps to reprocude:
1. Create new env.
2. Add one controller node and deploy changes.
3. Check deployment tasks status after successful deployment.
Expecte4d result:
All tasks switch from running to ready state. time_end fiel contains adequate value.
Actual result:
Several tasks stuck in runnig state. time_end contains "None".
[root@nailgun ~]# fuel deployment-tasks --task-id 38 --status running
deployment_
-------
memcached | 1 | running | 2016-03-
primary-keystone | 1 | running | 2016-03-
enable_quorum | 1 | running | 2016-03-
dump_rabbitmq_
nova-keystone | 1 | running | 2016-03-
cinder-keystone | 1 | running | 2016-03-
primary-ceph-mon | 1 | running | 2016-03-
reserved_ports | 1 | running | 2016-03-
fuel_pkgs | 1 | running | 2016-03-
swift-keystone | 1 | running | 2016-03-
netconfig | 1 | running | 2016-03-
virtual_ips | 1 | running | 2016-03-
openstack-
radosgw-keystone | 1 | running | 2016-03-
openstack-
openstack-
api-proxy | 1 | running | 2016-03-
create-cinder-types | 1 | running | 2016-03-
disable_
openstack-
rsync_core_puppet | 1 | running | 2016-03-
primary-swift-proxy | 1 | running | 2016-03-
openstack-
tags: | added: area-python |
Changed in fuel: | |
assignee: | nobody → Fuel Python Team (fuel-python) |
importance: | Undecided → High |
milestone: | none → 9.0 |
tags: | added: team-enhancements |
Changed in fuel: | |
status: | Incomplete → Confirmed |
assignee: | Fuel Python Team (fuel-python) → Vladimir Sharshov (vsharshov) |
tags: | added: on-verification |
Changed in fuel: | |
milestone: | 9.0 → 10.0 |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: | added: on-verification |
(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:
expected result
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