Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
(In reply to RHEL Program Management from comment #3)
> A request has been made to complete this BZ after the deadline. Please
> follow the instructions in this comment and answer all 3 questions. You can
> fill out this form by clicking the [reply] link on this comment, and then
> reply in-line to this message. Please do this even if you believe the case
> is obvious, or already covered in the BZ, as a way to make it easier for
> reviewers to approve this request.
>
> Verify the following information is set in the BZ: - Confirm the Release
> flag reflects the correct release - Set the Target Milestone field to
> Indicate when the work can be done (alpha, beta or rc).
>
> Prepare responsible parties to take action: - Verify the subsystem team
> indicated in the Pool field support a release exception - Ensure qa_ack+ and
> devel_ack+ are set and assignees are ready to complete the work by the
> Target Milestone. Answer the following 3 questions:
>
> 1. What is the impact of waiting until the next release to include this BZ?
> Reviewers want to know which RHEL features or customers are affected and if
> it will impact any Layered Product or Hardware partner plans.
Any autofs users that need to use quoted strings in autofs map entries (eg,
embedded spaces, some mount options, etc.) will encounter a program crash.
>
> 2. What is the risk associated with the fix? Reviewers want to know if the
> fix is contained, testable, and there is enough time to verify the work
> without impact the schedule or other commitments.
The risk is only that the program will crash in this use case.
However, having had a customer report this in RHEL-8, and the correction
verified by support testing (as well as the customer) the risk of side
effects or regressions of including the correction is low.
>
> 3. Provide any other details that should be weighed in making a decision
> (Other releases affected, upstream status, business impacts, etc).
A number of our customers are heavy autofs users, and this fault can have
very disruptive consequences. For example if autofs is used for user home
directories it can prevent users from logging in, if used in batch processing
such a animation (Pixar) or geophysics data processing (Chevron) this can
cause job failures that result in fairly significant productivity losses.
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-2020:5438