Mistral

Swift action not working in CI

Bug #2090618 reported by Arnaud Morin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mistral
Fix Released
Undecided
Arnaud Morin

Bug Description

Recently, swift action is failing in devstack CI jobs.

It seems swift was never installed by default on devstack.
I can't find how it used to work in the past.

Workflow that is created from test_swift_actions is ending in ERROR, and it make sense because swift is not there :)

Arnaud Morin (arnaud-morin)
Changed in mistral:
assignee: nobody → Arnaud Morin (arnaud-morin)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to mistral-tempest-plugin (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/mistral-tempest-plugin/+/936789

Changed in mistral:
status: New → In Progress
Revision history for this message
Arnaud Morin (arnaud-morin) wrote :

devstack on CI comes from swift, because it's set here:
https://github.com/openstack/mistral-tempest-plugin/blob/8cb31ce1f40def20ff322f4ead7a0e30e282ba8e/.zuul.yaml#L31-L34

So why is it failing now?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to mistral-extra (master)

Related fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/mistral-extra/+/936792

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to mistral-extra (master)

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/mistral-extra/+/936793

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on mistral-tempest-plugin (master)

Change abandoned by "Arnaud Morin <email address hidden>" on branch: master
Review: https://review.opendev.org/c/openstack/mistral-tempest-plugin/+/936789
Reason: I found the root cause in mistral-extra

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to mistral-extra (master)

Reviewed: https://review.opendev.org/c/openstack/mistral-extra/+/936792
Committed: https://opendev.org/openstack/mistral-extra/commit/46b60f2ffb10f3de45872de22242bf3ce8266d2c
Submitter: "Zuul (22348)"
Branch: master

commit 46b60f2ffb10f3de45872de22242bf3ce8266d2c
Author: Arnaud M <email address hidden>
Date: Sat Nov 30 23:59:09 2024 +0100

    Get endpoint with service_name

    We recently introduced a change to handle multiple service types.
    This is preventing some services to be retrieved from name if the
    service type is empty (like swift).

    So, let's do a first loop over service types, then try to get endpoint
    with service name as fallback.

    Related-bug: #2090618

    Change-Id: I8bb0d3a6eea04901f3f54fbaf8ef8eee7edadc57
    Signed-off-by: Arnaud M <email address hidden>

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to mistral-extra (master)

Reviewed: https://review.opendev.org/c/openstack/mistral-extra/+/936793
Committed: https://opendev.org/openstack/mistral-extra/commit/d304f75335a16f50fe72822c3bdb5bcd8388cc56
Submitter: "Zuul (22348)"
Branch: master

commit d304f75335a16f50fe72822c3bdb5bcd8388cc56
Author: Arnaud M <email address hidden>
Date: Sat Nov 30 23:46:33 2024 +0100

    Use service-type instead of service-name

    Some openstack actions were still relying on service-name.
    While this is correct, it's different from what we have on other
    services.
    Let's use service_type everywhere.

    It's also the root cause of a recent bug in Swift action, because the
    service_type set to an empty array prevent the get_endpoint to be give
    correct answer.

    Closes-Bug: #2090618

    Change-Id: I471585a9520d03ce8e86c65592c687a9b5194461
    Signed-off-by: Arnaud M <email address hidden>

Changed in mistral:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.