action #41228
closedos-autoinst fails executing qemu-img info on the qcow2 image
Added by SLindoMansilla over 5 years ago. Updated over 5 years ago.
0%
Description
- Job incomplete: http://slindomansilla-vm.qa.suse.de/tests/11
- It happens also with apparmor disabled.
- The file mode should be no problem since I am able to run qemu-img info as _openqa-worker
Updated by EDiGiacinto over 5 years ago
This should have already been fixed in os-autoinst from master, can you try upgrading and confirm ? Seems you are running a version from august
Updated by SLindoMansilla over 5 years ago
- Blocks action #40319: [functional][u] test fails in gnucash - gnucash not closed added
Updated by SLindoMansilla over 5 years ago
It is already updated:
sergio@linux-qoz6:~> sudo zypper se -sx os-autoinst
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+-------------+------------+-------------------------------+--------+-----------------------------------
| os-autoinst | srcpackage | 4.5.1536921887.bc2a3782-113.1 | noarch | devel-openQA
i+ | os-autoinst | package | 4.5.1536921887.bc2a3782-113.1 | x86_64 | devel-openQA
v | os-autoinst | package | 4.5.1533739786.546c7c63-1.2 | i586 | openSUSE-Tumbleweed-Oss (20180820)
v | os-autoinst | package | 4.5.1533739786.546c7c63-1.2 | x86_64 | openSUSE-Tumbleweed-Oss (20180820)
sergio@linux-qoz6:~>
Updated by SLindoMansilla over 5 years ago
sergio@linux-qoz6:~> zypper lr --uri
Repository priorities are without effect. All enabled repositories share the same priority.
# | Alias | Name | Enabled | GPG Check | Refresh | URI
--+--------------+----------------------------------------+---------+-----------+---------+-----------------------------------------------------------------------------
1 | devel-openQA | devel-openQA | Yes | (r ) Yes | Yes | https://download.opensuse.org/repositories/devel:/openQA/openSUSE_Tumbleweed
2 | repo-debug | openSUSE-Tumbleweed-Debug | No | ---- | ---- | http://download.opensuse.org/debug/tumbleweed/repo/oss/
3 | repo-non-oss | openSUSE-Tumbleweed-Non-Oss (20180820) | Yes | (r ) Yes | Yes | http://download.tumbleweed.boombatower.com/20180820/repo/non-oss/
4 | repo-oss | openSUSE-Tumbleweed-Oss (20180820) | Yes | (r ) Yes | Yes | http://download.tumbleweed.boombatower.com/20180820/repo/oss/
5 | repo-source | openSUSE-Tumbleweed-Source | No | ---- | ---- | http://download.opensuse.org/source/tumbleweed/repo/oss/
6 | repo-update | openSUSE-Tumbleweed-Update | Yes | (r ) Yes | Yes | http://download.opensuse.org/update/tumbleweed/
sergio@linux-qoz6:~>
Updated by EDiGiacinto over 5 years ago
From your logs:
[2018-09-19T08:49:25.0121 CEST] [debug] Current version is 4.5.1533739786.546c7c63 [interface v13]
[2018-09-19T08:49:25.0161 CEST] [debug] git hash in /var/lib/openqa/share/tests/opensuse: 4c6228e1318cb95bf55afa67c998bf6d28482a72
[2018-09-19T08:49:25.0176 CEST] [info] Daemon reachable under http://*:20043/jeCm1l7Q0Wh_R9aZ/
[2018-09-19T08:49:25.0180 CEST] [info] Listening at "http://[::]:20043"
Server available at http://[::]:20043
Updated by coolo over 5 years ago
- Status changed from New to Rejected
We don't have the capacity to debug your instance, sorry
Updated by SLindoMansilla over 5 years ago
- Subject changed from [tools] os-autoinst fails executing qemu-img info on the qcow2 image to os-autoinst fails executing qemu-img info on the qcow2 image
- Category changed from Regressions/Crashes to Support
- Status changed from Rejected to In Progress
- Assignee set to okurz
- Priority changed from Normal to Low
Updated by mitiao over 5 years ago
from your log, it seems the cmd was wrong with a extra parameter in the end:
/usr/bin/qemu-img info --output=json /var/lib/openqa/share/factory/hdd/opensuse-15.0-x86_64-267.2-gnome@64bit.qcow2 1
where is the 1 come from?
Updated by SLindoMansilla over 5 years ago
Info:
- Not sure why the log showed an old version.
- The next jobs show the last version and still show the problem:
When manually running isotovideo as _openqa-worker, it works.
mitiao, good observation, I supposed it was the exit code of the command, since before upgrading os-autoinst, the error was "runcmd failed with exit code 1"
Updated by coolo over 5 years ago
https://bugzilla.redhat.com/show_bug.cgi?id=1609561 is at least related
Updated by SLindoMansilla over 5 years ago
My mistake.
I understood wrong how apparmor profiles work in connection with the systemd service.
coolo has proven that my problem was caused by apparmor in my current configuration.
Let's wait for jrivera's feedback on monday to determine if he was also hit by apparmor, since he has a regular webui/remote-worker setup.
Updated by JERiveraMoya over 5 years ago
I have apparmor disabled in my workstation: http://dhcp42.suse.cz/tests/6/file/autoinst-log.txt
Updated by SLindoMansilla over 5 years ago
- Status changed from In Progress to Resolved
Determined also the same problem on jrivera's machine.
Note for the future, even when apparmor service is inactive, if the profiles where activated on boot, they still have effect.
After disabling the service, a reboot is necessary.
A quick test would be to set profiles to a more permissive restriction, like aa-complain, and try if the job runs.