Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem: ipa-migrate-winsync --log-file option doesn't work
Version-Release number of selected component (if applicable):
How reproducible: Always.
Steps to Reproduce:
1. Establish Winsync agreement.
2. Now remove Winsync agreement by giving the --log-file option.
ipa-winsync-migrate -v --realm=TEST.IN --server=win01.test.in --log-file=/tmp/test1.txt
Actual results:
root@ipa01 ipa]# ipa-winsync-migrate -v --realm=TEST.IN --server=win01.test.in --log-file=/tmp/test1.txt
ipa.ipalib.plugins.trust.trust_show: DEBUG: raw: trust_show(u'TEST.IN', version=u'2.156')
ipa.ipalib.plugins.trust.trust_show: DEBUG: trust_show(u'TEST.IN', rights=False, all=False, raw=False, version=u'2.156')
ipa.ipapython.ipaldap.SchemaCache: DEBUG: retrieving schema for SchemaCache url=ldapi://%2fvar%2frun%2fslapd-LABS01-TEST.socket conn=<ldap.ldapobject.SimpleLDAPObject instance at 0x2d45ea8>
ipa.ipapython.ipaldap.SchemaCache: DEBUG: flushing ldaps://ipa01.labs01.test:636 from SchemaCache
ipa.ipapython.ipaldap.SchemaCache: DEBUG: retrieving schema for SchemaCache url=ldaps://ipa01.labs01.test:636 conn=<ldap.ldapobject.SimpleLDAPObject instance at 0x4d6f4d0>
Expected results: When the --log-file file option is used the output should be written to the log file mentioned which isn't happening in the above case.
Additional info:
This is working as expected. When using --log-file, the command option validation is not written to the log file (it would be a nuisance to have to open the log file to find out why the command failed). Since the command in the example is also invoked with the verbose flag, the debug output originated during the command option validation is produced to the console.