** Changed in: maas
Status: In Progress => Invalid
** Changed in: maas
Assignee: LaMont Jones (lamont) => (unassigned)
** Changed in: maas
Milestone: 2.1.3 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is fixed in cloud-init 0.7.9.
** Changed in: cloud-init
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when
This bug was fixed in the package cloud-initramfs-tools - 0.30ubuntu1.1
---
cloud-initramfs-tools (0.30ubuntu1.1) yakkety; urgency=medium
* sync with upstream at 0.32ubuntu1 (revno 129)
* overlayroot: fix overlayroot=crypt with newer initramfs-tools
(LP: #1634310)
*
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.10.1
---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.10.1) yakkety; urgency=medium
* debian/cloud-init.templates: enable DigitalOcean by default [Ben Howard]
* debian/cloud-init.postinst: update
This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.3
---
cloud-initramfs-tools (0.27ubuntu1.3) xenial; urgency=medium
* sync with upstream at 0.32ubuntu1 (revno 129)
* overlayroot: fix overlayroot=crypt with newer initramfs-tools
(LP: #1634310)
*
Discussed in IRC, all of the test cases in question have been met.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
Hello LaMont, or anyone else affected,
Accepted cloud-initramfs-tools into yakkety-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/cloud-initramfs-tools/0.30ubuntu1.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello LaMont, or anyone else affected,
Accepted cloud-init into yakkety-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.8-49-g9e904bb-0ubuntu1~16.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
Hello LaMont, or anyone else affected,
Accepted cloud-initramfs-tools into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/cloud-initramfs-tools/0.27ubuntu1.3 in a few hours, and then in the
-proposed repository.
Please help us by testing
** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
Status: Confirmed => In Progress
** Changed in: cloud-initramfs-tools (Ubuntu Yakkety)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug was fixed in the package cloud-init - 0.7.8-49-g9e904bb-
0ubuntu1~16.04.1
---
cloud-init (0.7.8-49-g9e904bb-0ubuntu1~16.04.1) xenial-proposed; urgency=medium
* debian/cloud-init.postinst: update /etc/fstab on Azure to fix
future resize operations. (LP: #1611074)
*
** Changed in: maas
Milestone: 2.1.2 => 2.1.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To manage notifications
I'm marking this verification-done for xenial and cloud-init.
This is based on the following:
a.) the updated code for this bug is only used when ip= is on the command line
b.) an update to initramfs-tools is needed (and not yet present) in order to
easily test
c.) the code path is tested
I marked 'verification-done-xenial-cloud-init' dont know what the right
way to say "this is tested for cloud-init" is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not
** Description changed:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only
MAAS.
After I hand-walked busybox through getting an IPv6 address, everything
worked just fine until cloud-init
Hello LaMont, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.8-47-gb6561a1-0ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
** Branch linked: lp:~smoser/ubuntu/xenial/cloud-initramfs-tools/pkg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To
This bug was fixed in the package cloud-init - 0.7.8-35-gc24187e-
0ubuntu1
---
cloud-init (0.7.8-35-gc24187e-0ubuntu1) zesty; urgency=medium
* New upstream snapshot.
- pyflakes: fix issue with pyflakes 1.3 found in ubuntu zesty-proposed.
-- Scott Moser
** Changed in: maas
Milestone: 2.1.1 => 2.1.2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To manage notifications
** Changed in: cloud-init
Status: Confirmed => Fix Committed
** Changed in: cloud-init (Ubuntu Yakkety)
Status: New => Confirmed
** Changed in: cloud-init (Ubuntu Yakkety)
Importance: Undecided => Medium
** Changed in: cloud-initramfs-tools (Ubuntu Yakkety)
Status: New
This bug was fixed in the package cloud-initramfs-tools - 0.31ubuntu1
---
cloud-initramfs-tools (0.31ubuntu1) zesty; urgency=medium
* cloud-initramfs-dyn-netconf: Further adjustments to support
IPV6 and the new DEVICE6 and net6-DEVICE.conf files.
(LP: #1621615)
-- Scott
My currently-pending MPs address the issue and work in conjunction with
the new fixes for Bug#1621507:
https://code.launchpad.net/~lamont/cloud-init/+git/bug-1621615-device6/+merge/309718
https://code.launchpad.net/~lamont/cloud-initramfs-tools/bug-1621615-device6/+merge/309719
These need to
** Branch linked: lp:~lamont/cloud-initramfs-tools/bug-1621615-device6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To
** Merge proposal linked:
https://code.launchpad.net/~lamont/cloud-init/+git/bug-1621615-device6/+merge/309718
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not
** Description changed:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only
MAAS.
After I hand-walked busybox through getting an IPv6 address, everything
worked just fine until cloud-init
This bug was fixed in the package cloud-init -
0.7.8-1-g3705bb5-0ubuntu1~16.04.3
---
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.3) xenial-proposed; urgency=medium
* ntp: move to run after apt configuration (LP: #1628337).
cloud-init (0.7.8-1-g3705bb5-0ubuntu1~16.04.2) xenial;
This bug was fixed in the package cloud-initramfs-tools - 0.27ubuntu1.2
---
cloud-initramfs-tools (0.27ubuntu1.2) xenial; urgency=medium
* Add IPV6 support to cloud-initramfs-dyn-netconf. (LP: #1621615)
-- LaMont Jones Tue, 04 Oct 2016 14:52:53 -0600
--
** Changed in: maas
Assignee: (unassigned) => LaMont Jones (lamont)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To
** Changed in: maas
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To manage
The packages have been verified in xenial-proposed.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not
** Branch linked: lp:~lamont/cloud-initramfs-tools/yakkety-ipv6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To manage
** Branch linked: lp:~lamont/cloud-initramfs-tools/0.29ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To manage
** Changed in: cloud-init
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To
** Changed in: cloud-initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-initramfs-tools (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello LaMont, or anyone else affected,
Accepted cloud-initramfs-tools into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/cloud-initramfs-tools/0.27ubuntu1.1 in a few hours, and then in the
-proposed repository.
Please help us by testing
This bug was fixed in the package cloud-initramfs-tools - 0.29ubuntu2
---
cloud-initramfs-tools (0.29ubuntu2) yakkety; urgency=medium
* Add IPV6 support to cloud-initramfs-dyn-netconf. (LP: #1621615)
-- LaMont Jones Tue, 27 Sep 2016 16:07:48 -0600
**
As far as I can tell this doesn't seem to be fixed in cloud-initramfs-
tools for Yakkety. Am I missing something?
** Also affects: cloud-initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Branch linked: lp:cloud-initramfs-tools
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
To manage notifications about
This bug was fixed in the package cloud-init - 0.7.8-8-g0439d8a-0ubuntu1
---
cloud-init (0.7.8-8-g0439d8a-0ubuntu1) yakkety; urgency=medium
* New upstream snapshot.
- Decode unicode types in decode_binary [Robert Schweikert]
- systemd: Ensure that cloud-init-local happens
** Also affects: cloud-initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: cloud-initramfs-tools (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
** Changed in: cloud-init (Ubuntu Xenial)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted into cloud-init
** Description changed:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
- how ipv6 netboot with iscsi root disk doesn't work, blocking ipv6-only
+ how IPv6 netboot with iscsi root disk doesn't work, blocking IPv6-only
MAAS.
After I hand-walked busybox through
Hello LaMont, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/0.7.8-1-g3705bb5-0ubuntu1~16.04.2 in a few hours, and then in the
-proposed repository.
Please help us by testing this
** Changed in: cloud-init
Importance: Undecided => Medium
** Changed in: cloud-init
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not
** Merge proposal linked:
https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/306345
** Also affects: cloud-init
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: cloud-init (Ubuntu)
Importance: Undecided => High
** Changed in: cloud-init (Ubuntu)
Status: New => Confirmed
** Description changed:
https://bugs.launchpad.net/ubuntu/+source/klibc/+bug/1621507 talks of
how ipv6 netboot with iscsi root disk doesn't work, blocking
** Also affects: open-iscsi (Ubuntu)
Importance: Undecided
Status: New
** Changed in: open-iscsi (Ubuntu)
Status: New => Invalid
** Package changed: open-iscsi (Ubuntu) => ubuntu
** No longer affects: ubuntu
--
You received this bug notification because you are a member of
When curtin deploys a machine, it emits a disable-networking config; I
suspect that the cloud-init upgrade/change/fix may have removed it as
the 50-cloud-init.cfg is only written out if networking is not disabled.
curtin does the following:
echo "network: {config: disabled}" >
** Attachment added: "cloud-init-output.log from the system"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1621615/+attachment/4743950/+files/cloud-init-output.log
** Changed in: maas
Milestone: None => 2.1.0
--
You received this bug notification because you are a member of
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743949/+files/cloud-init.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network
/run/net-eno1.conf from the booted system. The various packages needed
to reproduce this are found in ppa:lamont/maas.
** Attachment added: "net-eno1.conf from the booted system"
https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743948/+files/net-eno1.conf
--
You received this bug
With the attached patch applied to0.7.8-1-g3705bb5-0ubuntu1~16.04.1, we
still fail.
Details of the failure are attached below.
** Attachment added: "A patch that does not fix the problem."
https://bugs.launchpad.net/maas/+bug/1621615/+attachment/4743947/+files/ipv6-config
--
You received
In the category of "highly related":
grep -v ^# /etc/network/interfaces.d/50-cloud-init.cfg
auto lo
iface lo inet loopback
iface eno1 inet dhcp
dns-nameservers 2001:67c:1562:8010::2:1
netmask 64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: maas
Importance: Undecided
Status: New
** Tags added: maas-ipv6
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621615
Title:
network not configured when ipv6 netbooted
54 matches
Mail list logo