← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1608726] Re: Confusing error message in BadRequest during floating ip assignment

 

Reviewed:  https://review.openstack.org/353687
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=cdb9a8435b1f8d75818ecaff2beb630b8f7160af
Submitter: Jenkins
Branch:    master

commit cdb9a8435b1f8d75818ecaff2beb630b8f7160af
Author: Augustina Ragwitz <auggy@xxxxxxxx>
Date:   Wed Aug 10 11:45:15 2016 -0700

    Improve error message for empty cached_nwinfo
    
    The error currently returned when NetworkInfo isn't yet available for an
    active instance is confusing for end users. This change updates that
    error message to something more informative.
    
    Change-Id: Ia1a88a63d2b1a2e595404e502f8094127135d7b0
    Closes-bug: #1608726


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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:
  Confusing error message in BadRequest during floating ip assignment

Status in OpenStack Compute (nova):
  Fix Released

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/545694/) 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.

  Expected result: nova would wait for the VM to become active before
  trying to assign a floating ip.

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


References