Project

General

Profile

coordination #91287

yast installation: leverage loghost parameter

Added by lnussel almost 2 years ago. Updated 7 months ago.

Status:
New
Priority:
Low
Assignee:
-
Target version:
Start date:
2021-04-20
Due date:
% Done:

0%

Estimated time:
(Total: 0.00 h)

Description

With the loghost parameter of linuxrc (https://en.opensuse.org/SDB: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: https://github.com/openSUSE/installation-images/blob/master/data/initrd/etc/rsyslog.d/logged_files.conf

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

action #91410: Research on leverage loghost parameterNew

History

#1 Updated by riafarov almost 2 years ago

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

#2 Updated by riafarov almost 2 years ago

  • Tracker changed from action to coordination

#3 Updated by oorlov over 1 year ago

  • Target version changed from SLE 15 SP3 to Current

#4 Updated by ybonatakis 7 months 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

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

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

[0] https://github.com/openSUSE/installation-images/blob/master/data/initrd/scripts/remote_log_setup
[1] http://aquarius.suse.cz/tests/11187
[2] https://www.syslog-ng.com/technical-documents/download/downloads?id=6091313
[3] http://www.softpanorama.org/Logs/Syslog_ng/configuration_examples.shtml

Also available in: Atom PDF