TripleO Train CentOS7 Overcloud Ironic reports "Clean Failed"

Bug #1891831 reported by Courtney Oakley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
New
Undecided
Unassigned

Bug Description

Description
===========
TripleO Centos7 Train/Current deploys Ironic on overcloud using the supplied templates

-e /usr/share/openstack-tripleo-heat-templates/environment/service/ironic-overcloud.yaml
-e /usr/share/openstack-tripleo-heat-templates/environment/service/ironic-inspector.yaml

The configuration is 3 Controllers,3 Compute,3 Ceph-Storage with SSL Public Endpoints and OVN (onv-ha-dvr).

After following all of the documented instructions and scripts for deploying Ironic Baremetal as-a Service with Openstack Train – CentOS7 the baremetal node successfully enrols, but then fails all provisioning steps that require node cleaning.

It displays “Cleaning” then "Clean Failed" before showing the following error.

Error: Detected change in error condition on node baremetal-0. Failed to prepare node 9101f6cc-71a6-4f27-8dbd-08702a95bfa2 for cleaning: Failed to create neutron ports for node's 9101f6cc-71a6-4f27-8dbd-08702a95bfa2 ports [Port(address=52:54:00:c8:ea:b6,created_at=2020-08-16T16:37:06Z,extra={},id=1,internal_info={},is_smartnic=False,local_link_connection={},node_id=1,physical_network=None,portgroup_id=None,pxe_enabled=True,updated_at=None,uuid=d4697454-cbd2-40c2-9784-75ba9120770b)].

Steps to reproduce
==================
Here are the steps followed;

1) ENROL THE BAREMETAL NODE
openstack baremetal create overcloud-baremetal1.yaml

2) CREATE THE DEFAULT BAREMETAL NETWORK & SUBNET
openstack network create --share --provider-network-type flat --provider-physical-network baremetal --external provisioning

openstack subnet create --network provisioning --subnet-range 10.x.x.0/24 --gateway 10.x.x.x --allocation-pool start=10.x.x.x,end=10.x.x.x provisioning-subnet

3) SET THE PROPERTIES OF THE NEW BAREMETAL NODE
openstack baremetal node set baremetal-0 --property local_gb=100 --property cpu_arch=x86_64 --property capabilities="boot_option:local"

openstack baremetal node set baremetal-0 --property cpus=4 --property memory_mb=4096

4) CREATE A BAREMETAL FLAVOUR (This one is a test one)
openstack flavor create --id auto --ram 4096 --vcpus 4 --disk 100 --property baremetal=true --public baremmetal-test

5) CREATE THE BAREMETAL DEPLOY IMAGES (KERNEL then RAMDISK)
openstack image create --container-format aki --disk-format aki --public --file /var/lib/ironic/httpboot/agent.kernel bm-deploy-kernel

openstack image create --container-format ari --disk-format ari --public --file /var/lib/ironic/httpboot/agent.ramdisk bm-deploy-ramdisk

6) INSTALL THE USER IMAGES (These are CentOS8.2 images; Kernel, Ramdisk, Image)
RAMDISK_ID=$(openstack image create \
--file centos82-image.initrd --public \
--container-format ari --disk-format ari \
-f value -c id centos82-image.initrd)

KERNEL_ID=$(openstack image create \
--file centos82-image.vmlinuz --public \
--container-format aki --disk-format aki \
-f value -c id centos82-image.vmlinuz)

openstack image create --file centos82-image.qcow2 --public --container-format bare --disk-format qcow2 --property kernel_id=$KERNEL_ID --property ramdisk_id=$RAMDISK_ID centos82-image

7) SPECIFY THE DEPLOY KERNEL AND DEPLOY RAMDISK
openstack baremetal node set baremetal-0 --driver-info deploy_kernel=$KERNEL_ID --driver-info deploy_ramdisk=$RAMDISK_ID

8) PROVISION THE NODE
openstack baremetal node manage baremetal-0
openstack baremetal node provide baremetal-0

(After this command the provisioning action "node provide" fails. Horizon shows the error described)

Expected Result
===============
The status should show "Cleaning", then "Available", meaning that the Node is ready for use as an overcloud deployment node (i.e. Baremetal compute node).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.