azure multi model dns failure
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Andrew Wilkins | ||
Bug Description
I have 2 models in azure, and both have a "machine-X". The last one to come up seems to steal the dns entry.
## repro
juju create-model modelA
juju deploy ubuntu
juju create-model modelB
juju deploy ubuntu
juju switch modelA
juju run --machine 0 'host machine-0'
juju switch modelB
juju run --machine 0 'host machine-0'
## expected results
machine-0 resolves to the private ip address of machine-0 in the current model
## actual results
machine-0 resolves to the private ip address of the most recently deployed machine-0, regardless of model
## more info
http://
This is problematic when you have services that connect to hostnames. In my case, all my big data slaves from modelA try to connect to a master in modelB because the 'machine-X' dns entry points to modelB.
| Changed in juju-core: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: azure-provider juju-release-support network |
| Changed in juju-core: | |
| milestone: | none → 2.0-beta7 |
| Changed in juju-core: | |
| status: | Triaged → In Progress |
| assignee: | nobody → Andrew Wilkins (axwalk) |
| Andrew Wilkins (axwalk) wrote | #1 |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Kevin W Monroe (kwmonroe) wrote | #2 |
| affects: | juju-core → juju |
| Changed in juju: | |
| milestone: | 2.0-beta7 → none |
| milestone: | none → 2.0-beta7 |
Kevin, this would be because the models were sharing a network previously, which is no longer the case in master/beta-7. I've just bootstrapped master, added a model, and a machine to the second model. "host machine-0" returns a different DNS entry for machine-0 in each model.