Bug 2107752
| Summary: | autofs: send FAIL cmd/ioctl mess when encountering problems with mount trigger [rhel-7.9.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Thiago Rafael Becker <tbecker> |
| Component: | autofs | Assignee: | Ian Kent <ikent> |
| Status: | CLOSED ERRATA | QA Contact: | Kun Wang <kunwan> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.9 | CC: | dwysocha, ikent, kpfleming, ossantos, xzhou |
| Target Milestone: | rc | Keywords: | Triaged, ZStream |
| Target Release: | --- | Flags: | pm-rhel:
mirror+
|
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | autofs-5.0.7-116.el7_9.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-03-07 09:54:45 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Thiago Rafael Becker
2022-07-15 20:55:17 UTC
So far I don't think the business case is there to justify a larger patch backport to RHEL7. If nothing changes, given what we have, I'm inclined to close this WONTFIX. Support team, a few questions to answer: 1. Is it feasible for customer to upgrade to RHEL8 to avoid this bug? * NOTE that any bug encountered on RHEL7 will have a similar problem with getting fixed as the bar is higher for any fix to go to RHEL7 2. Is there any workaround for the customer? * NOTE: There is only one customer case on the RHEL8 bug, and one customer case here. So it's likely there's some contributing factor that is causing such issue to be hit repeatedly in the customer environment, and so if that can be identified then the customer can probably avoid this issue. (In reply to Dave Wysochanski from comment #8) > So far I don't think the business case is there to justify a larger patch > backport to RHEL7. If nothing changes, given what we have, I'm inclined to > close this WONTFIX. While the patch is a bit larger than we would normally allow it is fairly straight forward and has had quite a bit of soak time. OTOH I haven't looked to see if it would pull in dependent patches. > > Support team, a few questions to answer: > 1. Is it feasible for customer to upgrade to RHEL8 to avoid this bug? > * NOTE that any bug encountered on RHEL7 will have a similar problem with > getting fixed as the bar is higher for any fix to go to RHEL7 > > 2. Is there any workaround for the customer? > * NOTE: There is only one customer case on the RHEL8 bug, and one customer > case here. So it's likely there's some contributing factor that is causing > such issue to be hit repeatedly in the customer environment, and so if that > can be identified then the customer can probably avoid this issue. There isn't a workaround unfortunately. The log messages should mostly only appear if the customer is using direct mount maps. They might also appear for sub-mounts (it will take a bit more to work out if that is actually the case). If the customer is using amd maps with autofs they do make heavy use of sub-mounts. So we would also want to know what usage is causing the logs to fill up. AFAICS the log messages are error messages so they will be logged which is fairly annoying. So if we can verify the customer usage could be filling the logs we should apply this change (assuming there aren't dependent patches that make the change too large). Ian Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (autofs bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:1096 |