Re: RE : RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
no joy with the accept_ra fiddling, the image are all ubuntu or debian cloud-init ready and are working on all in one node but not dedicated compute node, it's as if the dhcpv6 packet (before address is allocated to interface) are not passing between the control node and the dedicated compute node.
Le 2022-09-20 10:53, Michael Hazan a écrit :
Thanks for the suggestion, i will look into the accept_ra setting. However, the very same image that boot on the « old » all in one node are getting ipv6 and ipv4 without issue. The network interfaces are configured similarly on all nodes.
Michael
DE : Neil Jerram ENVOYÉ LE :mardi, 20 septembre 2022 10:47 À : Michael Hazan CC : Lajos Katona; openstack-discuss@lists.openstack.org OBJET :Re: RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
They may be outdated now, but I wonder if any of the steps described at https://projectcalico.docs.tigera.io/networking/openstack/ipv6 would help you? In particular, given that you have no route, perhaps you need the accept_ra config.
Best wishes,
Neil
On Tue, Sep 20, 2022 at 9:12 AM Michael Hazan mhazan@mandint.org wrote:
Hello,
The 3 nodes are running Ubuntu 20.04 and using libvirt. The instance are Ubuntu or debian based. The openstack virtual network is configured with both a v4 and a v6 dhcp pool. The instance should be getting both v4 and v6 (on the same interface) but the instance that are hosted on the compute node only get v4. If i run the dhclient -6 -r the instance actually get it's ipv6 but it's wrongly configured with a /128 (instead of 64) and no route.
Michael
DE : Lajos Katona ENVOYÉ LE :mardi, 20 septembre 2022 09:39 À : mhazan@mandint.org CC : openstack-discuss@lists.openstack.org OBJET :Re: [neutron][nova][ipv6]instance on compute node not getting dhcpv6
Hi,
Do you have some more details of your environment, which backend you use? OVS?
Your VMs have both IPv4 and v6 addresses and you mean that they got IPv4 as expected?
Lajos
mhazan@mandint.org ezt írta (időpont: 2022. szept. 19., H, 16:19):
Hello all,
i manage a small openstack cluster installed via Ubuntu package, it has been upgraded since the day of Newton and currently running Victoria. it started as a single node with the basic services installed, later a dedicated storage node and compute node were added. after upgrading to victoria, any instance that boot on the dedicated compute node start up but fails to get it's global ipv6 via stateful dhcp6, only linklocal(fe80) ip is shown by the instance. The ipv6 is created in openstack, the dhcpv4 works and there are no issue if the instance boot on the "old" all in one node. i can manually allocate (by editing the instance network config file) the ipv6 config and it works. any pointer as to what could cause this issue ?
BR, Michael
i've been trying to look where the packets get lost via tcpdump and i found this error "satus-code NoAddrsAvail" but it doesn't seem linked to the old checksum-fill bug. anyone has see this ?
ethertype IPv6, IP6 (class 0xc0, flowlabel 0x399d4, hlim 64, next-header UDP (17) payload length: 76) fe80::a9fe:a9fe.dhcpv6-server > fe80::x.dhcpv6-client: [udp sum ok] dhcp6 advertise (xid=2096d0 (client-ID hwaddr/time type 1 time 717510824 fa163e066ac7) (server-ID hwaddr/time type 1 time 664975537 fa163eb2d07e) (status-code NoAddrsAvail))
Le 2022-09-21 09:57, mhazan@mandint.org a écrit :
no joy with the accept_ra fiddling, the image are all ubuntu or debian cloud-init ready and are working on all in one node but not dedicated compute node, it's as if the dhcpv6 packet (before address is allocated to interface) are not passing between the control node and the dedicated compute node.
Le 2022-09-20 10:53, Michael Hazan a écrit :
Thanks for the suggestion, i will look into the accept_ra setting. However, the very same image that boot on the « old » all in one node are getting ipv6 and ipv4 without issue. The network interfaces are configured similarly on all nodes.
Michael
DE : Neil Jerram ENVOYÉ LE :mardi, 20 septembre 2022 10:47 À : Michael Hazan CC : Lajos Katona; openstack-discuss@lists.openstack.org OBJET :Re: RE : [neutron][nova][ipv6]instance on compute node not getting dhcpv6
They may be outdated now, but I wonder if any of the steps described at https://projectcalico.docs.tigera.io/networking/openstack/ipv6 would help you? In particular, given that you have no route, perhaps you need the accept_ra config.
Best wishes,
Neil
On Tue, Sep 20, 2022 at 9:12 AM Michael Hazan mhazan@mandint.org wrote:
Hello,
The 3 nodes are running Ubuntu 20.04 and using libvirt. The instance are Ubuntu or debian based. The openstack virtual network is configured with both a v4 and a v6 dhcp pool. The instance should be getting both v4 and v6 (on the same interface) but the instance that are hosted on the compute node only get v4. If i run the dhclient -6 -r the instance actually get it's ipv6 but it's wrongly configured with a /128 (instead of 64) and no route.
Michael
DE : Lajos Katona ENVOYÉ LE :mardi, 20 septembre 2022 09:39 À : mhazan@mandint.org CC : openstack-discuss@lists.openstack.org OBJET :Re: [neutron][nova][ipv6]instance on compute node not getting dhcpv6
Hi,
Do you have some more details of your environment, which backend you use? OVS?
Your VMs have both IPv4 and v6 addresses and you mean that they got IPv4 as expected?
Lajos
mhazan@mandint.org ezt írta (időpont: 2022. szept. 19., H, 16:19):
Hello all,
i manage a small openstack cluster installed via Ubuntu package, it has been upgraded since the day of Newton and currently running Victoria. it started as a single node with the basic services installed, later a dedicated storage node and compute node were added. after upgrading to victoria, any instance that boot on the dedicated compute node start up but fails to get it's global ipv6 via stateful dhcp6, only linklocal(fe80) ip is shown by the instance. The ipv6 is created in openstack, the dhcpv4 works and there are no issue if the instance boot on the "old" all in one node. i can manually allocate (by editing the instance network config file) the ipv6 config and it works. any pointer as to what could cause this issue ?
BR, Michael
participants (1)
-
mhazan＠mandint.org