"Critical nodes are not available for deployment" after cluster reset

Bug #1673747 reported by Vladimir Khlyunev
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
New
High
Fuel Sustaining

Bug Description

ISO 1481

https://product-ci.infra.mirantis.net/job/10.0.system_test.ubuntu.cluster_actions/214/testReport/(root)/deploy_neutron_stop_reset_on_provisioning/deploy_neutron_stop_reset_on_provisioning/

After cluster reset and redeploy nodes fall into error state:
{"uid"=>"1",
 "error_msg"=>"Node is not ready for deployment: mcollective has not answered",
 "status"=>"error"}
 for report failed: Task status provided '' is not supported; Task name is not provided

[root@nailgun ~]# fuel node
...
 1 | error | slave-01_controller | 1 | 10.109.33.4 | 64:7d:d1:36:6a:7d | | controller | 1 | 1
 2 | error | slave-02_compute | 1 | 10.109.33.5 | 64:99:e5:1d:9f:a8 | | compute | 1 | 1

Revision history for this message
Vladimir Khlyunev (vkhlyunev) wrote :

May be the same as https://bugs.launchpad.net/fuel/+bug/1667006 but this bug is not clear

summary: - Critical nodes are not available for deployment: ["1", "2"]
+ "Critical nodes are not available for deployment" after cluster reset
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.