Comment 1 for bug 1944978

Revision history for this message
Ronelle Landy (rlandy) wrote :

From Michael

The above error from Wes is different than the first error where no image was loaded in glance. It should be a different launchpad bug as they are unrelated.
The error Wes linked to today is a nova API failure.

Octavia worker log reported:
2021-09-23 05:53:30.165 43 ERROR octavia.network.drivers.neutron.allowed_address_pairs [-] Error plugging amphora (compute_id: 9b195052-8294-4855-afca-f4b1591ef28c) into port aaa37bba-4518-4621-b953-21db7380a3a9.: octavia.common.exceptions.ComputeUnknownException: Unknown exception from the compute driver: Unknown Error (HTTP 504).

The TripleO HAProxy instance reported:
Sep 23 05:53:29 standalone haproxy[12]: Server nova_osapi/standalone.ctlplane.localdomain is DOWN, reason: Layer7 timeout, check duration: 10001ms. 0 active and 0 backup servers left. 3 sessions active, 0 requeued, 0 remaining in queue.
Sep 23 05:53:29 standalone haproxy[12]: proxy nova_osapi has no server available!

The nova API log reports a traceback:
2021-09-23 05:53:31.148 11 ERROR nova.api.openstack.wsgi [req-a8f16fdc-0e92-4ff8-a414-8a40b2af5018 5fcf112ef52f4c88a39150602a71f492 8de52c88481246d7a2b8ac0dfc19f78d - default default] Unexpected exception in API method: oslo_messaging.exceptions.MessagingTimeout: Timed out waiting for a reply to message ID 66dcf42ffb3d4b97ba22ee6e46213bc4
2021-09-23 05:53:31.148 11 ERROR nova.api.openstack.wsgi Traceback (most recent call last):

This second job run failure is caused by nova failing in scenario 10.