Juju doesn't disable dhclient in KVMs
Bug #1666198 reported by
Ante Karamatić
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Witold Krecicki |
Bug Description
Once juju deploys a KVM, it properly changes /etc/network/
However, on first KVM boot there's still dhclient running on eth0. This happens because cloud-init creates /etc/network/
Juju should either ifdown eth0 or kill dhclient, before rewriting /e/n/i.
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
milestone: | none → 2.1.1 |
Changed in juju: | |
assignee: | nobody → Ian Booth (wallyworld) |
Changed in juju: | |
milestone: | 2.1.1 → none |
Changed in juju: | |
assignee: | Horacio Durán (hduran-8) → John A Meinel (jameinel) |
Changed in juju: | |
milestone: | 2.2-beta1 → 2.2-beta2 |
Changed in juju: | |
assignee: | John A Meinel (jameinel) → Witold Krecicki (wpk) |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
milestone: | 2.2-beta2 → 2.2-beta3 |
status: | Fix Committed → In Progress |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It seems that just doing "ifdown" isn't sufficient to stop dhclient. We may need to add a "dhclient -r" just before we do ifdown. I'm pretty sure the ifup will start it again if we stay in DHCP mode. (needs investigation to be sure of that.)