yahoo-eng-team team mailing list archive

[Assaf Muller <amuller@xxxxxxxxxx>]

I believe this was fixed by https://review.openstack.org/#/c/303966/.

** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  Created two dns-nameservers on one subnet by running two commands
  update "dns-nameserver" parameter in case of neutron server active-
  active

Status in neutron:
  Fix Released

Bug description:
  I had three controllers, I found a bug. I can create two dns-
  nameserver on one subnet by I run two commands update dns-nameserver
  parameter AT THE SAME TIME

  How to reproduce:

  Topology: http://codepad.org/ff0debPB

  Step1: Create one subnet with dns-nameserver is 8.8.8.8

  $ neutron subnet-create --name sub-int-net --dns-nameserver 8.8.8.8
  int-net 172.16.69.0/24

  Step 2: Update dns-nameserver parameter of "sub-int-net" 
  Please running commands AT THE SAME TIME

  - On Controller1
  $ neutron subnet-update --dns-nameserver 172.1.1.10 sub-int-net

  - On Controller2
  $ neutron subnet-update --dns-nameserver 172.1.1.20 sub-int-net

  The result:

  - Before update:
  $ neutron subnet-show sub-int-net
  This is the result: http://codepad.org/QLRnNebj

  - After update
  $ neutron subnet-show sub-int-net
  This is the result: http://codepad.org/y94cKrGV
  (Please note line 7&8)

  Check in database:
  This is the result: http://codepad.org/tOoWGVs8

  In originally, When we update dns-nameserver parameter, the system will remove the existing dns-nameserver and write a new dns-nameserver, which have value in command update 
  That mean: after update this subnet has only one dns-nameserver.

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