yahoo-eng-team team mailing list archive

[Stephen Finucane <1599400@xxxxxxxxxxxxxxxxxx>]

The move to validate these parameters at the API layer introduced in
Stein combined with the flavor extra spec validation work in Ussuri (API
microversion 2.86 or later) should have seen off this issue.

** Changed in: nova
       Status: In Progress => Won't Fix

** Changed in: nova
     Assignee: Ken'ichi Ohmichi (oomichi) => (unassigned)

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

Title:
  nova boot has unexpected API error

Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  Description:
  =====

  Nova allow users to set free-form flavor extra-specs "hw:cpu_policy"
  and "hw:cpu_thread_policy". However, these values are not true free-
  form values, but rather enum values. Specifying an invalid value for
  one of these values, and booting an instance with the invalid flavor
  will result in an uncaught ValueError in Nova and a HTTP 500 code
  being returned to the user.

  Reproduce:
  =====

  # 1. create flavor 11 with an illegal extra_spec
  "hw:cpu_thread_policy=shared"

      $ nova flavor-create test 11 128 1 3
      $ nova flavor-key 11 set hw:cpu_policy=dedicated
      $ nova flavor-key 11 set hw:cpu_thread_policy=shared

  # 2. boot an instance from that malformed flavor 11

      $ nova boot --image <image-id> --flavor 11 test

  Output:
  =====

  ERROR (ClientException): Unexpected API Error. Please report this at http://bugs.launchpad.net/nova/ and attach the Nova API log if possible.
  <type 'exceptions.ValueError'> (HTTP 500) (Request-ID: req-a26ad5f3-7982-4361-8817-0ab111ac9ab1)

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