PUT /placement/traits/{trait} occasionally fails with 502 Bad Gateway

Bug #2029520 reported by Stephen Finucane
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

We've been seeing a failures in a test in OpenStackSDK. The test simply create a new trait, lists all traits, shows the created trait, and then deletes the created trait. The failure occurs during the create step, when Apache returns the following error message:

    <title>502 Bad Gateway</title>
    <h1>Bad Gateway</h1>
    <p>The proxy server received an invalid
    response from an upstream server.<br />
    <p>Additionally, a 201 Created
    error was encountered while trying to use an ErrorDocument to handle the request.</p>
    <address>Apache/2.4.52 (Ubuntu) Server at Port 80</address>

Searching for "Additionally, a 201 Created error" returns exactly one result on Google, so this is a very unusual condition. I suspect this might not be a placement issue but rather an issue with uWSGI or WebOb but I've yet to find a smoking gun. Fortunately reproduction is relatively easy: against a local DevStack deployment run the following from the openstacksdk repo:

    OS_TEST_TIMEOUT=60 tox -e functional-py310 -- \
      -n openstack/tests/functional/placement/v1/test_trait.py \

Note that you may need to enable this test as we're going to skip it shortly.

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.