Bug 537067

Summary: Not probably to spend network installation fedora 12 (beta) from a NFS-server
Product: [Fedora] Fedora Reporter: Alex <alex-saf>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: anaconda-maint-list, rvykydal, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-12 19:23:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
photo-2
none
photo-3
none
photo-4
none
photo-5
none
photo-6
none
photo-7
none
photo-8
none
photo-9
none
photo-1 none

Description Alex 2009-11-12 11:28:12 UTC
Description of problem:
At network installation fedora 12 (beta) on the computer using PXE it is impossible to spend installation from a NFS-server. The network resource is not mounted. Besides, at network installation not probably to set Russian though earlier (fedora 8,9,10,11) it could be made.
Nevertheless it is possible to spend installation with web-server usage.

Version-Release number of selected component (if applicable):
1. Install DVD Fedora 12 (beta) for reception initrd.img, vmlinuz (from a
directory .../images/pxeboot)
2. syslinux-3.75-4.fc12.i686.rpm (Fedora Development for i386) for reception
pxelinux.0

How reproducible:


Steps to Reproduce:
1. Begin network installation fedora 12 (beta) (see photo-1.JPG)
2. Select for installation Russian (see photo-2.JPG). There is an error (see photo-3.JPG). Why?
3. Select NFS directory (see photo-4.JPG). Select "Manual configuration" from customisations TCP/IP (see photo-5.JPG).
4. After definition of network customisations enter parametres of a NFS-server (192.168.1.254) and a shared directory /var/www/html/linux/f12/i386/install (see photo-6.JPG). Press "Ok"
5. Error! The network resource is not mounted (see photo-7.JPG).
6. Switch Alt-F4 (see net-8.JPG)
7. Switch Alt-F3 (see net-9.JPG)
  
Actual results:
No install

Expected results:


Additional info:
DCHP-,TFTP anf NFS-servers work on computer:
1) OS - Fedora 7
2) Files for loading are on the patch:
/tftpboot/linux/f12/i386
3) List files:
initrd.img  pxelinux.0  vmlinuz
4) List /tftpboot/linux/f12/i386/pxelinux.cfg:
default
5) cat /tftpboot/linux/f12/i386/pxelinux.cfg/default
DEFAULT pxeboot
TIMEOUT 50
LABEL pxeboot
      KERNEL vmlinuz
      APPEND initrd=initrd.img
ONERROR LOCALBOOT 0

6) exportfs
....
/var/www/html/linux/f12/i386/install
                192.168.1.0/24
....
/var/www/html/linux/f12/i386/install
                <world>
....

Comment 1 Alex 2009-11-12 11:30:00 UTC
Created attachment 369185 [details]
photo-2

Comment 2 Alex 2009-11-12 11:31:51 UTC
Created attachment 369188 [details]
photo-3

Comment 3 Alex 2009-11-12 11:32:34 UTC
Created attachment 369189 [details]
photo-4

Comment 4 Alex 2009-11-12 11:33:36 UTC
Created attachment 369190 [details]
photo-5

Comment 5 Alex 2009-11-12 11:34:24 UTC
Created attachment 369191 [details]
photo-6

Comment 6 Alex 2009-11-12 11:35:52 UTC
Created attachment 369192 [details]
photo-7

Comment 7 Alex 2009-11-12 11:36:55 UTC
Created attachment 369193 [details]
photo-8

Comment 8 Alex 2009-11-12 11:37:59 UTC
Created attachment 369194 [details]
photo-9

Comment 9 Alex 2009-11-12 11:39:33 UTC
Created attachment 369195 [details]
photo-1

Comment 10 Radek Vykydal 2009-11-12 13:49:36 UTC
This looks like duplicate of bug #528537 that should be fixed post-beta. Could you please try if this workaround: https://bugzilla.redhat.com/show_bug.cgi?id=528537#c4 on the NFS server side works for you?

Comment 11 Alex 2009-11-12 19:08:09 UTC
yes,

1) on the NFS-server, add string RPCNFSDARGS="-N 4" in file /etc/sysconfig/nfs

2) reboot NFS-server

3) Has booted successfully, but as a result there is a same error as well as in Bug 537175

Comment 12 Chris Lumens 2009-11-12 19:23:07 UTC

*** This bug has been marked as a duplicate of bug 528537 ***