yahoo-eng-team team mailing list archive

[Inessa Vasilevskaya <ivasilevskaya@xxxxxxxxxxxx>]

Public bug reported:

Seen on mos 10, 1 controller/1 compute.

Not very difficult to trigger, though isn't reproduced on every run (got
3 hits in ~15 runs).

The error was seen while running this script (sorry about my bash
http://paste.openstack.org/show/545220/) on freshly deployed mos.

Steps to reproduce:
1). create floating id with nova floating-ip-create
2). boot a VM
3). right afterwards (not waiting for the VM to reach active state) assign a floating ip via nova floating-ip-associate

In ~20% of runs the following error was received: 
ERROR (BadRequest): No nw_info cache associated with instance (HTTP 400) (Request-ID: req-907e70c0-b6f7-4368-ae66-c02dd216000d)

The VM didn't get floating ip during unsuccessful runs.

** 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/1608726

Title:
  BadRequest during floating ip assignment

Status in OpenStack Compute (nova):
  New

Bug description:
  Seen on mos 10, 1 controller/1 compute.

  Not very difficult to trigger, though isn't reproduced on every run
  (got 3 hits in ~15 runs).

  The error was seen while running this script (sorry about my bash
  http://paste.openstack.org/show/545220/) on freshly deployed mos.

  Steps to reproduce:
  1). create floating id with nova floating-ip-create
  2). boot a VM
  3). right afterwards (not waiting for the VM to reach active state) assign a floating ip via nova floating-ip-associate

  In ~20% of runs the following error was received: 
  ERROR (BadRequest): No nw_info cache associated with instance (HTTP 400) (Request-ID: req-907e70c0-b6f7-4368-ae66-c02dd216000d)

  The VM didn't get floating ip during unsuccessful runs.

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