Based on the feedback from the cinder team, the default volume type is
assumed to be public. Considering this, this is not a horizon bug
apparently. I will remove horizon from the affected projects.

** No longer affects: horizon

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1826259

Title:
  Create Volume dialog opens (from image panel in Horizon) but getting
  error default volume type can not be found

Status in StarlingX:
  Triaged

Bug description:
  Brief Description
  -----------------
  Create Volume dialog opens (from image panel in Horizon) but getting error 
default volume type can not be found

  Severity
  --------
  standard

  Steps to Reproduce
  ------------------
  1. As tenant user, navigate to the Images panel
  2. Select "Create Volume" to opent the dialog
  3. Confirm the volume "Type" setting

  Expected Behavior
  ------------------
  Create Volume dialog should open and a default "Type" should be set (so that 
errors are not popping up)

  +Note: Create Volume dialog from the Volumes panel has default Volume
  Type setting "No volume type"

  Actual Behavior
  ----------------
  Creating Volume dialog (from image panel) opens without a default Volume Type 
resulting in error
  Error: Unable to retrieve the default volume type.

  
  Reproducibility
  ---------------
  yes

  System Configuration
  --------------------
  any

  Branch/Pull Time/Commit
  -----------------------
  BUILD_ID="20190421T233001Z"

  
  Timestamp/Logs
  --------------
  "Default volume type can not be found. (HTTP 404) (Request-ID: 
req-e9858d29-31c8-4d37-a05e-54710d029332)"

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to