yahoo-eng-team team mailing list archive

[Vish Ishaya <vishvananda@xxxxxxxxx>]

why would we do this? 172.16.1.0 is a perfectly valid ip in the
172.16.1.0/19 range. If you don't want it to be used you should manually
reserve it.

** Changed in: nova
       Status: New => Invalid

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

Title:
  nova-network trying to use first IP of subrange (x.x.x.0)

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Hi,

  I found some bugly behavior in nova-network. After adding some
  looooong network (172.16.0.0/19 in my case) and marking first C-class
  subnet (172.16.0.0/24) of this network inoperable (trough setting
  reserved=1 directly in database) for technical usage, nova trying to
  assign first IP of 2nd subnet (172.16.1.0/24) to the first created VM.

  In result, we got VM with assigned IP 172.16.1.0, which can cause some
  strange things in networking and communication with world.

  By default, nova-manage marks reserved only first and last IPs of full
  added network (by CIDR), but I think, it must mark first and last IPs
  of each C-class subnet too.

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