Red Hat Bugzilla – Bug 1313798
Console output post ipa-winsync-migrate command should be corrected.
Last modified: 2016-11-04 01:51:30 EDT
Created attachment 1132253 [details]
Description of problem: ipa-migrate-winsync should be ipa-winsync-migrate.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install IPA-server on RHEL7.2.
2. Create a winsync agreement with Windows AD 2012R2
3. Now add two-way AD trust with same windows 2012R2 AD
4. Now run ipa-winsync-migrate in verbose mode.
winsync migration happens successfully. But the output displayed on the console mentions "The ipa-migrate-winsync command was successful"
There is no command as 'ipa-migrate-winsync'.
Change the output description to "The ipa-winsync-migrate command was successful"
Attaching the console log shown in verbose mode.
same issue(same root cause) is in `ipa-winsync-migrate --help` output.
7151ea394aac00ca596a8d7460a2fcefd258b36e fix incorrect name of ipa-winsync-migrate command in help
57e02c7140fe2ad6fe6a6bc9823f84500bb78732 fix incorrect name of ipa-winsync-migrate command in help
c68e9510d03abb75d353e209ea32ac9d1ed362bc fix incorrect name of ipa-winsync-migrate command in help
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see firstname.lastname@example.org with any questions
Fix is seen.
Verified using ipa-server-4.4.0-2.1.el7.x86_64 on RHEL7.3 Beta(Maipo)
ipa.ipaserver.install.ipa_winsync_migrate.WinsyncMigrate: DEBUG: Migrated: user4@PNE.QE
ipa.ipaserver.install.ipa_winsync_migrate.WinsyncMigrate: WARNING: Migration completed. Please note that if PassSync was configured on the given Active Directory server, it needs to be manually removed, otherwise it may try to reset password for accounts that are no longer existent.
ipa.ipaserver.install.ipa_winsync_migrate.WinsyncMigrate: INFO: The ipa-winsync-migrate command was successful
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.