Skip to content

[stable/antelope] Use zaza.model.run_on_unit for ca checks#1411

Open
xtrusia wants to merge 1 commit into
openstack-charmers:stable/antelopefrom
xtrusia:backport-ca-run-on-unit-antelope
Open

[stable/antelope] Use zaza.model.run_on_unit for ca checks#1411
xtrusia wants to merge 1 commit into
openstack-charmers:stable/antelopefrom
xtrusia:backport-ca-run-on-unit-antelope

Conversation

@xtrusia

@xtrusia xtrusia commented Jul 5, 2026

Copy link
Copy Markdown
Contributor

Backport of #1192.

async_block_until_ca_exists uses libjuju unit.run to read the CA file on the units. The result structure of unit.run changed between libjuju 2.x and 3.x, so the results come back as None and the CA readiness check raises AttributeError, breaking vault setup under juju 3.x. Switch to zaza.model.run_on_unit which handles the version difference. Already on master, stable/caracal, stable/yoga and stable/zed.

Existing code uses the python libjuju unit.run in order to execute
a wait check for ca readiness across the units. The behavior of libjuju
changed between 2.x and 3.x and causes this functionality to break. This
is abstracted and handled in the zaza library, so use that code instead
as it properly handles the differences.

Signed-off-by: Billy Olsen <billy.olsen@canonical.com>
(cherry picked from commit a64d2c6)
Signed-off-by: Seyeong Kim <seyeong.kim@canonical.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants