action #109792
Updated by szarate about 2 years ago
There might be [cases](https://progress.opensuse.org/issues/106284) where it could be convenient to extract the logs via journal or serial console, due to limitations, network availability or simply convenience, for post processing. Ideally openQA would do something like: ``` cat EOF ---BEGIN OPENQA LOGFILE $test_module $log_filename --- $log ---END OPENQA LOGFILE $test_module $log_filename --- EOF > $serialdev ``` Ideally or something like this ``` `echo "MAKER" $( $log_string | gzip | base64encode) "END MAKER" > $serialdev` ``` Upon test completion, a program monitoring the [amqp events](https://open.qa/docs/#_configuring_amqp_message_emission) would parse the serial log, and split it into the multiple parts and upload the results to the corresponding job. It should, base64 encoding + gzip could be used to reduce the ammount of lines in the serial log. See https://amqp.opensuse.org for o3 and for OSD the URL is configured here: https://gitlab.suse.de/openqa/salt-pillars-openqa/-/blob/master/openqa/server.sls This would help further down the line, making investigation of isolated systems, or certain corner cases easier to debug. ## Constraints Use serial console, if it proves unreliable, system journal should be looked at (do mind the kernel rate limiting for messages)