action #19824
closed[sles][functional] Multiple tests time out because of a network issue on build0428 for ppc64le and aarch64 (was: failed uploading logs)
0%
Description
observation¶
Multiple tests fail because of a network issue on build0428 - failed uploading logs
x86_64
ppc64le
aarch64
- https://openqa.suse.de/tests/999194
- https://openqa.suse.de/tests/999167
- https://openqa.suse.de/tests/999159
workaround¶
retrigger job
Updated by mgriessmeier almost 7 years ago
- Related to action #19986: [sled] checksum failed when publishing cryptlvm hdd images added
Updated by mgriessmeier almost 7 years ago
happens also here
https://openqa.suse.de/tests/1014160
and here
https://openqa.suse.de/tests/1015047
probably related to https://progress.opensuse.org/issues/19986
Updated by okurz almost 7 years ago
- Subject changed from [sles][functional] Multiple tests fail because of a network issue on build0428 for ppc64le and aarch64 - failed uploading logs to [sles][functional] Multiple tests time out because of a network issue on build0428 for ppc64le and aarch64 (was: failed uploading logs)
Most of the jobs you mentioned are "incomplete" because the 2h timeout was hit so the problem is that either the test just takes this long and the MAX_JOB_TIME needs to be increased or some steps of the test now take longer than they should be. And that could be because of network problems, yes.
The following mentioned jobs fail for a different reason:
- https://openqa.suse.de/tests/999224/file/autoinst-log.txt fails because the qcow image could not be saved to the disk. See the "Checksum comparison (actual:expected) 4294967295:1424385091 with size (actual:expected) 0:10689445888". The 0 for "actual" size means that the disk image is 0 bytes big, as in, probably does not exist at all. The error message within openQA should be improved accordingly. Same for https://openqa.suse.de/tests/999167/file/autoinst-log.txt and https://openqa.suse.de/tests/1014160/file/autoinst-log.txt . See #16430 about that
Updated by okurz over 6 years ago
- Status changed from New to Rejected
We didn't see problems after that so let's assume it was an issue in our infrastructure related to network which was either fixing itself in time or fixed without us being informed about it.