Bug 218330
Summary: | NFS with Kereberos completely broken on 2.6.18 and 2.6.19 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Paarvai Naai <opensource3141> |
Component: | kernel | Assignee: | Jeff Layton <jlayton> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Brian Brock <bbrock> |
Severity: | urgent | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | k.georgiou, steved, wtogami |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 2.6.20-ish kernels | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-01-24 21:44:24 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
Paarvai Naai
2006-12-04 18:34:33 UTC
This of course affects FC6. I suspect the beta of RHEL5 (although I can't check at the moment) will have the same problem as well. Yes, that's why I listed that the kernel SRPM include the patch and be released in FC5 and FC6. That's also a good point about RHEL 5. Can someone move this forward soon? Thanks! I haven't heard anything back from anyone about this bug. I've been fighting this problem for nearly two months and it's getting very frustrating, especially since 2.6.17 has now been removed from the fc5 updates repository!!! This has caused considerable inconvenience for our company since we use NFSv3+Kerberos and need to have machines installed with a properly working kernel. I am unable to increase the urgency field past "Urgent", so can someone help me out. Thanks. Cloning the bug to FC6 and possibly RHEL5b2 might help there. It usually takes some time before that bug is assigned to anyone but lack of activity in bugzilla doesn't necessarily mean that someone isn't looking at it right now. Sorry it's taken so long to get to this bug. It sounds like there was an upstream fix to this problem in 2.6.20 or so? In any case, I believe this bug to fixed at this point. Please reopen it if you're still experiencing this problem with the most current kernel from F7 or later releases. |