Signature verification failure leads to saving image
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Invalid
|
Undecided
|
Niall Bunting |
Bug Description
Overview:
When signature verification fails it can cause a 500 error. This causes the image to become stuck in the saving state.
What should happen is that it returns a 40? and the image is put into the deleted state.
Reproducing:
glance image-create --name mySignedImage --container-format bare --disk-format qcow2 --property img_signature=
+------
| Property | Value |
+------
| checksum | None |
| container_format | bare |
| created_at | 2016-06-
| disk_format | qcow2 |
| id | f0839709-
| img_signature | |
| img_signature_
| img_signature_
| img_signature_
| min_disk | 0 |
| min_ram | 0 |
| name | mySignedImage |
| owner | 7f065427534f49a
| protected | False |
| size | None |
| status | queued |
| tags | [] |
| updated_at | 2016-06-
| virtual_size | None |
| visibility | private |
+------
500 Internal Server Error
The server has either erred or is incapable of performing the requested operation.
(HTTP 500)
nib@work-
+------
| Property | Value |
+------
| checksum | None |
| container_format | bare |
| created_at | 2016-06-
| disk_format | qcow2 |
| id | f0839709-
| img_signature | |
| img_signature_
| img_signature_
| img_signature_
| min_disk | 0 |
| min_ram | 0 |
| name | mySignedImage |
| owner | 7f065427534f49a
| protected | False |
| size | None |
| status | saving |
| tags | [] |
| updated_at | 2016-06-
| virtual_size | None |
| visibility | private |
+------
Console:
2016-06-23 09:46:35.619 TRACE glance.common.wsgi _('Signature verification failed')
2016-06-23 09:46:35.619 TRACE glance.common.wsgi SignatureVerifi
2016-06-23 09:46:35.619 TRACE glance.common.wsgi
Changed in glance: | |
status: | New → Invalid |