Bug 449177
| Summary: | amd stops working after 5.2 update | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | matt whiteley <whiteley> | ||||
| Component: | am-utils | Assignee: | Ian Kent <ikent> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | qe-baseos-daemons | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 5.2 | CC: | azelinka, lmiksik, rwheeler | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-04-10 17:10:19 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: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 928849 | ||||||
| Attachments: |
|
||||||
|
Description
matt whiteley
2008-05-30 22:03:57 UTC
Created attachment 307243 [details]
log entries from a mount attempt
It appears that this only happens when the map contains netgrpd selectors. The machines have no trouble looking up netgroups though. Removing the netgrpd selectors made the mounts work again. We would like to be able to use those though. If there is any insight as to why this broke from upgrading unrelated packages that would be helpful. Matt, is this problem still reproducible with RHEL5.5? (In reply to comment #2) > It appears that this only happens when the map contains netgrpd selectors. > The machines have no trouble > looking up netgroups though. Removing the netgrpd selectors made the mounts > work again. We would > like to be able to use those though. If there is any insight as to why this > broke from upgrading unrelated > packages that would be helpful. I have taken on am-utils maintenance and noticed this bug but it is very old. If we are to make headway I will need some information to duplicate the issue. In particular an example of your am-utils configuration. Assuming of course this wasn't just a problem that has gone away since. Matt, can you get back to me please. |