This is an update to the original Description above.

The qemu iotest 219 for -qcow2 fails intermittently on s390x with unexpected outputs. 

For example:

  Expected    ---> -{"return": [{"current-progress": 65536, "id": "job0", "status": "paused", "total-progress": 4194304, "type": "mirror"}]}
  Unexpected  ---> +{"return": [{"current-progress": 0, "id": "job0", "status": "paused", "total-progress": 0, "type": "mirror"}]}

  Expected    ---> -{"return": [{"current-progress": 131072, "id": "job0", "status": "running", "total-progress": 4194304, "type": "mirror"}]}
  Unexpected  ---> +{"return": [{"current-progress": 0, "id": "job0", "status": "running", "total-progress": 4194304, "type": "mirror"}]}

Reproduced upstream, I’ll send a patch.

Max

Closing qemu iotest BZs because the rpm build environment is not reliable and we're removing the run from %check (see bug 1742197).

We'll run the tests as part of our CI and track the failures using different BZs or tasks.

Some of these bugs are real and are worth fixing upstream, but there's no *need* to track them here. With that said, feel free to reopen the BZ if you *want* to track it.