action #54485

worker can not read out worker class and reverts to default

Added by okurz 9 months ago. Updated 7 months ago.

Status:ResolvedStart date:20/07/2019
Priority:NormalDue date:
Assignee:mkittler% Done:

0%

Category:Support
Target version:Done
Difficulty:
Duration:

Description

Observation

On lord.arch, on current git master (6a8f9a53) I observed that starting a worker shows:

$ sudo -u _openqa-worker nice -n 4 ./script/worker --instance 10 --isotovideo /local/os-autoinst/isotovideo --verbose --no-cleanup
[info] [pid:1020] worker 10:
 - worker hostname:       lord
 - isotovideo version:    14
 - websocket API version: 1
 - web UI hosts:          localhost
 - class:                 ?

so seemingly unable to readout the worker class from the config file which has:

[10]
WORKER_CLASS = qemu_x86_64_sle

History

#1 Updated by mkittler 9 months ago

  • Status changed from New to In Progress
  • Assignee set to mkittler
  • Target version set to Current Sprint

I guess that's because the worker class is inside an instance section.

#2 Updated by mkittler 9 months ago

Works for me, though. I need your full config.

#3 Updated by coolo 9 months ago

The worker class is basically in most workers in the instance config

#4 Updated by mkittler 9 months ago

That's true and it also works for me locally. I needed the config @okurz is using no check. By the way, are you sure the right config is loaded (e.g. OPENQA_CONFIG might point to the wrong place)?

#5 Updated by mkittler 9 months ago

  • Status changed from In Progress to Feedback

#6 Updated by okurz 9 months ago

at best just tell me which ssh key to add.

#7 Updated by okurz 9 months ago

Starting the worker over the systemd service yields the same. Also, trying with

sudo -u _openqa-worker strace -f -eopen nice -n 4 ./script/worker --instance 10 --isotovideo /local/os-autoinst/isotovideo --verbose --no-cleanup >strace_open 2>&1

to find attempts to open a worker config actually shows no hits on /etc/openqa whatsoever.

#8 Updated by mkittler 9 months ago

  • Status changed from Feedback to In Progress

The [global] section in your config is out-commented and our INI parser doesn't like settings outside a section. So I'd just say your config is invalid. I'm going to create a PR for showing parsing errors and the location of the config file in the setup summary printed on worker startup.

#10 Updated by mkittler 8 months ago

  • Status changed from In Progress to Resolved

PR has been merged

#11 Updated by mkittler 7 months ago

  • Target version changed from Current Sprint to Done

Also available in: Atom PDF