yahoo-eng-team team mailing list archive

[Oleg Bondarev <obondarev@xxxxxxxxxxxx>]

This is covered by blueprint allow-specific-floating-ip-address,
https://review.openstack.org/#/c/70286/ ,
https://review.openstack.org/100214

** Changed in: neutron
       Status: Confirmed => 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/1336120

Title:
  specified valid floating IP  address doen't work when creating a
  floating IP

Status in OpenStack Neutron (virtual network service):
  Invalid

Bug description:
  In the neutron API doument "http://developer.openstack.org/api-ref-
  networking-v2.html",  floating_ip_address could be set in the
  POST/v2.0/​{tenant_id}​/floatingips request. the floating_ip_address
  is not handled in the source code except checking to see if the
  floating_ip_address is in the external network or not.

  https://github.com/openstack/neutron/blob/master/neutron/db/l3_db.py

  the valid specified floating_ip_address is not used during creating
  port in the external network:

  external_port = self._core_plugin.create_port(context.elevated(), {
                  'port':
                  {'tenant_id': '',  # tenant intentionally not set
                   'network_id': f_net_id,
                   'mac_address': attributes.ATTR_NOT_SPECIFIED,
                   'fixed_ips': attributes.ATTR_NOT_SPECIFIED,    
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
  >>>>>>  if the  floating_ip_address is valid ip address, it should be used here to create the port in the external network
  >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
                   'admin_state_up': True,
                   'device_id': fip_id,
                   'device_owner': DEVICE_OWNER_FLOATINGIP,
                   'name': ''}})

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