Bug 1109050
| Summary: | Multiple nsDS5ReplicaId attributes created in cn=replication,cn=etc | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Kosek <mkosek> |
| Component: | ipa | Assignee: | Martin Kosek <mkosek> |
| Status: | CLOSED ERRATA | QA Contact: | Namita Soman <nsoman> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.6 | CC: | mkosek, nsoman, pviktori, rcritten |
| Target Milestone: | rc | Flags: | nsoman:
needinfo+
|
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-3.0.0-40.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
When an RHEL 6 master is installed or upgraded,
it adds an extra default value to the nsDS5ReplicaId attribute of the LDAP entry cn=replication,cn=etc.
This does not happen when the first master is installed.
In RHEL 7.0, IPA has stricter validation which prevents installing an RHEL 7.0 replica on such a system (see also: bug 1108199).
Consequence:
After an RHEL 6 master is installed or upgraded on a system with more than one master, installing an RHEL 7.0 replica will fail.
Fix:
The extra value is no longer added.
Result:
After a replica with the fix is installed, RHEL 7.0 replicas can be installed successfully.
|
Story Points: | --- |
| Clone Of: | 910458 | Environment: | |
| Last Closed: | 2014-10-14 07:32:55 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: | 910458 | ||
| Bug Blocks: | |||
|
Comment 1
Martin Kosek
2014-06-13 07:38:52 UTC
Verified against ipa-server-3.0.0-42.el6.i686 [root@nocp9 ~]# ldapsearch -x -h $MASTER -D 'cn=Directory Manager' -w $ADMINPW -b cn=replication,cn=etc,$BASEDN | grep nsDS5ReplicaId nsDS5ReplicaId: 3 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. http://rhn.redhat.com/errata/RHBA-2014-1383.html |