Blake.
that makes sense. I had forgotten about that switch to using rooturl.
So here is what happens. I do not think this is regression, though. I'm
not sure how it could have ever worked.
a.) initramfs (rooturl) configures networking due to 'ip=' on the command line.
this process writes files /run/network-eth0.conf with content shown in your
attached /run here.
b.) root pivots to new root (with the sqaushfs mounted loop), and keeps
/run intact.
c.) cloud-init reads the files in /run/network-eth0.conf and uses that
to override the fallback networking. In order to avoid bouncing the
interfaces configured in initramfs, cloud-init writes 'control-manual'
stanzas in ENI rather than 'auto eth0'. In the iscsi path, if cloud-init
wrote 'auto', then the nic might get bounced and iscsi root broken.
In the iscsi root case, its the 'net-interface-handler' that handles
transitioning the dns settings in /run/network-eth0.conf over to
the "real root". But in this case, nothing does that.
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning or testing)
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1711760/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
