[Glance] create image by downloading/importing from UI vs. CLI
Hi,
The initial issue I saw was "The Store URI was malformed." from Horizon when creating image by URL [1].
It works fine with Glance CLI as the following. ======== glance image-create --container-format bare --disk-format qcow2 --name cirros-test glance image-import --import-method web-download --uri https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img cirros-test ========
When I look into it, I see that UI and CLI work differently, they are handled by different workflow in Glance. Why is that? Why not UI follows the same workflow as CLI?
The root cause is that, [1] redirect to [2] and redirect to [3]. One issue here is that, query is not supported in [4]. pieces.query is dropped. When I attached query parameters, I got 403. And that's because, the workflow for UI is checking quota policy when adding location. It needs to get the size of image by HEAD request. But the signature in [3] is for GET request. So that HEAD request is forbidden by S3.
I don't think we can get an URL with signature for HEAD request in such case. So I go for an ugly workaround to skip the size check. Any ideas to make it work better?
Is quota policy involved in CLI workflow? Again, can we make UI work the same way as CLI?
[1] https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img [2] https://github.com/cirros-dev/cirros/releases/download/0.5.1/cirros-0.5.1-x8... [3] https://github-production-release-asset-2e65be.s3.amazonaws.com/219785102/6e... [4] https://github.com/openstack/glance_store/blob/488d3e2fe31e4fc7a461e9de8b20d...
Thanks! Tony
On 10/24/20 3:37 PM, Tony Liu wrote:
Hi,
The initial issue I saw was "The Store URI was malformed." from Horizon when creating image by URL [1].
It works fine with Glance CLI as the following.
glance image-create --container-format bare --disk-format qcow2 --name cirros-test glance image-import --import-method web-download --uri https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img cirros-test ========
When I look into it, I see that UI and CLI work differently, they are handled by different workflow in Glance. Why is that? Why not UI follows the same workflow as CLI?
No input, but adding the [horizon] tag to the subject line to try to get the right set of eyes on it.
The root cause is that, [1] redirect to [2] and redirect to [3]. One issue here is that, query is not supported in [4]. pieces.query is dropped. When I attached query parameters, I got 403. And that's because, the workflow for UI is checking quota policy when adding location. It needs to get the size of image by HEAD request. But the signature in [3] is for GET request. So that HEAD request is forbidden by S3.
I don't think we can get an URL with signature for HEAD request in such case. So I go for an ugly workaround to skip the size check. Any ideas to make it work better?
Is quota policy involved in CLI workflow? Again, can we make UI work the same way as CLI?
[1] https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img [2] https://github.com/cirros-dev/cirros/releases/download/0.5.1/cirros-0.5.1-x8... [3] https://github-production-release-asset-2e65be.s3.amazonaws.com/219785102/6e... [4] https://github.com/openstack/glance_store/blob/488d3e2fe31e4fc7a461e9de8b20d...
Thanks! Tony
As far as I know, Horizon is not using import workflow at all. Horizon needs to support import workflow in order to make UI work the same way as CLI.
Thanks & Best Regards, Abhishek Kekane
On Mon, Oct 26, 2020 at 7:35 PM Sean McGinnis sean.mcginnis@gmx.com wrote:
On 10/24/20 3:37 PM, Tony Liu wrote:
Hi,
The initial issue I saw was "The Store URI was malformed." from Horizon when creating image by URL [1].
It works fine with Glance CLI as the following.
glance image-create --container-format bare --disk-format qcow2 --name
cirros-test
glance image-import --import-method web-download --uri
https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img cirros-test
========
When I look into it, I see that UI and CLI work differently, they are handled by different workflow in Glance. Why is that? Why not UI follows the same workflow as CLI?
No input, but adding the [horizon] tag to the subject line to try to get the right set of eyes on it.
The root cause is that, [1] redirect to [2] and redirect to [3]. One issue here is that, query is not supported in [4]. pieces.query is dropped. When I attached query parameters, I got 403. And that's because, the workflow for UI is checking quota policy when adding location. It needs to get the size of image by HEAD request. But the signature in [3] is for GET request. So that HEAD request is forbidden by S3.
I don't think we can get an URL with signature for HEAD request in such case. So I go for an ugly workaround to skip the size check. Any ideas to make it work better?
Is quota policy involved in CLI workflow? Again, can we make UI work the same way as CLI?
[1] https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img [2]
https://github.com/cirros-dev/cirros/releases/download/0.5.1/cirros-0.5.1-x8...
[3]
https://github-production-release-asset-2e65be.s3.amazonaws.com/219785102/6e...
[4]
https://github.com/openstack/glance_store/blob/488d3e2fe31e4fc7a461e9de8b20d...
Thanks! Tony
participants (3)
-
Abhishek Kekane
-
Sean McGinnis
-
Tony Liu