Bug 783270

Summary: When migrating warn user if compat is enabled
Product: Red Hat Enterprise Linux 6 Reporter: Dmitri Pal <dpal>
Component: ipaAssignee: Rob Crittenden <rcritten>
Status: CLOSED ERRATA QA Contact: IDM QE LIST <seceng-idm-qe-list>
Severity: unspecified Docs Contact:
Priority: low    
Version: 6.3CC: jgalipea, mkosek, stanislav.polasek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-2.2.0-4.el6 Doc Type: Bug Fix
Doc Text:
No documentation needed.
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-06-20 13:30:23 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:

Description Dmitri Pal 2012-01-19 20:21:27 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/2274

The compat plugin just adds overhead to migration. We should check to see if it is enabled when a migration is done and warn that it should be disabled (ideally with an interactive "Do you want to continue?")

Comment 1 Rob Crittenden 2012-03-01 16:41:01 UTC
fixed upstream.

master: 73249140fce64e56ddf5cd70441804a627b0cc34

ipa-2-2: 23134479f6fb5aa79486987992f8c245522feca8

If compat is enabled you'll need to add the--with-compat option to migrate.

If compat is disabled there should be no option required.

Comment 3 Martin Kosek 2012-03-09 11:32:58 UTC
Unfortunately, I found a bug in compat plugin check which needs to be fixed before verification:

https://fedorahosted.org/freeipa/ticket/2508

I will move the bug back to ASSIGNED.

Comment 4 Rob Crittenden 2012-03-12 21:00:02 UTC
fixed upstream.

master: 0cb9882be9dc13781fb566df11df8bb962ea1ca9

ipa-2-2: 26b968c993ba65414d08e3d58991826cd229ed91

Comment 6 Jenny Severance 2012-03-19 18:55:07 UTC
Verified ::

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: bz783270 Warn if compat plugin is enabled
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: EXECUTING: echo Secret123 | ipa-compat-manage enable
:: [   PASS   ] :: Running 'echo Secret123 | ipa-compat-manage enable'
:: [   PASS   ] :: Restarting directory server
:: [   LOG    ] :: EXECUTING : echo Secret123 | ipa migrate-ds ldap://dhcp-187-227.bos.redhat.com:389
:: [   PASS   ] :: Running 'echo Secret123 | ipa migrate-ds ldap://dhcp-187-227.bos.redhat.com:389 > /tmp/compatenabled.out 2>&1'
:: [   PASS   ] :: File '/tmp/compatenabled.out' should contain 'The compat plug-in is enabled.'
:: [   LOG    ] :: Duration: 11s
:: [   LOG    ] :: Assertions: 4 good, 0 bad
:: [   PASS   ] :: RESULT: bz783270 Warn if compat plugin is enabled

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: [   LOG    ] :: bz783270 Migrate with compat plugin enabled
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

:: [   LOG    ] :: EXECUTING: echo Secret123 | ipa migrate-ds --with-compat ldap://dhcp-187-227.bos.redhat.com:389
:: [   PASS   ] :: Migrating with compat plugin enabled
:: [   PASS   ] :: Verifying puser1 was migrated
:: [   PASS   ] :: Verifying user 'puser2' was migrated
:: [   PASS   ] :: Verifying group 'group1' was migrated
:: [   PASS   ] :: Verifying group 'group2' was migrated
:: [   LOG    ] :: Cleaning up migrated users
:: [   LOG    ] :: Duration: 19s
:: [   LOG    ] :: Assertions: 5 good, 0 bad
:: [   PASS   ] :: RESULT: bz783270 Migrate with compat plugin enabled


version ::
ipa-server-2.2.0-4.el6.x86_64

Comment 8 Martin Kosek 2012-04-20 11:40:08 UTC
    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
No documentation needed.

Comment 10 errata-xmlrpc 2012-06-20 13:30:23 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.

http://rhn.redhat.com/errata/RHBA-2012-0819.html