This bug was fixed in the package resolvconf - 1.79ubuntu4.1
---
resolvconf (1.79ubuntu4.1) zesty-proposed; urgency=medium
* support reading dns information written by initramfs. (LP: #1711760)
-- Scott Moser Fri, 08 Dec 2017 14:47:54 -0500
** Changed in:
** Tags removed: verification-donezesty
** Tags added: verification-done-zesty
** Tags removed: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
I've verified zesty with the script that is attached.
Output is shown here.
** Attachment added: "verification log of zesty"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5023065/+files/zesty.log
** Tags removed: verification-needed verification-needed-zesty
** Tags added:
Hello Andres, or anyone else affected,
Accepted resolvconf into zesty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.79ubuntu4.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Also affects: resolvconf (Ubuntu Zesty)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu Zesty)
Status: New => Triaged
** Changed in: resolvconf (Ubuntu Zesty)
Importance: Undecided => Medium
--
You received this bug notification because you are a
** Description changed:
=== Begin SRU Template ===
[Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".
Thus dns resolution does not work. Of most interest was the MAAS use
case of the
This bug was fixed in the package resolvconf - 1.69ubuntu1.3
---
resolvconf (1.69ubuntu1.3) trusty-proposed; urgency=medium
* Fix bad shell syntax in newly added
/lib/resolvconf/net-interface-handler (LP: #1711760)
resolvconf (1.69ubuntu1.2) trusty-proposed; urgency=medium
** Attachment removed: "lp-1711760-test.sh: script to aid in testing default
to proposed"
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/4966838/+files/lp-1711760-test.sh
** Attachment removed: "updated recreate script that supports running in
'control' mode
** Attachment added: "output of running script with comments showing fix."
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5006686/+files/verify-trusty-lp-1711760.txt
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-done
** Attachment added: "final version of recreate script"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/5006685/+files/lp-1711760-test.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
Hello Andres, or anyone else affected,
Accepted resolvconf into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.69ubuntu1.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Attachment added: "one more try at reproduce script."
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1711760/+attachment/5006069/+files/lp-1711760-test.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
testing showed that I uploaded a bad version.
Fixed in a new upload
https://launchpadlibrarian.net/345007871/resolvconf_1.69ubuntu1.3_source.changes
** Tags removed: verification-needed verification-needed-trusty
** Tags added: verification-failed verification-failed-trusty
--
You received this
Hello Andres, or anyone else affected,
Accepted resolvconf into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/resolvconf/1.69ubuntu1.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: resolvconf (Ubuntu Trusty)
Status: Confirmed => In Progress
** Changed in: resolvconf (Ubuntu Trusty)
Assignee: (unassigned) => Scott Moser (smoser)
** Changed in: resolvconf (Ubuntu Xenial)
Assignee: (unassigned) => Scott Moser (smoser)
--
You received this bug
I've uploaded the same change that is in xenial but slightly adjusted for
trusty.
I'm attaching an updated recreate script that works for both xenial and trusty.
(trusty needs to install the cloud-initramfs-dyn-netconf package to mimic the
MAAS ephemeral environment).
** Attachment added:
** Merge proposal linked:
https://code.launchpad.net/~smoser/ubuntu/+source/resolvconf/+git/resolvconf/+merge/37
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
** Also affects: resolvconf (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: resolvconf (Ubuntu Trusty)
Status: New => Confirmed
** Changed in: resolvconf (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: resolvconf (Ubuntu Trusty)
Importance:
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during
** Description changed:
=== Begin SRU Template ===
[Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".
Thus dns resolution does not work. Of most interest was the MAAS use
case of the
This bug was fixed in the package resolvconf - 1.78ubuntu5
---
resolvconf (1.78ubuntu5) xenial; urgency=medium
* support reading dns information written by initramfs. (LP: #1711760)
-- Scott Moser Mon, 23 Oct 2017 12:44:53 -0400
** Changed in: resolvconf
I've verified these two manually! Thanks for all the work!
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "updated recreate script that supports running in
'control' mode (to show no harm is done)"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4998244/+files/lp-1711760-test.sh
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
the attached log shows this is working when expected and not when not
expected.
** Attachment added: "my.log: log of running lp-1711760-test.sh"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4998243/+files/my.log
--
You received this bug notification because you are a member of
> I have reviewed this. +1 from ~ubuntu-sru.
Thanks for the thoughtful review.
> What happens when the DHCP lease acquired in the initramfs expires? What
> if the DNS server changes after a new lease? Really it's the entire DHCP
> lease that needs handing over from the initramfs rather than just
I have reviewed this. +1 from ~ubuntu-sru.
Regression risk is mitigated as Scott says by careful gating of the
active code to limit exposure of these changes to the non-default use
case only.
I did note the following:
What happens when the DHCP lease acquired in the initramfs expires? What
if
Also, I've tested this in GMAAS and confirm the fix works!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during
Bumping this to critical provided that at this point, this completely
breaks MAAS.
** Changed in: resolvconf (Ubuntu Xenial)
Importance: Medium => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in
I updated some state on the tasks. As justification, this fix is in
resolvconf, so I dropped cloud-init. I had added it thinking it might
need integration, but it did not. Also marked the 'ubuntu' task as
"won't fix". The problem did not currently exist in Artful, and the
solution provided in
** Description changed:
=== Begin SRU Template ===
- [Impact]
+ [Impact]
Without this fix applied, dns settings provided to the dhcp response
in the initramfs are not reflected in the "real root".
Thus dns resolution does not work. Of most interest was the MAAS use
case of the
** Also affects: resolvconf (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: cloud-init (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
@Mark,
I do have access (just tested). I'll give it a try tomorrow! Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set
I think Andres has access to the GMAAS, would appreciate if he could
verify the fix there. If not, let me know and I can try it.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
I have verified that smoser changes do work with MAAS.
Testing steps:
1. Generated xenial amd64 image stream using smosers PPA.
2. Installed MAAS.
3. Removed the workaround in MAAS.
4. Imported the xenial amd64 image with smosers PPA.
5. Entered rescue mode.
6. Pinged google.com. (Worked)
7.
** Changed in: maas
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/332330
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3]
** Changed in: maas
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during
** Attachment added: "lp-1711760-test.sh: script to aid in testing default to
proposed"
https://bugs.launchpad.net/maas/+bug/1711760/+attachment/4966838/+files/lp-1711760-test.sh
** Attachment removed: "lp-1711760 script to aid in testing"
** Description changed:
+ === Begin SRU Template ===
+ [Impact]
+ Without this fix applied, dns settings provided to the dhcp response
+ in the initramfs are not reflected in the "real root".
+
+ Thus dns resolution does not work. Of most interest was the MAAS use
+ case of the
I've also asked the MAAS team to build a maas-images with an updated
squashfs.
I made a couple changes to lp:maas-images on Friday to make that easy to do
http://bazaar.launchpad.net/~maas-images-maintainers/maas-images/maas-ephemerals/revision/381
This script runs and demonstrates functional dns.
It launches a guest with a custom kernel command line
pointing to a nocloud datasource running on the host.
It uses user mode networking to seed a dns server and a
dns search.
The 'seedfrom' is done over dns which would not work if this
change
** Changed in: maas
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during
** Changed in: maas
Assignee: (unassigned) => Andres Rodriguez (andreserl)
** Changed in: maas
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
** Merge proposal linked:
https://code.launchpad.net/~andreserl/maas/+git/maas/+merge/331968
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3]
** Changed in: maas
Milestone: 2.3.0 => 2.3.0beta2
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3] resolv.conf is not set (during commissioning
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Scott Moser (smoser)
** Attachment added: "lp-1711760 script to aid in
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1711760
Title:
[2.3]
47 matches
Mail list logo