You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As it stands, if the system_facts actor has an issue parsing /etc/default/grub, it will raise a StopActorExecutionError exception. This will cause the issue to not be reported as an inhibitor. Since this issue prevents the upgrade from proceeding, it would be preferable to have it reported as an inhibitor so it will be detected as such when running "preupgrade".
Steps to reproduce:
Start on a CentOS 7 with leapp installed and setup to upgrade to AlmaLinux 8
Add the following line to /etc/default/grub: "unset GRUB_TERMINAL_OUTPUT"
Run "leapp preupgrade"
The preupgrade will halt due to the grub file issue, the error will be displayed on the terminal, and will be reported in /var/log/leapp/leapp-report.json. But, it will not be flagged as an inhibitor. This means that any code that processes the leapp-report.json file will not see that there were any issues that would inhibit the upgrade.
Another, more comprehensive fix, for this issue and others would be to have the code that catches StopActorExecutionError exceptions to flag the issue as an inhibitor when writing them to the report file (since anything causing the exception to be thrown would inhibit an upgrade operation).
The text was updated successfully, but these errors were encountered:
As it stands, if the system_facts actor has an issue parsing /etc/default/grub, it will raise a StopActorExecutionError exception. This will cause the issue to not be reported as an inhibitor. Since this issue prevents the upgrade from proceeding, it would be preferable to have it reported as an inhibitor so it will be detected as such when running "preupgrade".
Steps to reproduce:
The preupgrade will halt due to the grub file issue, the error will be displayed on the terminal, and will be reported in /var/log/leapp/leapp-report.json. But, it will not be flagged as an inhibitor. This means that any code that processes the leapp-report.json file will not see that there were any issues that would inhibit the upgrade.
Another, more comprehensive fix, for this issue and others would be to have the code that catches StopActorExecutionError exceptions to flag the issue as an inhibitor when writing them to the report file (since anything causing the exception to be thrown would inhibit an upgrade operation).
The text was updated successfully, but these errors were encountered: