yahoo-eng-team team mailing list archive

[zhaoleilc <1885570@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Description
 ===========
 When we deploy glance storage backend for cinder, there are some options which can
 be set:https://docs.openstack.org/mitaka/config-reference/image-service/backends.html#glance-cinder

 However, there is not an option which is indicative of availability
zone.

 When we create an image, a volume is built. We can choose a specific volume type 
 by setting cinder_volume_type so that the built volume complies with the specific
 volume type.

 When there is only a availability zone, the built volume is in this availability
 zone and belongs to the specific volume type.
 When there are multiple availability zones, the built volume is in the default
 availability zone, and in that case cinder will report an error which is "No valid
 backend was found" if the specific volume type does not correspond the volume
 backend which belogs to the default availability zone.

 Steps to reproduce
 ==================
 1. Deploy glance storage backend for cinder and set the cinder_volume_type to
 volume_for_glance.
 2. Create the volume type whose name is cinder_volume_type and which does not
 comply with the default availability zone.
 3. Upload a image to glance, but cinder will report an error which is "No valid
 backend was found".
 ​
 Expected result
 ===============
 When we choose a specific volume type by setting cinder_volume_type, the specific
 volume type should be allowed to belong any availability zone.

 Actual result
 =============
 When we choose a specific volume type by setting cinder_volume_type, the specific
 volume type can only belong the default availability zone.
 ​
 Environment
 ===========
 Rocky version of OpenStack

** Affects: glance
     Importance: Undecided
         Status: New

** Description changed:

  Description
   ===========
   When we deploy glance storage backend for cinder, there are some options which can
   be set:
-  https://docs.openstack.org/mitaka/config-reference/image- service/backends.html#glance-cinder
+  https://docs.openstack.org/mitaka/config-reference/image-service/backends.html#glance-cinder
  
   However, there is not an option which is indicative of availability
  zone.
  
   When we create an image, a volume is built. We can choose a specific volume type by
   setting
   cinder_volume_type so that the built volume complies with the specific volume type.
  
   When there is only a availability zone, the built volume is in this availability
   zone
   and belongs to the specific volume type.
   When there are multiple availability zones, the built volume is in the default
   availability
   zone, and in that case cinder will report an error which is "No valid backend was
   found" if
   the specific volume type does not correspond the volume backend which belogs to the
   default
   availability zone.
  
   ​
   Steps to reproduce
   ==================
   1. Deploy glance storage backend for cinder and set the cinder_volume_type to
   volume_for_glance.
   2. Create the volume type whose name is cinder_volume_type and which does not
   complies with
      the default availability zone.
   3. Upload a image to glance, but cinder will report an error which is "No valid
   backend was found".
   ​
   Expected result
   ===============
   When we choose a specific volume type by setting cinder_volume_type, the specific
   volume type should
   allow to belong any availability zone.
  
   Actual result
   =============
   When we choose a specific volume type by setting cinder_volume_type, the specific
   volume type can only
   belong the default availability zone.
   ​
   Environment
   ===========
   Rocky version of OpenStack

** Description changed:

  Description
   ===========
   When we deploy glance storage backend for cinder, there are some options which can
-  be set:
-  https://docs.openstack.org/mitaka/config-reference/image-service/backends.html#glance-cinder
+  be set:https://docs.openstack.org/mitaka/config-reference/image-service/backends.html#glance-cinder
  
   However, there is not an option which is indicative of availability
  zone.
  
   When we create an image, a volume is built. We can choose a specific volume type by
-  setting
-  cinder_volume_type so that the built volume complies with the specific volume type.
+  setting cinder_volume_type so that the built volume complies with the specific 
+  volume type.
  
   When there is only a availability zone, the built volume is in this availability
-  zone
-  and belongs to the specific volume type.
+  zone and belongs to the specific volume type.
   When there are multiple availability zones, the built volume is in the default
-  availability
-  zone, and in that case cinder will report an error which is "No valid backend was
-  found" if
-  the specific volume type does not correspond the volume backend which belogs to the
-  default
-  availability zone.
+  availability zone, and in that case cinder will report an error which is "No valid 
+  backend was found" if the specific volume type does not correspond the volume 
+  backend which belogs to the default availability zone.
  
-  ​
   Steps to reproduce
   ==================
   1. Deploy glance storage backend for cinder and set the cinder_volume_type to
   volume_for_glance.
   2. Create the volume type whose name is cinder_volume_type and which does not
-  complies with
-     the default availability zone.
+  comply with the default availability zone.
   3. Upload a image to glance, but cinder will report an error which is "No valid
   backend was found".
   ​
   Expected result
   ===============
   When we choose a specific volume type by setting cinder_volume_type, the specific
-  volume type should
-  allow to belong any availability zone.
+  volume type should be allowed to belong any availability zone.
  
   Actual result
   =============
   When we choose a specific volume type by setting cinder_volume_type, the specific
-  volume type can only
-  belong the default availability zone.
+  volume type can only belong the default availability zone.
   ​
   Environment
   ===========
   Rocky version of OpenStack

** Description changed:

  Description
   ===========
   When we deploy glance storage backend for cinder, there are some options which can
   be set:https://docs.openstack.org/mitaka/config-reference/image-service/backends.html#glance-cinder
  
   However, there is not an option which is indicative of availability
  zone.
  
-  When we create an image, a volume is built. We can choose a specific volume type by
-  setting cinder_volume_type so that the built volume complies with the specific 
-  volume type.
+  When we create an image, a volume is built. We can choose a specific volume type 
+  by setting cinder_volume_type so that the built volume complies with the specific
+  volume type.
  
   When there is only a availability zone, the built volume is in this availability
   zone and belongs to the specific volume type.
   When there are multiple availability zones, the built volume is in the default
-  availability zone, and in that case cinder will report an error which is "No valid 
-  backend was found" if the specific volume type does not correspond the volume 
-  backend which belogs to the default availability zone.
+  availability zone, and in that case cinder will report an error which is "No valid
+  backend was found" if the specific volume type does not correspond the volume
+  backend which belogs to the default availability zone.
  
   Steps to reproduce
   ==================
   1. Deploy glance storage backend for cinder and set the cinder_volume_type to
   volume_for_glance.
   2. Create the volume type whose name is cinder_volume_type and which does not
   comply with the default availability zone.
   3. Upload a image to glance, but cinder will report an error which is "No valid
   backend was found".
   ​
   Expected result
   ===============
   When we choose a specific volume type by setting cinder_volume_type, the specific
   volume type should be allowed to belong any availability zone.
  
   Actual result
   =============
   When we choose a specific volume type by setting cinder_volume_type, the specific
   volume type can only belong the default availability zone.
   ​
   Environment
   ===========
   Rocky version of OpenStack

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/1885570

Title:
  Miss availability zone option when deploy storage backend for cinder

Status in Glance:
  New

Bug description:
  Description
   ===========
   When we deploy glance storage backend for cinder, there are some options which can
   be set:https://docs.openstack.org/mitaka/config-reference/image-service/backends.html#glance-cinder

   However, there is not an option which is indicative of availability
  zone.

   When we create an image, a volume is built. We can choose a specific volume type 
   by setting cinder_volume_type so that the built volume complies with the specific
   volume type.

   When there is only a availability zone, the built volume is in this availability
   zone and belongs to the specific volume type.
   When there are multiple availability zones, the built volume is in the default
   availability zone, and in that case cinder will report an error which is "No valid
   backend was found" if the specific volume type does not correspond the volume
   backend which belogs to the default availability zone.

   Steps to reproduce
   ==================
   1. Deploy glance storage backend for cinder and set the cinder_volume_type to
   volume_for_glance.
   2. Create the volume type whose name is cinder_volume_type and which does not
   comply with the default availability zone.
   3. Upload a image to glance, but cinder will report an error which is "No valid
   backend was found".
   ​
   Expected result
   ===============
   When we choose a specific volume type by setting cinder_volume_type, the specific
   volume type should be allowed to belong any availability zone.

   Actual result
   =============
   When we choose a specific volume type by setting cinder_volume_type, the specific
   volume type can only belong the default availability zone.
   ​
   Environment
   ===========
   Rocky version of OpenStack

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