Molecule tests failing with 'Error: No such option: --base-config'

Bug #2018311 reported by Ronelle Landy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
Critical
Unassigned

Bug Description

Starting on 05/02, tripleo-ansible-centos-stream-molecule-tripleo_cephadm is failing with:

2023-05-02 12:40:26.110520 | centos-9-stream | try:
2023-05-02 12:40:26.110524 | centos-9-stream | > assert subprocess.call(cmd) == 0
2023-05-02 12:40:26.110529 | centos-9-stream | E AssertionError: assert 1 == 0
2023-05-02 12:40:26.110535 | centos-9-stream | E + where 1 = <function call at 0x7f7d0c67e310>(['python', '-m', 'molecule', '--base-config', '/home/zuul/src/opendev.org/openstack/tripleo-ansible/.config/molecule/config_podman.yml', 'converge', ...])
2023-05-02 12:40:26.110542 | centos-9-stream | E + where <function call at 0x7f7d0c67e310> = subprocess.call

....

2023-05-02 12:40:26.110792 | centos-9-stream | AttributeError: 'Runtime' object has no attribute 'exec'

...

2023-05-02 12:40:26.110891 | centos-9-stream | Error: No such option: --base-config
2023-05-02 12:40:26.110896 | centos-9-stream | ----- generated html file: file:///home/zuul/zuul-output/logs/reports.html -----

The test history is at:
https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ansible-centos-stream-molecule-tripleo_cephadm&skip=0

Example logs:

https://d02edf92696e37b29c38-5c978d7497c891806a9511dfe6eee904.ssl.cf1.rackcdn.com/881720/2/check/tripleo-ansible-centos-stream-molecule-tripleo_cephadm/18b633e/job-output.txt

https://storage.bhs.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_1f8/881720/2/check/tripleo-ansible-centos-stream-molecule-tripleo_cephadm/1f8490d/job-output.txt

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

Adding notes from chat:

Related failing line:

https://github.com/openstack/tripleo-ansible/blob/master/tests/test_molecule.py#L71

Cédric Jeanneret:
and nudge in your same patch maybe? replacing by "-c" iirc

Changed in tripleo:
milestone: none → antelope-1
importance: Undecided → Critical
status: New → Triaged
tags: added: promotion-blocker
Revision history for this message
Ronelle Landy (rlandy) wrote :

Some versions of packages that rev'ed between last passing and first failing test:

ansible-compat==4.0.1
coverage==7.2.5
ruamel.yaml==0.17.22
typing-extensions==4.5.0

Revision history for this message
Cédric Jeanneret (cjeanner) wrote :

It looks like an upstream bug:

https://github.com/ansible-community/molecule/issues/3903

Let's see with some pinning.

Revision history for this message
Cédric Jeanneret (cjeanner) wrote :

Passing job were apparently using ansible-compat==3.0.2

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to tripleo-ansible (stable/wallaby)

Related fix proposed to branch: stable/wallaby
Review: https://review.opendev.org/c/openstack/tripleo-ansible/+/882076

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix merged to tripleo-ansible (stable/wallaby)

Reviewed: https://review.opendev.org/c/openstack/tripleo-ansible/+/882076
Committed: https://opendev.org/openstack/tripleo-ansible/commit/45b0fc27cbc667fbba7b0e525b2ebb9801bdb7f4
Submitter: "Zuul (22348)"
Branch: stable/wallaby

commit 45b0fc27cbc667fbba7b0e525b2ebb9801bdb7f4
Author: Cédric Jeanneret <email address hidden>
Date: Tue May 2 17:27:59 2023 +0200

    Pin ansible-compat

    It seems latest version has some issues with Molecule, leading to the
    associated LP/CIX.
    You may also want to check out the original bug against Molecule:
    https://github.com/ansible-community/molecule/issues/3903

    Change-Id: I33bad8ef46061fc0ce67f7f445c2d63f17404dca
    Related-Bug: #2018311

tags: added: in-stable-wallaby
Ronelle Landy (rlandy)
Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
Cédric Jeanneret (cjeanner) wrote :
Ronelle Landy (rlandy)
Changed in tripleo:
status: In Progress → Fix Released
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.