Bug 1410080

Summary: incompatible nsEncryptionConfig object definition prevents RHEL 7->6 schema replication
Product: Red Hat Enterprise Linux 7 Reporter: Marcel Kolaja <mkolaja>
Component: 389-ds-baseAssignee: Noriko Hosoi <nhosoi>
Status: CLOSED ERRATA QA Contact: Viktor Ashirov <vashirov>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.3CC: msauton, nhosoi, nkinder, pvoborni, rcritten, rmeggins, spoore, tbordaz, william
Target Milestone: rcKeywords: Regression, TestBlocker, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.3.5.10-15.el7_3 Doc Type: Bug Fix
Doc Text:
Bug: nsEncryptionConfig schema definition diverged between RHEL-7 and RHEL-6 Schema learning mechanism does not merge definition so the schema can not be pushed from RHEL-7 to 6. This triggers schema violation errors. Fix: Defines the RHEL-6 specific attribute types nsTLS10, nsTLS11 and nsTLS12 and add them to the allowed attributes list of nsEncryptionConfig in the RHEL-7 schema. Result: The schema replication from RHEL-7 to 6 has no more problem.
Story Points: ---
Clone Of: 1404443 Environment:
Last Closed: 2017-01-17 18:23:13 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: 1404443    
Bug Blocks:    

Description Marcel Kolaja 2017-01-04 12:16:32 UTC
This bug has been copied from bug #1404443 and has been proposed
to be backported to 7.3 z-stream (EUS).

Comment 7 errata-xmlrpc 2017-01-17 18:23:13 UTC
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://rhn.redhat.com/errata/RHBA-2017-0088.html

Comment 8 Nathan Kinder 2017-08-17 20:47:47 UTC
*** Bug 1218029 has been marked as a duplicate of this bug. ***