[staging] [5.0.3] [5.1.2] Deploy cluster failed with timeout

Bug #1509000 reported by Kairat Kushaev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
High
Fuel Library (Deprecated)
5.0.x
Invalid
High
Fuel Library (Deprecated)
5.1.x
Won't Fix
High
Fuel Library (Deprecated)
6.0.x
Invalid
High
Fuel Library (Deprecated)
6.1.x
Invalid
High
Fuel Library (Deprecated)
7.0.x
Invalid
High
Fuel Library (Deprecated)
8.0.x
Invalid
High
Fuel Library (Deprecated)
Future
Invalid
High
Fuel Library (Deprecated)

Bug Description

Neutron Cluster deployment task stuck for more than 1 hour because of some reason.
You can see the error here:
https://old-stable-ci.infra.mirantis.net/job/5.0.3.staging.centos.bvt_1/316/console

https://old-stable-ci.infra.mirantis.net/job/5.1.2.staging.centos.bvt_1/320/console

If you look at nailgun logs you will see that the task should be completed at 12:41 but it just stuck for 40 minutes without useful explanation.
Apparently, the problem need to be reproduced with snapshot.

tags: added: staging
Changed in fuel:
milestone: none → 5.0-updates
importance: Undecided → High
Changed in fuel:
assignee: nobody → Bartłomiej Piotrowski (bpiotrowski)
assignee: Bartłomiej Piotrowski (bpiotrowski) → Fuel Library Team (fuel-library)
status: New → Confirmed
Revision history for this message
Kairat Kushaev (kkushaev) wrote :
summary: - [staging] [5.0.3] Deploy cluster failed with timeout
+ [staging] [5.0.3][5.1.2] Deploy cluster failed with timeout
summary: - [staging] [5.0.3][5.1.2] Deploy cluster failed with timeout
+ [staging] [5.0.3] [5.1.2] Deploy cluster failed with timeout
description: updated
Changed in fuel:
milestone: 5.0-updates → 9.0
status: Confirmed → New
Maciej Relewicz (rlu)
tags: added: area-library
Maciej Relewicz (rlu)
Changed in fuel:
status: New → Invalid
Maciej Relewicz (rlu)
Changed in fuel:
milestone: 9.0 → 5.0-updates
status: Invalid → Confirmed
Changed in fuel:
milestone: 5.0-updates → 9.0
Changed in fuel:
status: Confirmed → Invalid
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

MOS5.1 is no longer supported, moving to Won't Fix.

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.