ovirt_vm ansible cloud-init ipv6 related

Dear oVirt Would you be so kind to help out clarifying if and how is IPv6 supported with -ansible / ovirt_vm / cloud-init boot protocol. I have created a VM template which by default uses cloud-init with following: [cid:image001.png@01D5251F.E55FEAA0] When I boot the VM from UI, each VM gets IPv4 DHCP and IPv6 DHCP6 address, default cloud-init setup and we have infrastructure for both IPv4 and IPv6. However, when calling same template via Ansible ovirt_vm, using following: cloud_init_nics: |~ - nic_name: eth0 |~ nic_boot_protocol: dhcp |~ nic_on_boot: true each VM receives only IPv4 DHCP and only IPv6 RA, but not DHCP IPv6. Looking at booted VM, following options are not set: * /etc/sysconfig/network => NETWORKING_IPV6=yes * Or /etc/sysconfig/network-scripts/ifcfg-eth0 => DHCPV6C=yes and IPV6INIT=yes We need IPv6 DHCP6 address , especially for registering it host with DNS AAAA record. Is this supported? Am I doing it wrong way? If its supported please let me know, how can I make sure that VMs created using Ansible also initialize DHCPV6. Please assist. Marko Vrgotic ActiveVideo

Hello, thanks for the report. This is indeed supported by oVirt, but it's not supported by ovirt_vm Ansible module, I've opened an issue[1]. Thanks. [1] https://github.com/ansible/ansible/issues/58054 On 17/06/2019 15:18, Vrgotic, Marko wrote:
Dear oVirt
Would you be so kind to help out clarifying if and how is IPv6 supported with
-ansible / ovirt_vm / cloud-init boot protocol.
I have created a VM template which by default uses cloud-init with following:
When I boot the VM from UI, each VM gets IPv4 DHCP and IPv6 DHCP6 address, default cloud-init setup and we have infrastructure for both IPv4 and IPv6.
However, when calling same template via Ansible ovirt_vm, using following:
cloud_init_nics: |~
- nic_name: eth0 |~
nic_boot_protocol: dhcp |~
nic_on_boot: true
each VM receives only IPv4 DHCP and only IPv6 RA, but not DHCP IPv6.
Looking at booted VM, following options are not set:
* /etc/sysconfig/network => NETWORKING_IPV6=yes * Or /etc/sysconfig/network-scripts/ifcfg-eth0 => DHCPV6C=yes and IPV6INIT=yes
We need IPv6 DHCP6 address , especially for registering it host with DNS AAAA record.
Is this supported? Am I doing it wrong way?
If its supported please let me know, how can I make sure that VMs created using Ansible also initialize DHCPV6.
Please assist.
Marko Vrgotic
ActiveVideo
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/MLM7X2UDVV7ACJ...

Hello Ondra, Thank you for reporting an issue, its appreciated. I have to ask something additional, if you had experience with it: - to work around the current situation, I have added /etc/cloud/cloud.cfg.d/99_custom-networking.cfg file with following content: network: version: 2 ethernets: eth0: dhcp4: true dhcp6: true eth1: dhcp4: true dhcp6: true - this works, meaning that DHCPV6 address is added, but it results in following situation: the RA route is killed, rendering VM unreachable - to solve this one , we added following line, route to link-local ipv6 of the vlan with runcmd: runcmd: - [ ip, "-6", route, add, default, via, "ipv6 : link : local ", dev, eth0 ] Still, this yaml is completely ignored/not even parsed. Cloud-init complains (looking at the logs) of the bad datasource, but I have configured following in the cloud.cfg: datasource_list: ["NoCloud", "ConfigDrive"] Thnak you. On 19/06/2019, 12:25, "Ondra Machacek" <omachace@redhat.com> wrote: Hello, thanks for the report. This is indeed supported by oVirt, but it's not supported by ovirt_vm Ansible module, I've opened an issue[1]. Thanks. [1] https://github.com/ansible/ansible/issues/58054 On 17/06/2019 15:18, Vrgotic, Marko wrote: > Dear oVirt > > Would you be so kind to help out clarifying if and how is IPv6 supported > with > > -ansible / ovirt_vm / cloud-init boot protocol. > > I have created a VM template which by default uses cloud-init with > following: > > When I boot the VM from UI, each VM gets IPv4 DHCP and IPv6 DHCP6 > address, default cloud-init setup and we have infrastructure for both > IPv4 and IPv6. > > However, when calling same template via Ansible ovirt_vm, using following: > > cloud_init_nics: > |~ > > - nic_name: > eth0 > |~ > > nic_boot_protocol: > dhcp > |~ > > nic_on_boot: true > > each VM receives only IPv4 DHCP and only IPv6 RA, but not DHCP IPv6. > > Looking at booted VM, following options are not set: > > * /etc/sysconfig/network => NETWORKING_IPV6=yes > * Or /etc/sysconfig/network-scripts/ifcfg-eth0 => DHCPV6C=yes and > IPV6INIT=yes > > We need IPv6 DHCP6 address , especially for registering it host with DNS > AAAA record. > > Is this supported? Am I doing it wrong way? > > If its supported please let me know, how can I make sure that VMs > created using Ansible also initialize DHCPV6. > > Please assist. > > Marko Vrgotic > > ActiveVideo > > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-leave@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/MLM7X2UDVV7ACJ... >
participants (2)
-
Ondra Machacek
-
Vrgotic, Marko