Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Save the Bug ID in system logs when Anaconda reports crashes to Bugzilla. #766

Open
lruzicka opened this issue Oct 12, 2022 · 0 comments
Open

Comments

@lruzicka
Copy link

lruzicka commented Oct 12, 2022

I am trying to automate an openQA test that would be able to cause Anaconda to crash, report the bug to Bugzilla, check that it exists there and then close it to clean up. However, I am struggling to get the bug id programmatically, as it does not show anywhere in the log files.

The bug number is known to the process, because it is shown in the UI and it apparently also emerges in a temporary event log file which is available until the bug reporting wizard gets closed. Then it disappears.

On GUI, I we have managed to work around this problem by leaving the window open and then we could collect the bug number, but this approach does not work in the text installation mode, because the process finishes without any user interaction.

Please, save the bug ID in an exact location where it could be accessed after the bug has been reported and Anaconda closed, either in journalctl, /var/logs or similar location.

The workflow I am using:

  1. Start the installation process, either in graphical or text mode.
  2. Switch to a root console and run kill -USR1 'cat /var/run/anaconda.pid' to crash Anaconda.
  3. Switch back to Anaconda and use the UI to report a bug to Fedora maintainers.
  4. The bug gets created and the ID is shown in the UI.
  5. Then I would like to query Bugzilla if it is there (not possible as I do not have the bug ID - openQA has no way to detect visual elements and convert it to strings or numbers)
  6. And close the bug in Bugzilla (not possible).

Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant