yahoo-eng-team team mailing list archive

[John Garbutt <john@xxxxxxxxxxxxxxx>]

So I think this is actually python-novaclient.

It checks to see if its a valid id, and correctly gets 404.

This seems like the correct/expected behaviour.

** Changed in: nova
       Status: Confirmed => Invalid

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

Title:
  Flavor m1.tiny could not be found Exception while creating instance

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  While creating instance using "nova boot --flavor <flavor name> ",
  Instance is created successfully, but in /var/log/nova/nova-api.log
  file we find the following error log:-

  HTTP exception thrown: Flavor m1.tiny could not be found.
  "GET /v2/cf66e8c655474008a8c1fc088665df83/flavors/m1.tiny HTTP/1.1" status: 404 len: 298 time: 0.0457311

  By Logs we can see :-
  1. nova-api first tries to find the flavor using flavor name and then throw the exception.
  2. then nova-api tries to find the flavor using flavor id.

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