[Reduced footprint] Provisioning on KVM fail with "MCollective agents 'uploadfile' '9' didn't respond within the allotted time."

Bug #1535754 reported by Ksenia Svechnikova
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
slava valyavskiy
8.0.x
Confirmed
High
Unassigned

Bug Description

Steps:

 1. Update /etc/fuel/astute.yaml file, "FEATURE_GROUPS" list. Specify the required advanced/ experimental features to enable.
[root@nailgun ~]# cat /etc/fuel/astute.yaml | grep -A1 FEATURE
"FEATURE_GROUPS":
  - "advanced"
 2. Upload network-template
 3. assign virt, compute node with {"id":1,"mem":4,"cpu":2,"vda_size":"70G"}
 4. Provision this node
 5. Assign controller role to the new node
 6. Deploy

Controller node fails with MCollective agents 'uploadfile' '9' didn't respond within the allotted time.

http://paste.openstack.org/show/484287/

Revision history for this message
Ksenia Svechnikova (kdemina) wrote :
Maciej Relewicz (rlu)
Changed in fuel:
status: New → Confirmed
Revision history for this message
Ksenia Svechnikova (kdemina) wrote :

Add the tag "qa-blocker" as it block acceptance of the whole feature on HW lab

tags: added: regression-8.0
tags: added: blocker-for-qa
Changed in fuel:
milestone: 8.0 → 9.0
Anton Matveev (amatveev)
tags: added: team-mixed
Revision history for this message
Ksenia Svechnikova (kdemina) wrote :

The issue was caused by wrong HW configuration

Changed in fuel:
assignee: Bartosz Kupidura (zynzel) → Aleksey Zvyagintsev (azvyagintsev)
status: Confirmed → Invalid
Revision history for this message
Ksenia Svechnikova (kdemina) wrote :

The issue was seen again

Changed in fuel:
status: Invalid → Confirmed
Changed in fuel:
assignee: Aleksey Zvyagintsev (azvyagintsev) → nobody
Changed in fuel:
assignee: nobody → slava valyavskiy (slava-val-al)
Revision history for this message
slava valyavskiy (slava-val-al) wrote :

It was researched 'let-rename' script was issues root case. It's using ifup scripts to apply interfaces re-naming, and each interfaces is trying to get ip by dhcp(~5 minutes per interface). So, as workaround we should wait for 25 minutes before start of deployment.

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.