Yedidyah Bar David created OVIRT-3063: ----------------------------------------- Summary: gtar Cannot write: Input/output error (was: Change in ovirt-system-tests[master]: pytest: he: Port 008_restart_he_vm.py to pytest) Key: OVIRT-3063 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-3063 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Hi all, On Tue, Nov 24, 2020 at 8:54 PM Code Review <gerrit(a)ovirt.org&gt; wrote: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/140... [ INFO ] TASK [ovirt.ovirt.hosted_engine_setup : Extract appliance to local VM directory] [ ERROR ] fatal: [localhost]: FAILED! => {"changed": false, "dest": "/var/tmp/localvm3i6cjs21", "extract_results": {"cmd": ["/usr/bin/gtar", "--extract", "-C", "/var/tmp/localvm3i6cjs21", "-z", "--show-transformed-names", "--sparse", "-f", "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"], "err": "/usr/bin/gtar: images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d: Cannot write: Input/output error\n/usr/bin/gtar: images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d: Cannot utime: Input/output error\n/usr/bin/gtar: images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d: Cannot change ownership to uid 0, gid 0: Input/output error\n/usr/bin/gtar: images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d: Cannot change mode to rwxr-xr-x: Input/output error\n/usr/bin/gtar: images/1519176a-e693-4425-b47b-7acfdd7f180b/4904ac49-1535-47d9-9d52-b803df4f869d.meta: Cannot open: Input/output error\n/usr/bin/gtar: Exiting with failure status due to previous errors\n", "out": "", "rc": 2}, "handler": "TgzArchive", "msg": "failed to unpack /usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova to /var/tmp/localvm3i6cjs21", "src": "/usr/share/ovirt-engine-appliance/ovirt-engine-appliance-4.4-20201124175128.1.el8.ova"} Other such failures already happened several times recently. Perhaps some disk-space issue? Or something similar? Thanks, -- Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100151)