Bug 2125306
| Summary: | post-installation script can set an invalid value in DEFAULTKERNEL variable present in /etc/sysconfig/kernel | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Renaud Métrich <rmetrich> |
| Component: | kernel | Assignee: | Jan Stancek <jstancek> |
| kernel sub component: | Packaging | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Status: | CLOSED MIGRATED | Docs Contact: | |
| Severity: | low | ||
| Priority: | low | CC: | hkrzesin, lgoncalv, lzampier |
| Version: | 8.6 | Keywords: | MigratedToJIRA, Triaged |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-09-25 20:10:31 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Renaud Métrich
2022-09-08 14:48:43 UTC
(In reply to Renaud Métrich from comment #0) > Description of problem: > > This is somehow related to BZ #2125302. > The post-installation script for kernel-core has a sed line that changes > "kernel-smp" into "kernel". > Assuming DEFAULTKERNEL will still be considered (see related BZ #2125302), > the replacement value should not be "kernel" but "kernel-core". That's technically correct, but to hit this problem you'd need to be updating from RHEL4 (which appears to be last major release that had kernel-smp package, now EOL for 5+ years). Replacing kernel for kernel-core would make sense for the case of going RHEL6->RHEL8. This bug has been selected for migration from bugzilla to jira as part of our effort to pre-verify mass-migration tooling correctness. Please contact me (jarod) if any issues are encountered with this migration effort. If you need to test or create your jira account, see the following references for assistance: https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016394 https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016694 https://redhat.service-now.com/help?id=kb_article_view&sysparm_article=KB0016774 Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug. This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there. Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information. To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like: "Bugzilla Bug" = 1234567 In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information. |