### Test Scenario ### QE Setup is up and running with OSP13. Start "Clean" for BM Guests using: openstack baremetal node list openstack baremetal node manage <ID> openstack baremetal node provide <ID> ### Actual Result ### Clean fails and it seems that it happens because of "Ansible Networking" feature. ERRORs while "cleaning" is logged on Controller's server.log with the following content: 2019-11-07 13:21:13.582 38 ERROR networking_ansible.ml2.mech_driver [req-241223b6-c2c4-49f7-b6c0-4c06808a76bb 426d7163b8f94a1eaae114815e45c5ed cdc1abcbc6b845aea49de458ca8c1c04 - default default] Failed to plug in port 48683d87-0ba3-4e98-998e-5d912e821384 on device: switch1 from network 4e86a40b-6aa8-469f-8d2e-65059442561a reason: 'int' object has no attribute '__getitem__' 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers [req-241223b6-c2c4-49f7-b6c0-4c06808a76bb 426d7163b8f94a1eaae114815e45c5ed cdc1abcbc6b845aea49de458ca8c1c04 - default default] Mechanism driver ansible failed in bind_port: MechanismDriverError 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers Traceback (most recent call last): 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/neutron/plugins/ml2/managers.py", line 781, in _bind_port_level 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers driver.obj.bind_port(context) 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers File "/usr/lib/python2.7/site-packages/networking_ansible/ml2/mech_driver.py", line 277, in bind_port 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers raise ml2_exc.MechanismDriverError(e) 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers MechanismDriverError 2019-11-07 13:21:13.582 38 ERROR neutron.plugins.ml2.managers ### Expected Result ### "Clean" BM Guests should PASS
Sry, the + instead of the ? is probably my lack of experience with hotfixes. Thanks everyone.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0770