← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1343320] [NEW] in init_l3 ip address delete may occurrent delete multiple ips

 

Public bug reported:

For example:

# ip ad add 10.1.1.1/24 dev lo
# ip ad add 10.1.1.2/24 dev lo

# ip ad
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 10.1.1.1/24 scope global lo
       valid_lft forever preferred_lft forever
    inet 10.1.1.2/24 scope global secondary lo
       valid_lft forever preferred_lft forever

# ip ad del 10.1.1.1/24 dev lo
# ip ad
1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

Added two ips, and deleted one, all ips are gone.

This is because 10.1.1.2 is secondary, if the primary address is
deleted, also does the secondary address.

There is an sysconf entry controls the behaviour of deleting primary ip
(/proc/sys/net/ipv4/conf/all/promote_secondaries). when set instead of
deleting the secondary address, it will be promoted to primary ip

We should set it when creating a namespace.

** Affects: neutron
     Importance: Undecided
         Status: New

** Description changed:

  For example:
  
  # ip ad add 10.1.1.1/24 dev lo
  # ip ad add 10.1.1.2/24 dev lo
  
  # ip ad
- 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default 
-     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
-     inet 10.1.1.1/24 scope global lo
-        valid_lft forever preferred_lft forever
-     inet 10.1.1.2/24 scope global secondary lo
-        valid_lft forever preferred_lft forever
+ 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default
+     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+     inet 10.1.1.1/24 scope global lo
+        valid_lft forever preferred_lft forever
+     inet 10.1.1.2/24 scope global secondary lo
+        valid_lft forever preferred_lft forever
  
  # ip ad del 10.1.1.1/24 dev lo
  # ip ad
- 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default 
-     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
+ 1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default
+     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  
  Added two ips, and deleted one, all ips are gone.
  
  This is because 10.1.1.2 is secondary, if the primary address is
  deleted, also does the secondary address.
  
  There is an sysconf entry controls the behaviour of deleting primary ip
  (/proc/sys/net/ipv4/conf/all/promote_secondaries). when set instead of
- deleting the secondary address, it will be promoted to the primary ip
+ deleting the secondary address, it will be promoted to primary ip
  
  We should set it when creating a namespace.

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

Title:
  in init_l3 ip address delete may occurrent delete multiple ips

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  For example:

  # ip ad add 10.1.1.1/24 dev lo
  # ip ad add 10.1.1.2/24 dev lo

  # ip ad
  1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
      inet 10.1.1.1/24 scope global lo
         valid_lft forever preferred_lft forever
      inet 10.1.1.2/24 scope global secondary lo
         valid_lft forever preferred_lft forever

  # ip ad del 10.1.1.1/24 dev lo
  # ip ad
  1: lo: <LOOPBACK> mtu 65536 qdisc noop state DOWN group default
      link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00

  Added two ips, and deleted one, all ips are gone.

  This is because 10.1.1.2 is secondary, if the primary address is
  deleted, also does the secondary address.

  There is an sysconf entry controls the behaviour of deleting primary
  ip (/proc/sys/net/ipv4/conf/all/promote_secondaries). when set instead
  of deleting the secondary address, it will be promoted to primary ip

  We should set it when creating a namespace.

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


Follow ups

References