yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

This is most likely not something that Nova is doing, but rather
something Neutron is doing when the port is created, based on the type
of neutron setup you have.

** Also affects: neutron
   Importance: Undecided
       Status: New

** Changed in: nova
       Status: New => 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/1617409

Title:
  fixed ip gets assigned when a port is created with no fixed ip

Status in neutron:
  New
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  When a neutron port is created with no fixed ip, and bound to a nova instance, a random IP is automatically picked up from subnet pool and assigned.
  Port request body :
  port_req_body
  {'port': {'network_id': u'b3bfb646-5794-44e6-86eb-0f90b18c6d78', 'tenant_id': u'ccfdd1bc5f894ad0a085e3e1d53f9329', 'mac_address': u'fa:f8:86:36:34:20', 'fixed_ips': [], 'admin_state_up': True}}

  After it is bound to a nova instance, it gets an ip associated with it. From neutron port-show :
  | fixed_ips           | {"subnet_id": "90f2afbc-bc64-4a0c-823a-a39d71f1fadd", "ip_address": "10.0.0.5"} |
  This appears to be a problem due to changes in newton. This behavior was not there in mitaka.

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