Project

General

Profile

action #41228

os-autoinst fails executing qemu-img info on the qcow2 image

Added by SLindoMansilla almost 4 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Category:
Support
Target version:
-
Start date:
2018-09-19
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description


Related issues

Blocks openQA Tests - action #40319: [functional][u] test fails in gnucash - gnucash not closedResolved2018-08-282018-10-09

History

#1 Updated by EDiGiacinto almost 4 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

#2 Updated by SLindoMansilla almost 4 years ago

  • Blocks action #40319: [functional][u] test fails in gnucash - gnucash not closed added

#3 Updated by SLindoMansilla almost 4 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:~>

#4 Updated by SLindoMansilla almost 4 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:~>

#5 Updated by EDiGiacinto almost 4 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

#6 Updated by coolo almost 4 years ago

  • Status changed from New to Rejected

We don't have the capacity to debug your instance, sorry

#7 Updated by SLindoMansilla almost 4 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 Concrete Bugs to Support
  • Status changed from Rejected to In Progress
  • Assignee set to okurz
  • Priority changed from Normal to Low

#8 Updated by mitiao almost 4 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?

#9 Updated by SLindoMansilla almost 4 years ago

Info:

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"

#11 Updated by SLindoMansilla almost 4 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.

#12 Updated by JERiveraMoya almost 4 years ago

I have apparmor disabled in my workstation: http://dhcp42.suse.cz/tests/6/file/autoinst-log.txt

#13 Updated by SLindoMansilla almost 4 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.

Also available in: Atom PDF