Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1805773 - [DDF] Node Cleaning section needs to be changed.
Summary: [DDF] Node Cleaning section needs to be changed.
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 13.0 (Queens)
Hardware: All
OS: All
Target Milestone: ---
: ---
Assignee: Alex McLeod
QA Contact: RHOS Documentation Team
Depends On:
TreeView+ depends on / blocked
Reported: 2020-02-21 14:26 UTC by Direct Docs Feedback
Modified: 2020-10-07 13:42 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-10-07 13:42:40 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Direct Docs Feedback 2020-02-21 14:26:02 UTC
Node Cleaning section needs to be changed.

Make it:

 By default, the Bare Metal service is set to use a network named provisioning for node cleaning. However, network names are not unique in OpenStack Networking, so it is possible for a tenant to create a network with the same name, causing a conflict with the Bare Metal service. Therefore, it is recommended to use the network UUID instead.

    Configure cleaning by providing the provider network UUID on the controller running the Bare Metal Service:


        IronicCleaningNetwork: UUID

    Replace UUID with the UUID of the bare metal network created in the previous steps.

    You can find the UUID using openstack network show:

    openstack network show NETWORK_NAME -f value -c id


    This configuration must be done after the initial overcloud deployment, because the UUID for the network isnât available beforehand.
    Apply the changes by redeploying the overcloud with the openstack overcloud deploy command as described in Section 3.4, âDeploying the Overcloudâ. 

Redeploying the overcloud with openstack overcloud deploy will revert any manual changes, so make sure you have added the cleaning configuration to ~/templates/ironic.yaml (described in the previous step) before the next time you use openstack overcloud deploy. 

It is possible to apply the change manually without OpenStack Director for testing purposes:

Configure the cleaning network:
crudini --set /var/lib/config-data/puppet-generated/ironic/etc/ironic/ironic.conf neutron cleaning_network 

Restart the Bare Metal service:
docker restart ironic_conductor

Reported by: akaris


Note You need to log in before you can comment on or make changes to this bug.