[MAAS 2 + Juju2.0b11] binding name "public" not defined by the unit's charm
Bug #1603229 reported by
Jason Hobbs
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Charm Helpers |
Confirmed
|
Undecided
|
Unassigned | ||
OpenStack Tempest Charm (Deprecated) |
Confirmed
|
Medium
|
Unassigned | ||
charms.openstack |
Confirmed
|
Undecided
|
Unassigned | ||
Juju Charms Collection |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I'm trying to use the tempest charm against a xenial based cloud deployed by juju 2.0 beta 11, to bare metal, with the MAAS provider.
The identity-
identity-
With admin, public, and internal bindings.
Here's my juju status yaml output:
http://
summary: |
tempest charm fails with 'binding name "admin" not defined by the unit's - charm' + charm' on juju2b11 |
summary: |
- binding name "public" not defined by the unit's charm + [MAAS 2 + Juju2.0b11] binding name "public" not defined by the unit's + charm |
Changed in charm-helpers: | |
status: | New → Confirmed |
Changed in charms.openstack: | |
status: | New → Confirmed |
To post a comment you must log in.
Attached juju log for the tempest unit.