yahoo-eng-team team mailing list archive

[Xaver Stiensmeier <1991224@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description: When using connections available_floating_ip(network, server) in the past it automatically attached an existing un-attached floating-ip (or created a new one) to the given server.
Now available_floating_ip(network, server) only returns the ip address when finding an existing un-attached floating ip, but no longer attaches it. If no un-attached floating ip exists, it works as expected and creates a new one and attaches it to the given server.

Version Details: python-openstackclient==6.0.0

Crystal clear details to reproduce the bug:
# fill in your own data and make sure to have a not-associated floating-ip
conn = create_connection()
server = create_server(name="SomeName", flavor="SomeFlavor", image="SomeImage", network="SomeNetwork")
conn.wait_for_server(server, auto_ip=False, timeout=600)
conn.available_floating_ip("TheExternalNetworkOfSomeNetwork", server)

Test environment details: No changes I know of.

Actual result: Free floating ip is returned but not attached to given server
Expected result: Free floating ip is returned and attached to given server

Additional investigative details: I first thought it might be a racing
condition and implemented a long delay between server creation and
available_floating_ip. This did not help. I also looked into attaching a
floating ip manually, but only found the deprecated
https://docs.openstack.org/api-ref/compute/#add-associate-floating-ip-
addfloatingip-action-deprecated

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: floating-ip

-- 
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/1991224

Title:
  available_floating_ip(network, server) does no longer work when having
  an existing floating ip (Bug)

Status in OpenStack Compute (nova):
  New

Bug description:
  Description: When using connections available_floating_ip(network, server) in the past it automatically attached an existing un-attached floating-ip (or created a new one) to the given server.
  Now available_floating_ip(network, server) only returns the ip address when finding an existing un-attached floating ip, but no longer attaches it. If no un-attached floating ip exists, it works as expected and creates a new one and attaches it to the given server.

  Version Details: python-openstackclient==6.0.0

  Crystal clear details to reproduce the bug:
  # fill in your own data and make sure to have a not-associated floating-ip
  conn = create_connection()
  server = create_server(name="SomeName", flavor="SomeFlavor", image="SomeImage", network="SomeNetwork")
  conn.wait_for_server(server, auto_ip=False, timeout=600)
  conn.available_floating_ip("TheExternalNetworkOfSomeNetwork", server)

  Test environment details: No changes I know of.

  Actual result: Free floating ip is returned but not attached to given server
  Expected result: Free floating ip is returned and attached to given server

  Additional investigative details: I first thought it might be a racing
  condition and implemented a long delay between server creation and
  available_floating_ip. This did not help. I also looked into attaching
  a floating ip manually, but only found the deprecated
  https://docs.openstack.org/api-ref/compute/#add-associate-floating-ip-
  addfloatingip-action-deprecated

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