Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionJ.H.M. Dassen (Ray)
2011-02-14 11:48:57 UTC
2. What is the nature and description of the request?
The RHEL6 install Guide needs to be more specific on NFS Install from ISO
instructions.
It is not specific enough about what will need to be in the /images folder.
The ONLY two files to be in the directory are product.img and install.img
If the entire directory, files like pxeboot and trans.tbl are included, the
install fails.
Here is what does work:
I shared out a folder called /install with these contents:
[root@user etc]# cd /install
[root@user install]# ls -l
total 3351200
drwxrwxr-x. 2 user user 4096 Jan 26 17:26 images
-rw-rw-r--. 1 user user 3431618560 Sep 22 21:40 RHEL6.0-20100922.1-Server-x86_64-DVD1.iso
In the images folder I got ONLY install.img and product.img out of the Big
3.4gb iso/images folder and put them in:
[root@user images]# ls -l
total 125416
-rw-rw-r--. 1 user user 122527744 Sep 22 18:04 install.img
-rw-rw-r--. 1 user user 5898240 Sep 22 18:08 product.img
[root@user images]#
Here is my /etc/exports. I also disabled selinux and iptables for times sake:
[root@user images]# cat /etc/exports
/install *(ro)
I booted from the network install disk you get off the web site:
-rw-rw-r--. 1 user user 232761344 Jan 27 14:16 rhel-server-6.0-x86_64-boot.iso
This disk is like doing a linux askmethod.
I started the install from the disk, chose nfs directory,
NFS server name: 10.12.66.13
Red Hat Enterprise Linux Directory: /install
NFS Mount options (optional): I did not have any mount options. I was sharing
it out via my Fedora workstation.
The Graphical Installer launched and because the Product.img file was there I
was able to go through and pick what I needed and install from any of the
product categories.
3. Why does the customer need this? (List the business requirements here)
There is already a BZ out to have the iso be enough to do the install. It just
needs to be clearer about what needs to be in there. Maybe one of those red
alert boxes in there.
4. How would the customer like to achieve this? (List the functional
requirements here)
Just a blurb to explain that ONLY those two files should be in /images
5. For each functional requirement listed in question 4, specify how Red Hat
and the customer can test to confirm the requirement is successfully
implemented.
I tested this here at my desk
6. Is there already an existing RFE upstream or in Red Hat bugzilla?
BZ 584472 is related but is not a complaint about the Doc
7. How quickly does this need resolved? (desired target release)
we will get more calls about this I am sure.
8. Does this request meet the RHEL Inclusion criteria (please review)
[Empty]
9. List the affected packages
Just the install Doc
10. Would the customer be able to assist in testing this functionality if
implemented?
Just verify the Doc