yahoo-eng-team team mailing list archive

[Brian Haley <1719240@xxxxxxxxxxxxxxxxxx>]

Actually, after asking for a review of the patch, I've abandoned it
since this behavior of allowing the gateway_ip valued not in the subnet
is intentional:

https://bugs.launchpad.net/neutron/+bug/1335023

So there are use cases where it is required, and being more strict would
break them.

** Changed in: neutron
       Status: In Progress => Invalid

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

Title:
  Host route with different network hop ip is getting updated and CSC is
  sending it the VM for static route update

Status in neutron:
  Invalid

Bug description:
  1. TROUBLE DESCRIPTION
  1.1. Trouble summary
       Host route with different network hop ip is getting updated and CSC is sending it the VM for static route update 

  1.2. Detailed trouble description
       
       - update neutron subnet with host route with different network next hop ip address
       - observe CSC updating the VM with the host route 
       - observe VM updating the same and traffic is affected
       - expected : since the feature works on ELAN , different subnet next hop ip should not be updated in the VM

  logs :

       stack@ubuntu:~/devstack$ neutron subnet-list
  +--------------------------------------+------+------------+------------------------------------------+
  | id                                   | name | cidr       | allocation_pools                         |
  +--------------------------------------+------+------------+------------------------------------------+
  | 2fb37acf-7f2a-46f5-aff5-e6ad898d2a83 | s2   | 2.1.1.0/24 | {"start": "2.1.1.2", "end": "2.1.1.254"} |
  | 3a7d0b90-ff45-45bc-969c-f9b40e338e72 | s1   | 1.1.1.0/24 | {"start": "1.1.1.2", "end": "1.1.1.254"} |
  | 9054b9f2-5ce3-4323-a99c-885392b7f309 | s3   | 3.1.1.0/24 | {"start": "3.1.1.2", "end": "3.1.1.254"} |
  | efb27dc3-ed22-46e9-8e22-9a4ca47a9e53 | s4   | 4.1.1.0/24 | {"start": "4.1.1.2", "end": "4.1.1.254"} |
  +--------------------------------------+------+------------+------------------------------------------+
  stack@ubuntu:~/devstack$
  stack@ubuntu:~/devstack$ neutron subnet-update s1 --host-route destination=3.1.1.0/24,nexthop=2.1.1.12
  Updated subnet: s1

  in VM:

  routes are getting updated 
  PING 3.1.1.7 (3.1.1.7): 56 data bytes
  64 bytes from 3.1.1.7: seq=0 ttl=64 time=0.433 ms
  64 bytes from 3.1.1.7: seq=1 ttl=64 time=0.143 ms

  --- 3.1.1.7 ping statistics ---
  2 packets transmitted, 2 packets received, 0% packet loss
  round-trip min/avg/max = 0.143/0.288/0.433 ms
  $
  $
  $ sudo /sbin/cirros-dhcpc up eth0
  udhcpc (v1.20.1) started
  Sending discover...
  Sending select for 1.1.1.13...
  Lease of 1.1.1.13 obtained, lease time 86400
  $
  $
  $ route -n
  Kernel IP routing table
  Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
  0.0.0.0         1.1.1.1         0.0.0.0         UG    0      0        0 eth0
  0.0.0.0         4.1.1.1         0.0.0.0         UG    0      0        0 eth3
  0.0.0.0         3.1.1.1         0.0.0.0         UG    0      0        0 eth2
  0.0.0.0         2.1.1.1         0.0.0.0         UG    0      0        0 eth1
  1.1.1.0         0.0.0.0         255.255.255.0   U     0      0        0 eth0
  2.1.1.0         0.0.0.0         255.255.255.0   U     0      0        0 eth1
  3.1.1.0         2.1.1.12        255.255.255.0   UG    0      0        0 eth1
  3.1.1.0         0.0.0.0         255.255.255.0   U     0      0        0 eth2
  4.1.1.0         0.0.0.0         255.255.255.0   U     0      0        0 eth3
  $ ping 3.1.1.7
  PING 3.1.1.7 (3.1.1.7): 56 data bytes

  --- 3.1.1.7 ping statistics ---
  2 packets transmitted, 0 packets received, 100% packet loss
  $
  $
  in CSC: routes are processed and send as an dhcp update
  2017-09-15 11:16:03,333 | INFO  | pool-28-thread-1 | DhcpPktHandler                   | 360 - org.opendaylight.netvirt.dhcpservice-impl - 0.3.4.SNAPSHOT | XXXX checking hostRoute HostRoutes{getDestination=IpPrefix [_ipv4Prefix=Ipv4Prefix [_value=3.1.1.0/24]], getNexthop=IpAddress [_ipv4Address=Ipv4Address [_value=2.1.1.12]], augmentations={}}
  2017-09-15 11:16:03,333 | INFO  | pool-28-thread-1 | DhcpPktHandler                   | 360 - org.opendaylight.netvirt.dhcpservice-impl - 0.3.4.SNAPSHOT | XXXX hostRoute next hop 2.1.1.12
  2017-09-15 11:16:03,333 | INFO  | pool-28-thread-1 | DhcpPktHandler                   | 360 - org.opendaylight.netvirt.dhcpservice-impl - 0.3.4.SNAPSHOT | XXXX finally going to set subnetHostRoutes [HostRoutes{getDestination=IpPrefix [_ipv4Prefix=Ipv4Prefix [_value=3.1.1.0/24]], getNexthop=IpAddress [_ipv4Address=Ipv4Address [_value=2.1.1.12]], augmentations={}}]


  1.3. Frequency of fault
       reproducible 

  1.4. Workaround and Recovery
       configure next hop in the same network

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