yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #93095
[Bug 2043784] [NEW] Image download fails with corrupt image hash mismatch
Public bug reported:
Glance backend is Cinder and Cinder backend is RBD
Reproducer:
1. Create a volume from image (cirros in my case)
2. Launch an instance from the bootable volume
3. write a sparse file to the volume
dd if=/dev/zero of=sparsefile bs=1M count=1 seek=1K
4. Delete the instance (needed for next operation)
5. Upload the volume to image (only possible if volume is in available state)
6. Download the image
glance image-download <image-id> --file testfile.img
We hit the following error
[Errno 32] Corrupt image download. Hash was
684f9d8384ad816dbe9cdb2b7250da1304e4dda5a796d572fb4d682d38bab699c39586cef4ad175573bdcbfc9829100795772d96fe164fcc284748db442db5a1
expected
1379e418b9f00dd6b7ca0d9c3464f06c1a8eb4f6ed8073ae615275007636dc064f15a8b33404dfc53b7613a0517f4ab71be7aca3f391e0452da9bb2e98f503a6
I think it might be due to the inconsistency writing the sparse files.
** Affects: glance
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Glance.
https://bugs.launchpad.net/bugs/2043784
Title:
Image download fails with corrupt image hash mismatch
Status in Glance:
New
Bug description:
Glance backend is Cinder and Cinder backend is RBD
Reproducer:
1. Create a volume from image (cirros in my case)
2. Launch an instance from the bootable volume
3. write a sparse file to the volume
dd if=/dev/zero of=sparsefile bs=1M count=1 seek=1K
4. Delete the instance (needed for next operation)
5. Upload the volume to image (only possible if volume is in available state)
6. Download the image
glance image-download <image-id> --file testfile.img
We hit the following error
[Errno 32] Corrupt image download. Hash was
684f9d8384ad816dbe9cdb2b7250da1304e4dda5a796d572fb4d682d38bab699c39586cef4ad175573bdcbfc9829100795772d96fe164fcc284748db442db5a1
expected
1379e418b9f00dd6b7ca0d9c3464f06c1a8eb4f6ed8073ae615275007636dc064f15a8b33404dfc53b7613a0517f4ab71be7aca3f391e0452da9bb2e98f503a6
I think it might be due to the inconsistency writing the sparse files.
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/2043784/+subscriptions