Import of nodes on CLI incorrectly puts node in 'available' state

[Dan Trainor]

Importing nodes on the CLI with 'openstack baremetal import --json nodes.json' incorrectly puts a node in an 'available' state. A node in an 'available' state cannot be introspected. It looks as if the import process runs the register_or_update and then the provide Mistral action when it should only be running the register_or_update action.

[Dan Trainor (dtrainor)]

This happens regardless of if any machine-specific parameters are defined in the json file used for import.

[Dan Trainor (dtrainor)]

Example of nodes.json not defining extended properties of the node

[Dan Trainor (dtrainor)]

Example of nodes.json defining extended properties of the node

[Dan Trainor (dtrainor)]

The state of the node can be changed with 'ironic set-provision-state xx manage' to proceed with introspection

[Julie Pichon (jpichon)]

I don't have a Mitaka environment at hand to check and although looking at the Mitaka code, I don't see anything obvious moving the nodes to 'available' I suspect it was the default in the past as well, because "openstack baremetal introspection bulk start" takes nodes in 'available' state and moves them through the different states to run introspection. It would be good to confirm that the default didn't change though.

For what it's worth we're moving away from these commands exactly for this kind of reasons (see [1] for additional background information). A new import command was added during the Newton cycle that leaves the nodes in manageable state. Fom Ocata they should become the new default while the 'baremetal' commands will be deprecated.

$ openstack overcloud node import ~/instackenv.json

(There is also configure, provide and introspect in the same format for node management.)

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-May/095456.html

[Dan Trainor (dtrainor)]

I have not seen this behavior in the last several months, I believe the way that nodes were imported was refactored, making this go away. jpichon, is this your observation too?

[Julie Pichon (jpichon)]

I've been using the new commands ("openstack overcloud node import") since Newton so I'm not sure of the current status for "baremetal import."

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE