action #91287


yast installation: leverage loghost parameter

Added by lnussel almost 3 years ago. Updated 26 days ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
(Total: 0.00 h)


With the loghost parameter of linuxrc ( it's possible to send syslog messages to another host during installation. It does not only log what's actually logged but also sends yast logs and several other files via syslog:

That means it would be possible to collect log output in openqa live as it happens. So logs would even be available if something unexpectedly crashes during install. The post fail hook and explicit log collection steps could be made superfluous or at least radically simplified as no logs have to be uploaded manually anymore.

Getting syslog packets is rather easy, just open a udp port and listen to it. That can be done in few lines of perl. So the code that spawns qemu could do it. The loghost parameter support ip:port syntax, so each worker instance can have a separate syslog listener.

Subtasks 1 (0 open1 closed)

action #91410: Research on leverage loghost parameterRejected2021-04-20

Actions #1

Updated by riafarov almost 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Enhancement to existing tests)
  • Target version set to SLE 15 SP3
Actions #2

Updated by riafarov almost 3 years ago

  • Tracker changed from action to coordination
Actions #3

Updated by oorlov over 2 years ago

  • Target version changed from SLE 15 SP3 to Current
Actions #4

Updated by ybonatakis almost 2 years ago

I took some time to get some experience with it as part of another ticket considering the openqa logs.

A PoC i run included just a normal installation. With this, I imply that the following was not covered so far:

  • How to be used in a scenario with a preinstalled images
  • Collect other log files of interest
  • Isolation and representation of the logs in filesystem per job

Logging Server

and restart the service
(In additional i had also to disable the firewall to let incoming traffic talk to 415 port)

Clients and OpenQA

The concern is how to make the logs to be represented per job. The setup in the logging server logged everything in a file per host. But i havent gone through all the documentation[2][3] to explore all the options.
Another thing is how to include other files, but everything seems possible IMO


Actions #5

Updated by JERiveraMoya 2 months ago

  • Target version deleted (Current)
Actions #6

Updated by JERiveraMoya 2 months ago

  • Tracker changed from coordination to action
Actions #7

Updated by JERiveraMoya 2 months ago

  • Status changed from New to Rejected

Backlog clean-up.

Actions #8

Updated by lnussel 2 months ago

  • Status changed from Rejected to New

reject without any explanation?

Actions #9

Updated by JERiveraMoya 26 days ago

  • Status changed from New to Rejected

Also available in: Atom PDF