juju uses different logic for showing IP addresses for containers vs host machines
Bug #1698130 reported by
John A Meinel
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Triaged
|
Low
|
Unassigned | ||
Bug Description
On one of our large deployments when deploying many applications to both LXD containers as well as host machines, when doing "juju status", all of the containers are listed with IPv6 addresses while all of the host machines are only showing IPv4 addresses.
All of the containers do have IPv4 addresses from the host space.
| tags: | added: adrastea |
Revision history for this message
| John A Meinel (jameinel) wrote | #1 |
| tags: |
added: maas-provider removed: maas |
Revision history for this message
| Canonical Juju QA Bot (juju-qa-bot) wrote | #2 |
| Changed in juju: | |
| importance: | Medium → Low |
| tags: | added: expirebugs-bot |
To post a comment you must log in.
From talking with mskalka it may just be that v6 is disabled on the host machines so we pick v6 when its available and then v4, but the host machines don't have v6 addresses.