All Devstack Based Jobs Failing to Create Swap on master
Hello everyone, At approximately 12:53 UTC September 24 (today) [0] Devstack's Xena branch was created. Due to an unexpected side effect in Devstack's Zuul configs this has caused all Devstack based jobs against master and possible stable/xena to RETRY_LIMIT and fail. The underlying issue you'll see in the jobs is that mkswap cannot create swap because it already exists [1]. This happens because Devstack's pre-run playbook is running twice [2] and the configure-swap role is not idempotent. The role is running twice because the Devstack base job is loading master and stable/xena's configs and composing them together which results in two pre-run playbooks being selected one for each branch. This happens because Devstack's stable/xena branch explicitly states that its configs apply to master and feature/r1 branches [3]. I've pushed up a change [4] to remove this Zuul configuration from the Xena branch which I expect will fix things for us. [0] https://zuul.opendev.org/t/openstack/build/ebe77aee0c104c9e9b917ff28a4731ee/... [1] https://zuul.opendev.org/t/openstack/build/52fa83b18e1a476b80afc41617fe68f9/... [2] https://zuul.opendev.org/t/openstack/build/52fa83b18e1a476b80afc41617fe68f9/... [3] https://opendev.org/openstack/devstack/src/branch/stable/xena/.zuul.yaml#L1-... [4] https://review.opendev.org/c/openstack/devstack/+/810947
On Fri, Sep 24, 2021 at 10:14 AM Clark Boylan <cboylan@sapwetik.org> wrote:
Hello everyone,
At approximately 12:53 UTC September 24 (today) [0] Devstack's Xena branch was created. Due to an unexpected side effect in Devstack's Zuul configs this has caused all Devstack based jobs against master and possible stable/xena to RETRY_LIMIT and fail.
The underlying issue you'll see in the jobs is that mkswap cannot create swap because it already exists [1]. This happens because Devstack's pre-run playbook is running twice [2] and the configure-swap role is not idempotent. The role is running twice because the Devstack base job is loading master and stable/xena's configs and composing them together which results in two pre-run playbooks being selected one for each branch. This happens because Devstack's stable/xena branch explicitly states that its configs apply to master and feature/r1 branches [3].
I've pushed up a change [4] to remove this Zuul configuration from the Xena branch which I expect will fix things for us.
Thanks Clark - this was puzzling. Made a depends-on change in a devstack job elsewhere, and it went past the failure.
[0] https://zuul.opendev.org/t/openstack/build/ebe77aee0c104c9e9b917ff28a4731ee/... [1] https://zuul.opendev.org/t/openstack/build/52fa83b18e1a476b80afc41617fe68f9/... [2] https://zuul.opendev.org/t/openstack/build/52fa83b18e1a476b80afc41617fe68f9/... [3] https://opendev.org/openstack/devstack/src/branch/stable/xena/.zuul.yaml#L1-... [4] https://review.opendev.org/c/openstack/devstack/+/810947
On Fri, Sep 24, 2021, at 10:05 AM, Clark Boylan wrote:
snip
I've pushed up a change [4] to remove this Zuul configuration from the Xena branch which I expect will fix things for us.
snip
[4] https://review.opendev.org/c/openstack/devstack/+/810947
This change has merged and things appear happier. You should be clear to recheck at this point.
participants (2)
-
Clark Boylan
-
Goutham Pacha Ravi