Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionMuhammad Aizuddin Bin Zali
2016-12-28 07:02:31 UTC
Description of problem:
Bootdisk only capably of generating initrd and kernel up to 30 chars. Anything more will break:
As example in /BOOT/:
RHEL_MINIMAL_7_3_X86_64_VMLINU
In isolinux.cfg:
KERNEL BOOT/RHEL_MINIMAL_7_3_X86_64_VMLINUZ
Missing "Z" character on VMLINUZ causing the bootdisk to break the installation.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Hosts > Operating Systems
2. Name the Operating Systems with long name more than 30 chars
3.
Actual results:
Expected results:
Operating systems naming should stop user from continue if the chars count is exceeding the bootdisk capability.
Additional info:
Hello, this is a duplicate of bug 1403393 which will be part of the upcoming minor release.
*** This bug has been marked as a duplicate of bug 1403393 ***