Another situation that caused a signature_verified issue:
1) Login as admin
2) Upload an ISO image to Glance
3) Set the image to "shared"
4) Use "image add project" to share the ISO with a given project
5) Login as the project admin
6) Accept the image (image set --accept, which does not appear to be documented)
7) Create a volume from the ISO (openstack volume create --image <shared_iso_image>)
This results in the volume having an "error" status.
The cinder logs include:
File "/var/lib/kolla/venv/lib/python2.7/site-packages/cinder/db/sqlalchemy/api.py", line 5042, in volume_glance_metadata_bulk_create\n volume_id=volume_id)\n', u'GlanceMetadataExists: Glance metadata cannot be updated, key signature_verified exists for volume id 29d4812b-7773-41f5-a75d-b818cd696de9\n'
The volume has the following property:
volume_image_metadata | {u'signature_verified': u'False'}
but the image does NOT have this property.
I'm not sure if this is a result of the same issue, but thought I would mention it. This seems like it may be a permissions issue on the shared image, which could become a problem for any image that is shared and deployed as a volume by the image consumer.
Another situation that caused a signature_verified issue:
1) Login as admin
2) Upload an ISO image to Glance
3) Set the image to "shared"
4) Use "image add project" to share the ISO with a given project
5) Login as the project admin
6) Accept the image (image set --accept, which does not appear to be documented)
7) Create a volume from the ISO (openstack volume create --image <shared_iso_image>)
This results in the volume having an "error" status.
The cinder logs include:
File "/var/lib/ kolla/venv/ lib/python2. 7/site- packages/ cinder/ db/sqlalchemy/ api.py" , line 5042, in volume_ glance_ metadata_ bulk_create\ n volume_ id=volume_ id)\n', u'GlanceMetadat aExists: Glance metadata cannot be updated, key signature_verified exists for volume id 29d4812b- 7773-41f5- a75d-b818cd696d e9\n'
The volume has the following property: image_metadata | {u'signature_ verified' : u'False'}
volume_
but the image does NOT have this property.
I'm not sure if this is a result of the same issue, but thought I would mention it. This seems like it may be a permissions issue on the shared image, which could become a problem for any image that is shared and deployed as a volume by the image consumer.
Eric