Bug 1383910 – Incorrect autofs.schema

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 1383910 - Incorrect autofs.schema

Summary:	Incorrect autofs.schema

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	autofs (Show other bugs)
Sub Component:
Version:	7.2
Hardware:	Unspecified Unspecified

Priority	low Severity low
Target Milestone:	rc
Target Release:	---
Assigned To:	Ian Kent
QA Contact:	xiaoli feng
Docs Contact:	Milan Navratil

URL:
Whiteboard:
Keywords:

Depends On:	703846
Blocks:
	Show dependency tree / graph

Reported:	2016-10-12 02:56 EDT by Ian Kent
Modified:	2017-08-01 08:43 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	autofs-5.0.7-59.el7
Doc Type:	Bug Fix
Doc Text:	The _autofs_ package now contains the `README.autofs-schema` file and an updated schema The `samples/autofs.schema` distribution file was out of date and incorrect. As a consequence, it is possible that somebody is using an incorrect LDAP schema. However, a change of the schema in use cannot be enforced. With this update: * The `README.autofs-schema` file has been added to describe the problem and recommend which schema to use, if possible. * The schema included in the _autofs_ package has been updated to `samples/autofs.schema.new`.
Story Points:	---
Clone Of:	703846
Environment:
Last Closed:	2017-08-01 08:43:52 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2017:2213	normal	SHIPPED_LIVE	autofs bug fix and enhancement update	2017-08-01 12:09:35 EDT

Groups: None (edit)

Comment 3 errata-xmlrpc 2017-08-01 08:43:52 EDT

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, 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-2017:2213

Note You need to log in before you can comment on or make changes to this bug.