← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1234855] Re: Cannot update dns name servers for in-use subnet

 

*** This bug is a duplicate of bug 1227268 ***
    https://bugs.launchpad.net/bugs/1227268

I think this is a duplicate of bug 1227268, feel free to reopen if I'm
mistaken. Agreed that a mechanism to only change the fields that were
actually modified would be a nice improvement in general.

** This bug has been marked a duplicate of bug 1227268
   Can't update neutron subnet

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1234855

Title:
  Cannot update dns name servers for in-use subnet

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  Attempting to modify the dns nameservers for an in-use subnet results
  in an error in Horizon.  Using the CLI client to do it manually works
  fine.

  Logged in as a non-admin user.

  Navigate to Networks
  Choose "Edit subnet"
  Change the dns name servers in "Subnet Detail" tab

  After updating, the following error pops up:

  Error: Failed to update subnet "10.5.0.0/16": Current gateway ip
  10.5.0.1 already in use by port cb573b75-a2a0-4751-ab8a-a5c38610f967.
  Unable to update.

  The port in question is in fact in use as the subnets router.  I
  wonder if Horizon is attempting to do a bulk update of all subnet
  configuration based instead of updating only those settings that have
  changed?

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