deployment stuck at 100% all nodes ready

Bug #1479789 reported by Andrey Epifanov
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Medium
MOS Maintenance
5.1.x
Won't Fix
Medium
MOS Maintenance

Bug Description

Our steps:
- perform the following command:
  fuel --env <cluster ID> deployment --delete
- added 4 new compute nodes (these nodes were already used before) to the already deployed env before (cluster)
- network verify (failed) ?! for the 3 nodes which were in cluster
- pushed deploy changes
- nodes were deployed 100% and marked as ready
  all tasks complete 100%
- deployment stuck and the env didn't go to the operational state

Workaround:
- deleted all tasks
- env still is not in operational state
- Openstack works fine

Env:
MOS: Mirantis Openstack::5.1.1.
OS: Centos
Reference architecture: -
Networking: Neutron::Neutron with GRE
Additional projects:
Related Projects: -
Glance back-end: -
Cinder back-end: -
Other 3rd party components: -

Revision history for this message
Oleksiy Molchanov (omolchanov) wrote :

Andrey, please attach diagnostic snapshot.

Changed in fuel:
milestone: none → 5.1.1-mu-1
assignee: nobody → Fuel Python Team (fuel-python)
Revision history for this message
Ihor Kalnytskyi (ikalnytskyi) wrote :

Move it to Incomplete until diagnostic snapshot is attached.

Changed in fuel:
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Miroslav Anashkin (manashkin) wrote :

Attached some logs.
Full snapshot is about 300 Gib.

Revision history for this message
Miroslav Anashkin (manashkin) wrote :
Dmitry Pyzhov (dpyzhov)
Changed in fuel:
status: Incomplete → Confirmed
Revision history for this message
Miroslav Anashkin (manashkin) wrote :
Andrew Woodward (xarses)
Changed in fuel:
assignee: Fuel Python Team (fuel-python) → MOS Sustaining (mos-sustaining)
tags: added: customer-found
Andrew Woodward (xarses)
Changed in fuel:
status: Confirmed → New
importance: Medium → Undecided
assignee: MOS Sustaining (mos-sustaining) → nobody
milestone: 5.1.1-mu-1 → 7.0
assignee: nobody → Fuel for Openstack (fuel)
Revision history for this message
Vitaly Sedelnik (vsedelnik) wrote :

Invalid for 5.1.1-updates because with 5.1.1 maint updates we could deliver OpenStack fixes only but not deployment time fixes.

Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

Bug is valid but won't be fixed due to low priority

Changed in fuel:
milestone: 7.0 → 5.1.1-mu-2
importance: Undecided → Medium
assignee: Fuel for Openstack (fuel) → MOS Sustaining (mos-sustaining)
status: New → Won't Fix
Roman Rufanov (rrufanov)
tags: added: support
Changed in fuel:
milestone: 5.1.1-mu-2 → 5.1.1-updates
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.