Nodes provision failed after environment reset
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Vladimir Kozhukalov |
Bug Description
MOS 9.2, snapshot #577
Detailed description:
Environment nods provision is failed if after either failed or successful deployment a cluster was reset and provisioned again. After provisioning process and reboot nodes boot into bootstrap again instead of booting from disk.
Error message: "Provision has failed. #<RuntimeError: Could not find any hosts in discovery data provided>"
We've run into this issue on hardware lab, here is diagnostic snapshot: http://
Steps to reproduce:
1. Configure a new cluster
2. Deploy it (it does not matter whether deployment succeeds or not)
3. Reset cluster
4. Provision or deploy the cluster again
Expected result:
Provisioning is successful, deployment status is same as for step 2
Actual result:
Provision failed with message "Provision has failed. #<RuntimeError: Could not find any hosts in discovery data provided>" for every node.
Workaround:
Delete the cluster and create a new one from scratch
Changed in fuel: | |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in fuel: | |
status: | Confirmed → Fix Committed |
tags: | added: on-verification |
The issue appears when a user resets an environment and then immediately starts redeployment (not waiting for reset to finish).