-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix: Modify grub timeout in grub config directly #86
Conversation
[citest] |
regexp: '^GRUB_TIMEOUT=.*' | ||
replace: 'GRUB_TIMEOUT={{ bootloader_timeout }}' | ||
mode: "{{ __bootloader_grub_stat.stat.exists | | ||
ternary(__bootloader_grub_stat.stat.mode, '0644') }}" |
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.
Does one apply to the current kernel, and the other applies to new kernels?
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.
This is general, not applied to any kernel but to the system generally. This timeout happens before you use any kernel, actually.
[citest] |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #86 +/- ##
=========================================
+ Coverage 0 78.43% +78.43%
=========================================
Files 0 2 +2
Lines 0 255 +255
=========================================
+ Hits 0 200 +200
- Misses 0 55 +55
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Enhancement: Modify grub timeout in grub config directly
Reason: On RHEL 7, rebuilding grub config with grubby2-mkconfig has a bug that returns previously removed kernels
Result: This workaround doesn't require rebuilding grub config and hence avoids the bug