[Tracking] libjuju get_unit_address() fails on juju 2.9 #472
Comments
openstack-mirroring
pushed a commit
to openstack/charm-ceph-dashboard
that referenced
this issue
Mar 17, 2022
The overlay duplicates what is already in focal.yaml, and it is causing the gate deployment to fail as follows: ERROR cannot deploy bundle: the provided bundle has the following errors: charm path in application "ceph-dashboard" does not exist: /ceph-dashboard.charm Additionally this sets ZAZA_FEATURE_BUG472=1 for test runs as deployments cannot get a public address otherwise: openstack-charmers/zaza#472 Depends-On: https://review.opendev.org/c/openstack/charm-ceph-dashboard/+/830967 Change-Id: I2b65cbb9c8d5c8b978b1474ac216a527bea09cb5
freyes
added a commit
to freyes/zaza-openstack-tests
that referenced
this issue
Mar 22, 2023
Replace the use of "unit.public_address" with
zaza.model.get_unit_public_address().
AssertionError: {'host': '172.16.0.25', 'port': 3306, 'user': 'prom_exporter'} != {'host': None, 'port': 3306, 'user': 'prom_exporter'}
- {'host': '172.16.0.25', 'port': 3306, 'user': 'prom_exporter'}
? ^^^^^^^^^^^^^
+ {'host': None, 'port': 3306, 'user': 'prom_exporter'}
Related-Bug: openstack-charmers/zaza#472
lmlg
pushed a commit
to lmlg/ceph-charms
that referenced
this issue
Jan 22, 2025
The overlay duplicates what is already in focal.yaml, and it is causing the gate deployment to fail as follows: ERROR cannot deploy bundle: the provided bundle has the following errors: charm path in application "ceph-dashboard" does not exist: /ceph-dashboard.charm Additionally this sets ZAZA_FEATURE_BUG472=1 for test runs as deployments cannot get a public address otherwise: openstack-charmers/zaza#472 Depends-On: https://review.opendev.org/c/openstack/charm-ceph-dashboard/+/830967 Change-Id: I2b65cbb9c8d5c8b978b1474ac216a527bea09cb5
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a tracking bug for juju/python-libjuju#615.
A feature flag
ZAZA_FEATURE_BUG472=1will switch on using libjuju for test purposes. Otherwise it will fall back to using juju status and extracting the public address using the juju golang command line client.The text was updated successfully, but these errors were encountered: