Can't bring up a machine on a dual network (ipv4 and ipv6)
Bug #1635716 reported by
Mathieu Trudel-Lapierre
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Trying to bring up a system with both IPv4 and IPv6 available should be generating files in /run/net6-
Both of these files may contain the DEVICE variable, as well as HOSTNAME and DNSDOMAIN.
I made some small changes to the dhclient hook for the initramfs to write that to both, since it does make sense for both IP protocols. However, this causes cloud-init to fail since the device name is defined in both files (ValueError, "defined multiple times" -- see screenshot).
Related bugs:
* bug 1621507: initramfs-tools configure_
* bug 1621615: network not configured when ipv6 netbooted into cloud-init
Related branches
~smoser/cloud-init:bug/1635716-initrd-cfg-net6
Rejected
for merging
into
cloud-init:master
- cloud-init Commiters: Pending requested
-
Diff: 88 lines (+44/-7)2 files modifiedcloudinit/net/cmdline.py (+12/-7)
tests/unittests/test_net.py (+32/-0)
description: | updated |
Changed in cloud-init (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.
Hi, this is new functionality, and cloud-init is being reasonable in its assertion as in any existing behavior this would be an error.
Please provide some examples of net6-eth0.conf and net-eth0.conf that should work together, and your expected result.