yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Medium => Undecided

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

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

Title:
  response to vm spawn may  contain invalid values

Status in OpenStack Compute (nova):
  Expired

Bug description:
  When spawning a VM via nova API, the response contains a description
  of the server with the information available at API level.

  However the API makes assumptions for some of the fields which may
  turn out to be incorrect.

  For example:

  - availability zone: the default one is returned by the API, however
  logic in the scheduler may cause the non-default AZ to be used

  - security group: when spawning a VM using the --nic port=<uuid> flag
  in a neutron deployment, the server response shows the security group
  "default" in none was specified at creation time. However the correct
  SGs are those (if any) attached to the port rather than default

  The response from the API shall only contain information which the API
  can control.

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