Node update via "baremetal import" fails when some of the existing nodes are in not in "enroll" or "available" state
Bug #1635240 reported by
Dmitry Tantsur
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
Medium
|
Dmitry Tantsur |
Bug Description
Our workflows expect all nodes to be in these states. This is not correct, e.g. when some nodes are deployed to or are in manageable state. We need to only apply "manage" action to nodes in "enroll" state.
summary: |
- Node update fails when some of the nodes are in not in "enroll" or - "available" states + Node update via "baremetal import" fails when some of the existing nodes + are in not in "enroll" or "available" state |
Changed in tripleo: | |
milestone: | none → ocata-1 |
Changed in tripleo: | |
assignee: | nobody → Dmitry Tantsur (divius) |
Changed in tripleo: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/392179
Review: https:/