Description of problem:
The schema bundled with autofs in RHEL 6.0 suffers from BZ #584808, c+p below:
The autofs.schema file bundled with openldap-servers incorrectly uses OID
18.104.22.168.22.214.171.124 for objectclass automount. Only attributes are meant to appear
under 126.96.36.199.1.1.1 so an objectclass cannot use this range. Also this OID is
already (and correctly) assigned to the attribute memberNisNetgroup.
Version-Release number of selected component (if applicable):
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
(In reply to comment #0)
> Description of problem:
> The schema bundled with autofs in RHEL 6.0 suffers from BZ #584808, c+p below:
So your asking for the schema in the upstream package to be
replaced with the one in bug 584808?
(In reply to Ian Kent from comment #3)
> (In reply to comment #0)
> > Description of problem:
> > The schema bundled with autofs in RHEL 6.0 suffers from BZ #584808, c+p below:
> So your asking for the schema in the upstream package to be
> replaced with the one in bug 584808?
(In reply to Steve Whitehouse from comment #16)
> Removing it upstream seems reasonable to me. Doing it in RHEL6 at this stage
> is probably not a good plan, in case it surprises someone, since it has been
> there a long time, no doubt. Perhaps some documentation to explain where the
> newer one(s) can be found would be one way out of this? In that case we
> could change this to a doc bug I think.
Yeah, good point.
I could add a README.autofs.schema to /usr/share/doc/autofs
which basically says don't use this it isn't correct and
specify the recommended schema names.
I believe the rfc3207* schema are readily available in LDAP
servers (even Windows uses rfc2307 in their Unix extensions)
and have been for a long time now so I'm reluctant to include
copies in autofs or anywhere really.
I'm also not sure that people should be encouraged to use
specific schema when they should be included and maintained
within the particular LDAP product.
I'd prefer to say something to that effect in the README above.
If people do have a problem I could provide schema definitions
on request (and say that in the above README).
Created attachment 1209498 [details]
Patch - update and add README for old autofs schema
Fixed autofs.schema.new not copied to rpm package.
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.