Bug 500084
Summary: | fstab entry works in FC10, fails in FC11 (requires a '.' after the server name) | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Leslie Brooks <no_cats2000> |
Component: | setup | Assignee: | Ondrej Vasik <ovasik> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | atkac, notting, ovasik, pknirsch, steved |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-03-22 17:55:20 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: |
Description
Leslie Brooks
2009-05-10 19:54:45 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping This does not appear to be a nfs-utils bug but more a DNS issue... But to be honest I'm not sure to whom I should reassign this to... Bill, would you have an idea on how to handle this?? Well, setup is probably not the best choice ... why did you choose it? I'll add Adam Tkac (bind maintainer) to cc , as probably he may help with this as well. How is this host name resolved - DNS? /etc/hosts? Other? > Well, setup is probably not the best choice ... why did you choose it?
I thought it was a parsing issue for /etc/fstab, so I did the following:
# rpm -qf /etc/fstab
setup-2.8.9-1.fc12.noarch
Ok, setup owns that file (and creates empty one), but anaconda/users/whatever modifies it. Anyway - I guess reporter should at least provide info from Comment #4, so setting needinfo. The host name is resolved by DNS. (In reply to comment #7) > The host name is resolved by DNS. Do you run BIND as a caching nameserver on that machine (and have "nameserver 127.0.0.1" in your /etc/resolv.conf)? Or do you use nameserver which doesn't run on the same machine. No, I don't run Bind on the machine; the host name is resolved by my router running DD-WRT. The router has a static IP address for the NFS server, but I don't use a domain. As there is not known where the problem is, I'm closing that bugzilla CANTFIX. It's not clear which component might be responsible for those issues, it might be either bug somewhere or some local configuration issue. I think it can't be resolved by setup component, so if you decide to reopen it, try to find out better component. I have no idea which one. |