← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1742093] [NEW] ip_allocation attribute is not accessible over REST requests

 

Public bug reported:

Currently, one can set the ip_allocation attribute to "none" on a port
with the neutron API [1] or the python-neutronclient [2].

This is useful for instantiating a VM that doesn't have an IP, and
fixing [3]

However, to be able to read this attribute, the ip_allocation extension
must be enabled, which is not mandatory to set this attribute to "none".

The only way to enable this extension seems to activate the segments
service plugin. However, enabling this service plugin just to be able to
instantiate a VM without an IP is cumbersome.

Moreover, while using the API, the fact that the ip_allocation attribute
can be set to "none", but cannot be read afterward is inconsistent.


[1] https://review.openstack.org/#/c/361455/
[2] https://review.openstack.org/#/c/504817/
[3] https://bugs.launchpad.net/nova/+bug/1741575

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  ip_allocation attribute is not accessible over REST requests

Status in neutron:
  New

Bug description:
  Currently, one can set the ip_allocation attribute to "none" on a port
  with the neutron API [1] or the python-neutronclient [2].

  This is useful for instantiating a VM that doesn't have an IP, and
  fixing [3]

  However, to be able to read this attribute, the ip_allocation
  extension must be enabled, which is not mandatory to set this
  attribute to "none".

  The only way to enable this extension seems to activate the segments
  service plugin. However, enabling this service plugin just to be able
  to instantiate a VM without an IP is cumbersome.

  Moreover, while using the API, the fact that the ip_allocation
  attribute can be set to "none", but cannot be read afterward is
  inconsistent.

  
  [1] https://review.openstack.org/#/c/361455/
  [2] https://review.openstack.org/#/c/504817/
  [3] https://bugs.launchpad.net/nova/+bug/1741575

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