yahoo-eng-team team mailing list archive

[Sven Kieske <2036877@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I'll copy from this report, please notice that I'm NOT the original
reporter!:

https://bugs.launchpad.net/kolla-ansible/+bug/2033980/comments/8

Before cleaning the PID file, I did take a look at the config of radvd:

```
$ cat /var/lib/neutron/ra/aee91f41-1945-40b4-b72f-8be2eb369b44.radvd.conf
interface qr-caa16d7e-26
{
   AdvSendAdvert on;
   MinRtrAdvInterval 30;
   MaxRtrAdvInterval 100;
   AdvLinkMTU 1450;

   RDNSS 2a02:74a0:x:0::53 10.40.3.53 2a02:74a0:x:0::54 {};

   prefix 2a02:74a0:x:y::/64
   {
        AdvOnLink on;
        AdvAutonomous on;
   };

   route fe80::a9fe:a9fe/128 {
   };
};
```

We've been configuring the router with terraform, assigning the ipv4
resolvers to the IPv4 subnet and the IPv6 resolvers to the IPv6 subnet.

After deleting the router, adjusting the subnets (no resolvers on v4,
only ipv6 resolvers on ipv6), and recreating the router, radvd is now
active and everything's fine.

It seems that due to misconfiguration (and incomplete template parsing),
IPv4 nameservers ended up in the config of radvd, which failed to start.
Neutron was then unable to clean up the pidfile, thus failing to start
radvd again.

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2036877

Title:
  radvd seems to crash when ipv4 addresses are supplied as nameservers
  to ipv6 subnets

Status in neutron:
  New

Bug description:
  I'll copy from this report, please notice that I'm NOT the original
  reporter!:

  https://bugs.launchpad.net/kolla-ansible/+bug/2033980/comments/8

  Before cleaning the PID file, I did take a look at the config of
  radvd:

  ```
  $ cat /var/lib/neutron/ra/aee91f41-1945-40b4-b72f-8be2eb369b44.radvd.conf
  interface qr-caa16d7e-26
  {
     AdvSendAdvert on;
     MinRtrAdvInterval 30;
     MaxRtrAdvInterval 100;
     AdvLinkMTU 1450;

     RDNSS 2a02:74a0:x:0::53 10.40.3.53 2a02:74a0:x:0::54 {};

     prefix 2a02:74a0:x:y::/64
     {
          AdvOnLink on;
          AdvAutonomous on;
     };

     route fe80::a9fe:a9fe/128 {
     };
  };
  ```

  We've been configuring the router with terraform, assigning the ipv4
  resolvers to the IPv4 subnet and the IPv6 resolvers to the IPv6
  subnet.

  After deleting the router, adjusting the subnets (no resolvers on v4,
  only ipv6 resolvers on ipv6), and recreating the router, radvd is now
  active and everything's fine.

  It seems that due to misconfiguration (and incomplete template
  parsing), IPv4 nameservers ended up in the config of radvd, which
  failed to start. Neutron was then unable to clean up the pidfile, thus
  failing to start radvd again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2036877/+subscriptions