| Summary: | anaconda failed to install repository NFS default | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tao Wu <twu> | ||||||||||
| Component: | kernel | Assignee: | Jeff Layton <jlayton> | ||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | rawhide | CC: | gansalmon, g.kaviyarasu, hoyang, itamar, jlayton, jonathan, kernel-maint, madhu.chinakonda, nfs-maint, sdharane, steved, twu, vanmeeuwen+fedora | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | Unspecified | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-02-28 14:03: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: | |||||||||||
| Attachments: |
|
||||||||||||
I found the anaconda can not mount NFS directory correctly, then I try to manually mount, but it failed finally. The screen shot is in the attachment. anaconda passes nolock to mount, so this is not the problem. Please attach /tmp/anaconda.log, /tmp/program.log, and /tmp/syslog after the failure to this bug. Thanks. Created attachment 562414 [details]
anaconda log
Created attachment 562415 [details]
program log
Created attachment 562416 [details]
syslog
The log files has been attached, thanks. This has still taken place on anaconda 17.8 . This is a kernel panic, which you can see from the attached syslog. That's not the problem. The stack trace is from a interaction with the
debugobjects code and slab ctor functions. This is a known problem. Here's the
upstream discussion thread:
http://www.spinics.net/lists/linux-nfs/msg26896.html
The warning is harmless, but I've proposed a patch to paper over the
problem. Still waiting on Trond to merge it at this point.
The real problem seems to be this message in the program.log:
07:31:20,403 ERR program: mount.nfs: access denied by server while mounting nfs.englab.nay.redhat.com:/pub/fedora/linux/development/17/i386
...but you'll need to do some troubleshooting to determine why the server
is refusing to allow you to mount.
(In reply to comment #9) > That's not the problem. The stack trace is from a interaction with the > debugobjects code and slab ctor functions. This is a known problem. Here's the > upstream discussion thread: > > http://www.spinics.net/lists/linux-nfs/msg26896.html > > The warning is harmless, but I've proposed a patch to paper over the > problem. Still waiting on Trond to merge it at this point. > > The real problem seems to be this message in the program.log: > > 07:31:20,403 ERR program: mount.nfs: access denied by server while mounting > nfs.englab.nay.redhat.com:/pub/fedora/linux/development/17/i386 > > ...but you'll need to do some troubleshooting to determine why the server > is refusing to allow you to mount. I have tried to mounting the server in the host system, and it successfully mounted, but in the kvm(which is running on the host system) it can not be mounted. (In reply to comment #10) > (In reply to comment #9) > > That's not the problem. The stack trace is from a interaction with the > > debugobjects code and slab ctor functions. This is a known problem. Here's the > > upstream discussion thread: > > > > http://www.spinics.net/lists/linux-nfs/msg26896.html > > > > The warning is harmless, but I've proposed a patch to paper over the > > problem. Still waiting on Trond to merge it at this point. > > > > The real problem seems to be this message in the program.log: > > > > 07:31:20,403 ERR program: mount.nfs: access denied by server while mounting > > nfs.englab.nay.redhat.com:/pub/fedora/linux/development/17/i386 > > > > ...but you'll need to do some troubleshooting to determine why the server > > is refusing to allow you to mount. > > I have tried to mounting the server in the host system, and it successfully > mounted, but in the kvm(which is running on the host system) it can not be > mounted. (In reply to comment #10) > (In reply to comment #9) > > That's not the problem. The stack trace is from a interaction with the > > debugobjects code and slab ctor functions. This is a known problem. Here's the > > upstream discussion thread: > > > > http://www.spinics.net/lists/linux-nfs/msg26896.html > > > > The warning is harmless, but I've proposed a patch to paper over the > > problem. Still waiting on Trond to merge it at this point. > > > > The real problem seems to be this message in the program.log: > > > > 07:31:20,403 ERR program: mount.nfs: access denied by server while mounting > > nfs.englab.nay.redhat.com:/pub/fedora/linux/development/17/i386 > > > > ...but you'll need to do some troubleshooting to determine why the server > > is refusing to allow you to mount. > > I have tried to mounting the server in the host system, and it successfully > mounted, but in the kvm(which is running on the host system) it can not be > mounted. Please try to set the network to bridge for the guest. At this point, I don't see any evidence of a NFS bug here. I'm going to go ahead and close this as NOTABUG. Please reopen it with an explanation if you feel that's incorrect. |
Created attachment 561491 [details] anaconda screen Description of problem: anaconda failed to install repository NFS default Version-Release number of selected component (if applicable): anaconda 17.7 How reproducible: 100% Steps to Reproduce: 1.Boot the installer using any available means (netinst.iso, pxeboot images or DVD.iso) 2.Direct anaconda to use NFS as the installation type by adding the boot command: askmethod 3.Choose NFS directory as Installation method when prompted. 4.Provide the hostname and path to the installation tree 5.Proceed with installation Actual results: Anaconda did not find the repository. Expected results: Anaconda uses the install repository from the NFS server provided. Additional info: