yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

Method `nova.volume.cinder.API#create` accepts `size` as the 3rd args,
but in wrapper of `nova.volume.cinder.translate_volume_exception`, the 3rd
parameter is volume_id. If we hit cinder exception when creating volumes
like the response body down below:
```
{"itemNotFound": {"message": "Volume type with name xxx could not be found.",
"code": 404}}
```
we may get exception in nova compute log like this:
```
BuildAbortException: Build of instance xxx aborted: Volume 40 could not be
found.
```
actually, `40` is volume size, not voluem id.

This could be a little misleading.

** Affects: nova
     Importance: Medium
     Assignee: Fan Zhang (fanzhang)
         Status: In Progress

** Affects: nova/queens
     Importance: Low
         Status: Confirmed

** Affects: nova/rocky
     Importance: Low
         Status: Confirmed

** Affects: nova/stein
     Importance: Low
         Status: Confirmed

** Affects: nova/train
     Importance: Low
         Status: Confirmed


** Tags: serviceability volumes

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/stein
   Importance: Undecided
       Status: New

** Also affects: nova/train
   Importance: Undecided
       Status: New

** Also affects: nova/rocky
   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/1846532

Title:
  Confusing error message when volume create fails

Status in OpenStack Compute (nova):
  In Progress
Status in OpenStack Compute (nova) queens series:
  Confirmed
Status in OpenStack Compute (nova) rocky series:
  Confirmed
Status in OpenStack Compute (nova) stein series:
  Confirmed
Status in OpenStack Compute (nova) train series:
  Confirmed

Bug description:
  Method `nova.volume.cinder.API#create` accepts `size` as the 3rd args,
  but in wrapper of `nova.volume.cinder.translate_volume_exception`, the 3rd
  parameter is volume_id. If we hit cinder exception when creating volumes
  like the response body down below:
  ```
  {"itemNotFound": {"message": "Volume type with name xxx could not be found.",
  "code": 404}}
  ```
  we may get exception in nova compute log like this:
  ```
  BuildAbortException: Build of instance xxx aborted: Volume 40 could not be
  found.
  ```
  actually, `40` is volume size, not voluem id.

  This could be a little misleading.

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