yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #83105
[Bug 1885003] [NEW] Interrupted copy-to-store may corrupt a subsequent operation
Public bug reported:
This is a hypothetical (but very possible) scenario that will result in
a corrupted image stored by glance. I don't have code to reproduce it,
but discussion seems to indicate that it is possible.
Scenario:
1. Upload image to glance to one store, everything is good
2. Start an image_import(method='copy-to-store') to copy the image to another store
3. Power failure, network failure, or `killall -9 glance-api`
4. After the failure, re-request the copy-to-store
5. That glance worker will see the residue of the image in the staging directory, which is only partial because the process never finished, and will start uploading that to the new store
6. Upon completion, the image will appear in two stores, but one of them will be quietly corrupted
** 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/1885003
Title:
Interrupted copy-to-store may corrupt a subsequent operation
Status in Glance:
New
Bug description:
This is a hypothetical (but very possible) scenario that will result
in a corrupted image stored by glance. I don't have code to reproduce
it, but discussion seems to indicate that it is possible.
Scenario:
1. Upload image to glance to one store, everything is good
2. Start an image_import(method='copy-to-store') to copy the image to another store
3. Power failure, network failure, or `killall -9 glance-api`
4. After the failure, re-request the copy-to-store
5. That glance worker will see the residue of the image in the staging directory, which is only partial because the process never finished, and will start uploading that to the new store
6. Upon completion, the image will appear in two stores, but one of them will be quietly corrupted
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/1885003/+subscriptions
Follow ups