-
Notifications
You must be signed in to change notification settings - Fork 146
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
Handle default kernel cmdline if multiple boot entries for the default kernel are defined #1302
Handle default kernel cmdline if multiple boot entries for the default kernel are defined #1302
Conversation
Thank you for contributing to the Leapp project!Please note that every PR needs to comply with the Leapp Guidelines and must pass all tests in order to be mergeable.
Packit will automatically schedule regression tests for this PR's build and latest upstream leapp build.
Note that first time contributors cannot run tests automatically - they need to be started by a reviewer. It is possible to schedule specific on-demand tests as well. Currently 2 test sets are supported,
See other labels for particular jobs defined in the Please open ticket in case you experience technical problem with the CI. (RH internal only) Note: In case there are problems with tests not being triggered automatically on new PR/commit or pending for a long time, please contact leapp-infra. |
/packit copr-build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. note that failed IPU 7 -> 8 tests are invalid.
Tested manually, kind of it works but I found that our solution is not good for such a setup - affecting all major IPU paths. Reproducer:
Result
and in the report:
Note that in this case, this has been kind of expected behaviour as the process is expecting to see just one bootloader entry for the target kernel and in case that multiple entries exists, we are not sure which value to set. However, thinking about machines with |
The missing `leapp.reporting.Report` class is added to kernelcmdlineconfig actor `produces` tuple.
e1807bf
to
750ad95
Compare
repos/system_upgrade/common/actors/kernelcmdlineconfig/libraries/kernelcmdlineconfig.py
Outdated
Show resolved
Hide resolved
repos/system_upgrade/common/actors/kernelcmdlineconfig/libraries/kernelcmdlineconfig.py
Outdated
Show resolved
Hide resolved
repos/system_upgrade/common/actors/kernelcmdlineconfig/libraries/kernelcmdlineconfig.py
Outdated
Show resolved
Hide resolved
repos/system_upgrade/common/actors/kernelcmdlineconfig/libraries/kernelcmdlineconfig.py
Outdated
Show resolved
Hide resolved
df3bc99
to
67f0a47
Compare
67f0a47
to
3ae95f4
Compare
…are listed Instead of erroring out when grubby lists multiple entries for the default kernel, always use the `args=` and `root=` from the first one and create a post-upgrade report. The report instruct user to ensure those are the correct ones or to correct them. This can happen, for example, if MAKEDEBUG=yes is set in /etc/sysconfing/kernel. Jira: RHEL-46911
3ae95f4
to
95f9b3e
Compare
Test results from 8->9:
From /var/log/leapp/leapp-report.txt
From /var/log/leapp/leapp-upgrade.log:
|
Instead of erroring out when grubby lists multiple entries for the
default kernel, always use the
args=
androot=
from the first one and createa post-upgrade report. The report instruct user to ensure those are the
correct ones or to correct them.
This can happen, for example, if MAKEDEBUG=yes is set in
/etc/sysconfing/kernel.
Also the missing
leapp.reporting.Report
class is added to kernelcmdlineconfig actorproduces
tuple.Jira: RHEL-46911