public address not always available for setting cmr ingress address
Bug #1727707 reported by
Ian Booth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Ian Booth | ||
Bug Description
When setting up relation data as a unit enter's scope, the cross model relations functionality will get the machine public address. But the public address may not yet have been assigned by the cloud and it so it correctly falls back to private address.
We need to consider how to wait for the public address so that it may be always used if available.
| Changed in juju: | |
| milestone: | 2.3-beta2 → none |
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.3-beta3 |
| assignee: | nobody → Ian Booth (wallyworld) |
| status: | Triaged → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
https:/