Provisioning as a graph is unstable
Bug #1667006 reported by
Vladimir Kuklin
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
In Progress
|
High
|
Aleksandr Didenko | ||
Newton |
Invalid
|
High
|
Unassigned |
Bug Description
While testing provisioning graph I figured out the following:
1) move_to_bootstrap exits when the node is not yet ready for tasks execution, thus we have sporadic failures of the consequent 'upload_
2) it seems that cobbler does not apply netboot disable/enable flag immediately - we need either to sync it before or introduce some way of waiting for it to sync properly
3) node reboot task does not check system node type and reports that the node has successfully rebooted, while it failed to reboot into the OS actually
4) dnsmasq restart limits for systemd should be raised
description: | updated |
description: | updated |
Changed in fuel: | |
assignee: | Vladimir Kuklin (vkuklin) → Aleksandr Didenko (adidenko) |
tags: | added: swarm-fail |
To post a comment you must log in.
3) move_to_bootstrap and disable cobbler netboot should happen one by one on the master node on-startup changes the mcollective config and restarts it.
4) move_to_boostrap should fire nailgun agent to generate identity config or we will get into the situation when the node does not have mco id - we need to exit from move_to_bootstrap only when the identity is generated properly, e.g. when nailgun-agent write date to nailgun_uid and fix-configs-