IPv6 not enabled by default
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
cloud-init |
Expired
|
High
|
Unassigned | ||
cloud-init (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
In ubuntu-
I can enable IPv6 using "network-config" on a NoCloud cidata volume, but at that point I might as well just put my user-data in there and not use NoCloudNet. I would prefer to avoid this method.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cloud-init 20.1-10-
ProcVersionSign
Uname: Linux 5.4.0-1009-kvm x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckR
CloudName: NoCloud
Date: Thu May 14 15:26:23 2020
PackageArchitec
ProcEnviron:
TERM=vt220
PATH=(custom, no user)
XDG_RUNTIME_
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)
logs.tgz: Error: [Errno 2] No such file or directory: '/tmp/cloud-
Changed in cloud-init (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
Changed in cloud-init: | |
status: | New → Triaged |
importance: | Undecided → High |
Hi Kevin,
I did some testing and ipv6 seems to work as expected for me. I did the following:
1. `virsh net-edit default` and added:
<ip family='ipv6' address= '2001:db8: :1' prefix='64'>
</ip>
to have IPv6 configured on virbr0. As the prefix is a /64 dnsmasq will automatically send router advertisements on the interface, allowing SLAAC configuration.
2. `virsh net-destroy default`
`virsh net-start default`
`ip -c addr show virbr0` <- to check the v6 addr is there
3. Downloaded ubuntu- 20.04-server- cloudimg- amd64.img from images. ubuntu. com
cloud-
4. qemu-img create -f qcow2 -F qcow2 -o backing_ file=ubuntu- 20.04-server- cloudimg- amd64.img focal-v6test.qcow2
6. Created the following meta-data and user-data files:
$ cat meta-data
instance-id: iid-local01
local-hostname: cloudimg
$ cat user-data
#cloud-config
password: passw0rd
chpasswd: { expire: False }
ssh_pwauth: True
6. Served them over IPv6 with: `python3 -m http.server --bind ::`
7. Deployed the VM with:
virt-install --name focal-v6test --os-variant= ubuntu20. 04 --disk path=focal- v6test. qcow2 --import --sysinfo 'system. serial= ds=nocloud- net;s=http://[2001:db8: :1]:8000/ '
Everything worked as expected: the cloud-init picked up user-data and meta-data via ipv6 and configured the VM accordingly.
If something is not working for you I doubt the cause is IPv6 not being enabled. How are IPv6 addresses assigned on your network?
I'm marking this report as Incomplete for the moment, please set it back to New after commenting back, and we'll look at it again. Thanks!