Adding additional node to instackenv.json and running "openstack baremetal import instackenv.json" causes all the existing nodes to lose their existing profile

[Miles Gould]

openstack-ironic: adding additional node to instackenv.json and running "openstack baremetal import --json instackenv.json" causes all the existing nodes to lose their tag to existing profile.

Environment:

Steps to reproduce:
1. Deploy overcloud with:
openstack overcloud deploy --debug \
--templates \
--libvirt-type kvm \
--ntp-server clock.redhat.com \
--neutron-network-type vxlan \
--neutron-tunnel-types vxlan \
--control-scale 3 \
--control-flavor controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484 \--compute-scale 1 \
--compute-flavor compute-b634c10a-570f-59ba-bdbf-0c313d745a10 \--environment-file "/usr/share/openstack-tripleo-heat-templates/environments/services/sahara.yaml" \
--ceph-storage-scale 2 \
--ceph-storage-flavor ceph-cf1f074b-dadb-5eb8-9eb0-55828273fab7 \
-e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml \
-e /home/stack/virt/ceph.yaml \
-e /home/stack/virt/network/network-environment.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
-e /home/stack/virt/hostnames.yml \
-e /home/stack/virt/debug.yaml

#Note the used flavors

2. Add additional node to instackenv.json
3. Run "openstack baremetal import --json instackenv.json"
4. Run "openstack baremetal configure boot
5. Attempt to scale compute with:

openstack overcloud deploy --debug \
--templates \
--libvirt-type kvm \
--ntp-server clock.redhat.com \
--neutron-network-type vxlan \
--neutron-tunnel-types vxlan \
--control-scale 3 \
--control-flavor controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484 \--compute-scale 2 \
--compute-flavor compute-b634c10a-570f-59ba-bdbf-0c313d745a10 \--environment-file "/usr/share/openstack-tripleo-heat-templates/environments/services/sahara.yaml" \
--ceph-storage-scale 2 \
--ceph-storage-flavor ceph-cf1f074b-dadb-5eb8-9eb0-55828273fab7 \
-e /usr/share/openstack-tripleo-heat-templates/environments/storage-environment.yaml \
-e /home/stack/virt/ceph.yaml \
-e /home/stack/virt/network/network-environment.yaml \
-e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
-e /home/stack/virt/hostnames.yml \
-e /home/stack/virt/debug.yaml

Result:

Error: only 0 of 3 requested ironic nodes are tagged to profile controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484 (for flavor controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484)
Recommendation: tag more nodes using ironic node-update <NODE ID> replace properties/capabilities=profile:controller-d75f3dec-c770-5f88-9d4c-3fea1bf9c484,boot_option:local
There are 7 ironic nodes with no profile that will not be used: b49e5645-4080-43c9-9cd4-cc8f16ca5aa6, 8ae72c6f-a391-4e3f-9f7b-e5eaede47e78, 92c54948-b480-43a9-9f6c-46dc39d6c601, d3efcfa7-cde9-42e0-8990-76a54d7f9bd4, 4b1090ae-889a-46ab-9c14-9525c17bd8ef, a855f1a0-881c-4395-a6e0-8134ae132475, 21b69552-1144-4dc0-aade-b96c7688d4c1

Run ironic node-show on any of the existing nodes - you'll see that none of the nodes has tag to profile.

Workaround, manually set the tag to profile with:
ironic node-update <NODE ID> replace properties/capabilities=profile:<profile>,boot_option:local

[Miles Gould (mgould)]

Upstreamified version of https://bugzilla.redhat.com/show_bug.cgi?id=1379815.

[Emilien Macchi (emilienm)]

There are no currently open reviews on this bug, changing the status back to the previous state and unassigning. If there are active reviews related to this bug, please include links in comments.

[Alex Schultz (alex-schultz)]

bz was closed as not a bug, so closing this as won't fix