When creating a glance image with --copy-from option, if the network connection between Glance's backend (Swift) drops, the image gets stuck in 'saving' state despite Swift registering a connection timeout.
The bug is observed in MOS 9.x
Steps to reproduce:
root@cic-1:~# glance --os-image-api-version 1 image-create --name testTrusty --disk-format qcow2 --container-format bare --copy-from http://10.80.245.8:8000/sparse-file.img --is-public True --progress
+------------------+--------------------------------------+
| Property | Value |
+------------------+--------------------------------------+
| checksum | None |
| container_format | bare |
| created_at | 2019-04-11T17:36:44.000000 |
| deleted | False |
| deleted_at | None |
| disk_format | qcow2 |
| id | 97b91f48-b553-47da-9e46-dda4a0ea5e27 |
| is_public | True |
| min_disk | 0 |
| min_ram | 0 |
| name | testTrusty |
| owner | 7b0003268773455db9c64af90fff54c1 |
| protected | False |
| size | 10737418240 |
| status | queued |
| updated_at | 2019-04-11T17:36:44.000000 |
| virtual_size | None |
+------------------+--------------------------------------+
root@cic-1:~#
root@cic-1:~#
root@cic-1:~# glance image-list
+--------------------------------------+------------------+
| ID | Name |
+--------------------------------------+------------------+
| 957fdad7-70d8-4039-bd1d-1dc6485b4a3d | |
| eb37059e-7c56-4c4c-ad52-68d4ec043140 | emarklj_Ubuntu-1 |
| 091d0a0e-c756-49b4-875e-e655a638b9f9 | emhnprp_test |
| 32c02d01-cbf7-49ef-ab44-789bb84bb2e2 | node-image |
| f9c3eead-5baa-4557-a4fa-7ae721bc709b | test123 |
| 97b91f48-b553-47da-9e46-dda4a0ea5e27 | testTrusty |
| a47abfc8-f97f-4211-a720-1c3f70d3163b | TestVM |
+--------------------------------------+------------------+
root@cic-1:~# glance image-show 97b91f48-b553-47da-9e46-dda4a0ea5e27
+------------------+--------------------------------------+
| Property | Value |
+------------------+--------------------------------------+
| checksum | None |
| container_format | bare |
| created_at | 2019-04-11T17:36:44Z |
| disk_format | qcow2 |
| id | 97b91f48-b553-47da-9e46-dda4a0ea5e27 |
| min_disk | 0 |
| min_ram | 0 |
| name | testTrusty |
| owner | 7b0003268773455db9c64af90fff54c1 |
| protected | False |
| size | 10737418240 |
| status | saving |
| tags | [] |
| updated_at | 2019-04-11T17:36:44Z |
| virtual_size | None |
| visibility | public |
+------------------+--------------------------------------+
While creating image, remove the connection between cic and image source.
You will see similar log from swift-proxy-server:
ERROR Client read timeout (60s) (txn: tx986fb15e8a5d46f0954b6-005caf7b42) (client_ip: 192.168.13.2)
However, image will still remain in the 'saving' state.
Http is deprecated. And when the http connection is interrupted, swift-proxy-server writes the below error –
swift-proxy-
And also the swift-object-server writes the http code 408.
swift-object-
But in our case we have observed that the swift proxy server reports no error back. They expect that swift-proxy should report http exception as per below code.
Could you please clarify on expected behavior from swift-proxy in such case. Should it report back to glance/swift client/or any other