This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2218911 - [DDF] Hi all, I wonder. Is there a reason why all this is not solved by single step as this:
Summary: [DDF] Hi all, I wonder. Is there a reason why all this is not solved by singl...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: Documentation
Version: unspecified
Hardware: All
OS: All
medium
unspecified
Target Milestone: rc
: ---
Assignee: Sagar Dubewar
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-30 14:27 UTC by Direct Docs Feedback
Modified: 2023-09-27 15:23 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-08 12:46:02 UTC
Type: ---
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   RHEL-2644 0 None Migrated None 2023-09-27 15:23:26 UTC
Red Hat Issue Tracker RHELPLAN-161354 0 None None None 2023-06-30 14:28:40 UTC

Description Direct Docs Feedback 2023-06-30 14:27:22 UTC 
Hi all, I wonder. Is there a reason why all this is not solved by single step as this:

```
%packages
-kernel
kernel-64k
%end
```

That is Anaconda recommended solution for installing just one kernel.

Reported by: jkonecny

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/performing_an_advanced_rhel_9_installation/installing-rhel-on-arm-with-kernel-64k_installing-rhel-as-an-experienced-user#annotations:9f30376c-673e-43d9-b635-bd64add0d6b6
Comment 1 Jiri Konecny 2023-06-30 14:35:33 UTC 
Feel free to ping me for more questions.

Pinging Gary and Sagar if you agree with the change.
Comment 12 Marta Lewandowska 2023-08-11 09:11:54 UTC 
I tried four scenarios: 

1)
%packages
@core
kernel-64k
@end

plus postscript from comment#8

2)
%packages
kernel-64k
@end

plus postscript from comment#8

3)
%packages
kernel-64k
@end

no postscript

4)
%packages
-kernel
kernel-64k
%end

no postscript

1 & 2 are equivalent: both kernels get installed, kernel-64k gets set to default
3: both kernels get installed, kernel gets set to default
in all three cases:
# cat /etc/sysconfig/kernel 
# UPDATEDEFAULT specifies if kernel-install should make
# new kernels the default
UPDATEDEFAULT=yes

# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel-core

4 (Jirka's suggestion): only kernel-64k gets installed
# cat /etc/sysconfig/kernel 
# UPDATEDEFAULT specifies if kernel-install should make
# new kernels the default
UPDATEDEFAULT=yes

# DEFAULTKERNEL specifies the default kernel package type
DEFAULTKERNEL=kernel-64k-core

So, DEFAULTKERNEL is only set correctly if one kernel gets installed.
https://github.com/rhinstaller/anaconda/blob/master/pyanaconda/modules/storage/bootloader/utils.py#L193

postscript is necessary to set the correct kernel as default in case more than one is installed.
Comment 16 RHEL Program Management 2023-09-08 12:42:24 UTC 
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.
Comment 17 RHEL Program Management 2023-09-08 12:46:02 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.