| 2019-02-22 17:37:00 |
Gabriele Cerami |
description |
logs at https://logs.rdoproject.org/91/625191/10/openstack-check/tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001/4a4cc02/job-output.txt.gz#_2019-02-21_14_19_23_784677
show errors in OVB stack cleanup in post, at the end of the job
2019-02-21 14:19:08.159285 | LOOP [ovb-manage : List ports of baremetal for delete]
2019-02-21 14:19:15.803124 | primary | No Network found for provision-93331
2019-02-21 14:19:15.803628 | primary | ok: Item: {'delete': True, 'net': 'provision-93331'} Result: 1
2019-02-21 14:19:15.803708 |
2019-02-21 14:19:23.762223 | primary | No Network found for public-93331
2019-02-21 14:19:23.762439 | primary | ok: Item: {'delete': 'true', 'net': 'public-93331'} Result: 1
2019-02-21 14:19:23.784544 |
2019-02-21 14:19:23.784677 | LOOP [ovb-manage : Delete baremetal ports of OVB networks]
2019-02-21 14:21:14.999554 | primary | Failed to delete port with name or ID 'No': No Port found for No
2019-02-21 14:21:14.999954 | primary | Failed to delete port with name or ID 'Network': No Port found for Network
2019-02-21 14:21:15.000023 | primary | Failed to delete port with name or ID 'found': No Port found for found
2019-02-21 14:21:15.000088 | primary | Failed to delete port with name or ID 'for': No Port found for for
2019-02-21 14:21:15.000140 | primary | Failed to delete port with name or ID 'provision-93331': No Port found for provision-93331
2019-02-21 14:21:15.000189 | primary | 5 of 5 ports failed to delete.
For some reason, the networks between overcloud and undercloud get deleted before job completion, and the job doesn't ignore nor fail gracefully.
work items:
1) understand what deletes the stacks before the cleanup
2) make the role more idempotent. If the networks are not there, it's not really a failure, and it should be ok to proceed anyway. |
Original Reporter: Chandan Kumar
logs at https://logs.rdoproject.org/91/625191/10/openstack-check/tripleo-ci-centos-7-ovb-3ctlr_1comp-featureset001/4a4cc02/job-output.txt.gz#_2019-02-21_14_19_23_784677
show errors in OVB stack cleanup in post, at the end of the job
2019-02-21 14:19:08.159285 | LOOP [ovb-manage : List ports of baremetal for delete]
2019-02-21 14:19:15.803124 | primary | No Network found for provision-93331
2019-02-21 14:19:15.803628 | primary | ok: Item: {'delete': True, 'net': 'provision-93331'} Result: 1
2019-02-21 14:19:15.803708 |
2019-02-21 14:19:23.762223 | primary | No Network found for public-93331
2019-02-21 14:19:23.762439 | primary | ok: Item: {'delete': 'true', 'net': 'public-93331'} Result: 1
2019-02-21 14:19:23.784544 |
2019-02-21 14:19:23.784677 | LOOP [ovb-manage : Delete baremetal ports of OVB networks]
2019-02-21 14:21:14.999554 | primary | Failed to delete port with name or ID 'No': No Port found for No
2019-02-21 14:21:14.999954 | primary | Failed to delete port with name or ID 'Network': No Port found for Network
2019-02-21 14:21:15.000023 | primary | Failed to delete port with name or ID 'found': No Port found for found
2019-02-21 14:21:15.000088 | primary | Failed to delete port with name or ID 'for': No Port found for for
2019-02-21 14:21:15.000140 | primary | Failed to delete port with name or ID 'provision-93331': No Port found for provision-93331
2019-02-21 14:21:15.000189 | primary | 5 of 5 ports failed to delete.
For some reason, the networks between overcloud and undercloud get deleted before job completion, and the job doesn't ignore nor fail gracefully.
work items:
1) understand what deletes the stacks before the cleanup
2) make the role more idempotent. If the networks are not there, it's not really a failure, and it should be ok to proceed anyway. |
|
