overcloud image processing doesn't fail if the source qcow2 is empty

Bug #1943055 reported by Alex Schultz
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Triaged
Medium
Unassigned

Bug Description

If the source qcow2 for the image upload is empty (bytes 0), we convert it to a 0 byte raw file rather than errorring that the file not valid when processing it.

Changed in tripleo:
status: New → Triaged
importance: Undecided → Medium
milestone: none → xena-3
Revision history for this message
Julia Kreger (juliaashleykreger) wrote :

https://paste.opendev.org/show/809178/ shows the deconstruction of the referenced image which is not zero bytes. I'm suspecting something environmental is in play here, but until we have logs and actual failures recorded, I'm thinking something else yet identified is going on.

Revision history for this message
Julia Kreger (juliaashleykreger) wrote :

Chatted with Alex more. So the issue was a zero byte qcow2 file going into qemu-img convert. If this happens, it returns an exit code of "0" and creates a zero byte raw file. My best guess is it thinks it is actually reading a raw input as there is no header. It creates the output file which is also zero bytes. Anyhow, I've confirmed this is the case manually.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.