Project

General

Profile

Actions
Copy link

action #27934

closed

[tools][expedite][sprint 201711.2] openQA-worker doesn't start because of error with db_profiler.pm

Added by SLindoMansilla about 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
EDiGiacinto
Category:
Feature requests
Target version:
-
Start date:
2017-11-20
Due date:
% Done:

100%

Estimated time:

Description

observation

When starting the worker service on an installed Leap 42.3 as on a docker container based on Leap 42.3, the worker fails to start showing the following error:

Can't locate db_profiler.pm:   Permission denied at /usr/share/openqa/script/../lib/OpenQA/Setup.pm line 26.
BEGIN failed--compilation aborted at /usr/share/openqa/script/../lib/OpenQA/Setup.pm line 26.
Compilation failed in require at /usr/share/openqa/script/../lib/OpenQA/Worker.pm line 33.
BEGIN failed--compilation aborted at /usr/share/openqa/script/../lib/OpenQA/Worker.pm line 33.
Compilation failed in require at /usr/share/openqa/script/worker line 106.
BEGIN failed--compilation aborted at /usr/share/openqa/script/worker line 106.

steps to reproduce

On Leap 42.3

  1. Install the package openQA-worker from repository http://download.opensuse.org/repositories/devel:/openQA/openSUSE_Leap_42.3 having also enabled http://download.opensuse.org/repositories/devel:/openQA:/Leap:/42.3/openSUSE_Leap_42.3
  2. Try to start a worker:
# systemctl start openqa-worker@1

OR

_openqa-worker$ /usr/share/openqa/script/worker --verbose --instance 1
  1. You will see the mentioned error output above.

problem

H1: REJECTED BY E1.2 The current version openQA-worker-4.5.1511164281.966cda56-22.1.noarch is producing the same error on all distributions.
H2: VERIFIED BY E2.1 The problem is related to apparmor.
H3: The problem is reproducible in other machine.

E1.1: Try a docker container with an image based on Tumbleweed and try to reproduce the error, following the steps.
R1.1: It fails running the container on the same machine.

E1.2: Try to reproduce the error, following the steps on a fresh installed Leap 42.3 on a different physical machine.
R1.2: It works on another machine.

E2.1: Try to start the worker with apparmor stopped.
R2.1: The worker works as expected.

E3.1: Find someone that have the same issue.
R3.1: qkzhu have the same issue.

E3.2: For qkzhu the worker also works trying with a stopped apparmor.
R3.2: Waiting for answer.

Actions
Copy link
 #1

Updated by SLindoMansilla about 7 years ago

  • Description updated (diff)
  • Status changed from New to Rejected
Actions
Copy link
 #2

Updated by qkzhu about 7 years ago

I also met this issue on my local instance, the worker service was installed on Leap42.2:

  • openQA-client-4.5.1511290893.c1143c32-24.1.noarch
  • openQA-common-4.5.1511290893.c1143c32-24.1.noarch
  • openQA-worker-4.5.1511290893.c1143c32-24.1.noarch
  • openQA-4.5.1511290893.c1143c32-24.1.noarch
  • os-autoinst-4.4.1511284591.d1020b93-470.1.x86_64
  • os-autoinst-openvswitch-4.4.1511284591.d1020b93-470.1.x86_64

Repositories:

Actions
Copy link
 #3

Updated by SLindoMansilla about 7 years ago

  • Status changed from Rejected to New

Reopened since I am not the only one having this problem.

Hello qkzhu,

I discovered that in my case the problem was related to apparmor. I haven't taken the time yet to investigate it.
To verify that you are having the same problem, could try shortly stop apparmor and try to start the worker?
If you don't see any error about db_profiler, we can confirmed the bug.

Actions
Copy link
 #4

Updated by SLindoMansilla about 7 years ago

  • Description updated (diff)
Actions
Copy link
 #5

Updated by EDiGiacinto about 7 years ago

Can't reproduce here.
Can you confirm the issue is gone when applying ( https://github.com/os-autoinst/openQA/pull/1504 ) to the apparmor profiles ?

Actions
Copy link
 #6

Updated by coolo about 7 years ago

  • Subject changed from [tools] openQA-worker doesn't start because of error with db_profiler.pm to [tools][ openQA-worker doesn't start because of error with db_profiler.pm
  • Status changed from New to Resolved

merged and confirmed to be fixed

Actions
Copy link
 #7

Updated by qkzhu about 7 years ago

  • Status changed from Resolved to In Progress

SLindoMansilla wrote:

Reopened since I am not the only one having this problem.

Hello qkzhu,

I discovered that in my case the problem was related to apparmor. I haven't taken the time yet to investigate it.
To verify that you are having the same problem, could try shortly stop apparmor and try to start the worker?
If you don't see any error about db_profiler, we can confirmed the bug.

The worker is working properly after stopping the apparmor, thanks.

Actions
Copy link
 #8

Updated by coolo about 7 years ago

  • Status changed from In Progress to Resolved

so why reopen?

Actions
Copy link
 #9

Updated by szarate about 7 years ago

  • Subject changed from [tools][ openQA-worker doesn't start because of error with db_profiler.pm to [tools][expedite][sprint 201711.2] openQA-worker doesn't start because of error with db_profiler.pm
  • % Done changed from 0 to 100
Actions
Copy link
 #10

Updated by szarate about 7 years ago

  • Assignee set to EDiGiacinto
Actions
Copy link

Also available in: Atom PDF