step 1: create a image, and upload the image by "web-download" method. in glance code, it will add two property "os_glance_failed_import" and "os_glance_importing_to_stores".
step 2: in glance code , it will execute /v2/images.py and os_glance_import_task(), I guess it a sign, to sign a import-image task status. and it can force clean "the last task" and reimport image. whatever,I don't care it anymore
step 3: so, when I use a web-download method to upload a image , it will contains property "os_glance_failed_import" and "os_glance_failed_import". if create a volume by this image, It is also included in the volume_image_metadata property of the volume.
step 4: If i use "os-volume_upload_image" action of cinder, in cinder code. "os_glance_failed_import" and "os_glance_failed_import" will be param and rejected by glance, that's so bad.
bugs report: (in my view)
step 1: create a image, and upload the image by "web-download" method. in glance code, it will add two property "os_glance_ failed_ import" and "os_glance_ importing_ to_stores" .
step 2: in glance code , it will execute /v2/images.py and os_glance_ import_ task(), I guess it a sign, to sign a import-image task status. and it can force clean "the last task" and reimport image. whatever,I don't care it anymore
step 3: so, when I use a web-download method to upload a image , it will contains property "os_glance_ failed_ import" and "os_glance_ failed_ import" . if create a volume by this image, It is also included in the volume_ image_metadata property of the volume.
step 4: If i use "os-volume_ upload_ image" action of cinder, in cinder code. "os_glance_ failed_ import" and "os_glance_ failed_ import" will be param and rejected by glance, that's so bad.