← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1392923] [NEW] Orphan floating ip's created via rapid delete/assign/remove operations

 

Public bug reported:

It is possible to create 'orphan' floating ip's (at least in devstack testing) through a sequence of:
delete vip
assign vip
remove vip

API calls + timestamps from a test run:
26101:[2014-11-14 17:18:57,446] mahmachine/INFO/stdout: 0x7f8833395250: delete floating ip id: 14
26145:[2014-11-14 17:18:58,237] mahmachine/INFO/stdout: 0x7f88333e8810: assign floating ip: 172.24.4.14 || d4545f39-6a5c-40e3-99f4-f72c22d56fc7
27333:[2014-11-14 17:19:25,144] mahmachine/INFO/stdout: 0x7f88333e8810: remove floating ip: 172.24.4.14 || d4545f39-6a5c-40e3-99f4-f72c22d56fc7

This results in floating ip addresses that are still listed as attached
to an instance, yet are not owned (and are not removable) by the
instance's owner.

In the database, the fixed_ip_id is not null (the server id), yet the project id is:
the 'host' column may or may not be populated, but the cause and effect appear to be the same regardless of this.

select id, address, fixed_ip_id, project_id, host from floating_ips where project_id IS NULL and fixed_ip_id IS NOT NULL;
+----+-------------+-------------+------------+-------------+
| id | address     | fixed_ip_id | project_id | host        |
+----+-------------+-------------+------------+-------------+
|  2 | 172.24.4.2  |           4 | NULL       | NULL        |
|  7 | 172.24.4.7  |           4 | NULL       | mahmachine  |
| 11 | 172.24.4.11 |           4 | NULL       | mahmachine  |
|  6 | 172.24.4.6  |           7 | NULL       | mahmachine  |
| 15 | 172.24.4.15 |           7 | NULL       | mahmachine  |
|  3 | 172.24.4.3  |           8 | NULL       | mahmachine  |
| 14 | 172.24.4.14 |          10 | NULL       | NULL        |
+----+-------------+-------------+------------+-------------+

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  Orphan floating ip's created via rapid delete/assign/remove operations

Status in OpenStack Compute (Nova):
  New

Bug description:
  It is possible to create 'orphan' floating ip's (at least in devstack testing) through a sequence of:
  delete vip
  assign vip
  remove vip

  API calls + timestamps from a test run:
  26101:[2014-11-14 17:18:57,446] mahmachine/INFO/stdout: 0x7f8833395250: delete floating ip id: 14
  26145:[2014-11-14 17:18:58,237] mahmachine/INFO/stdout: 0x7f88333e8810: assign floating ip: 172.24.4.14 || d4545f39-6a5c-40e3-99f4-f72c22d56fc7
  27333:[2014-11-14 17:19:25,144] mahmachine/INFO/stdout: 0x7f88333e8810: remove floating ip: 172.24.4.14 || d4545f39-6a5c-40e3-99f4-f72c22d56fc7

  This results in floating ip addresses that are still listed as
  attached to an instance, yet are not owned (and are not removable) by
  the instance's owner.

  In the database, the fixed_ip_id is not null (the server id), yet the project id is:
  the 'host' column may or may not be populated, but the cause and effect appear to be the same regardless of this.

  select id, address, fixed_ip_id, project_id, host from floating_ips where project_id IS NULL and fixed_ip_id IS NOT NULL;
  +----+-------------+-------------+------------+-------------+
  | id | address     | fixed_ip_id | project_id | host        |
  +----+-------------+-------------+------------+-------------+
  |  2 | 172.24.4.2  |           4 | NULL       | NULL        |
  |  7 | 172.24.4.7  |           4 | NULL       | mahmachine  |
  | 11 | 172.24.4.11 |           4 | NULL       | mahmachine  |
  |  6 | 172.24.4.6  |           7 | NULL       | mahmachine  |
  | 15 | 172.24.4.15 |           7 | NULL       | mahmachine  |
  |  3 | 172.24.4.3  |           8 | NULL       | mahmachine  |
  | 14 | 172.24.4.14 |          10 | NULL       | NULL        |
  +----+-------------+-------------+------------+-------------+

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


Follow ups

References