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.
Bug 1283879 - ipa-winsync-migrate: Traceback message should be replaced by "IPA is not configured on this system"
Summary: ipa-winsync-migrate: Traceback message should be replaced by "IPA is not conf...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-20 07:28 UTC by Sudhir Menon
Modified: 2016-11-04 05:40 UTC (History)
3 users (show)

Fixed In Version: ipa-4.4.0-0.el7.1.alpha1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 05:40:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Sudhir Menon 2015-11-20 07:28:17 UTC 
Description of problem: When ipa-winsync-migrate command is run on the system which is not yet configured as ipa-server, the traceback message displayed on the console should be replaced with user-friendly message saying that 'IPA is not configured on this system'

Version-Release number of selected component (if applicable): 7.2

How reproducible:Always, when IPA server is not configured on the system

Steps to Reproduce:
1. Login to RHEL7.2
2. Run "yum install ipa-server ipa-server-trust-ad"
3. Ensure "ipa-server-install" is not run.
4. Now do "ipa-winsync-migrate"
5. Now do "ipa-adtrust-install"

Actual results:

4. traceback message is displayed on the console.
[root@ipaserver1 ~]# ipa-winsync-migrate 
ipa: WARNING: session memcached servers not running
Traceback (most recent call last):
  File "/usr/sbin/ipa-winsync-migrate", line 23, in <module>
    WinsyncMigrate.run_cli()
  File "/usr/lib/python2.7/site-packages/ipapython/admintool.py", line 124, in run_cli
    sys.exit(cls.main(sys.argv))
  File "/usr/lib/python2.7/site-packages/ipaserver/install/ipa_winsync_migrate.py", line 346, in main
    api.Backend.ldap2.connect(ccache)
  File "/usr/lib/python2.7/site-packages/ipalib/backend.py", line 63, in connect
    conn = self.create_connection(*args, **kw)
  File "/usr/lib/python2.7/site-packages/ipaserver/plugins/ldap2.py", line 149, in create_connection
    client_controls=clientctrls)
  File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 1070, in gssapi_bind
    '', auth_tokens, server_controls, client_controls)
  File "/usr/lib64/python2.7/contextlib.py", line 35, in __exit__
    self.gen.throw(type, value, traceback)
  File "/usr/lib/python2.7/site-packages/ipapython/ipaldap.py", line 975, in error_handler
    error=info)
ipalib.errors.NetworkError: cannot connect to 'ldap://localhost:389': 

5. Traceback message is not displayed on the console, although ipa-server-install is not run on the system

[root@ipaserver1 ~]# ipa-adtrust-install 
The log file for this installation can be found in /var/log/ipaserver-install.log
IPA is not configured on this system.


Expected results:
Instead of the traceback message seen in Actual Results 4, the output should be 
similar to what we see in Actual Results 5.

Basically replace traceback message with user-friendly message on the console.


Additional info:
Comment 2 Petr Vobornik 2015-11-20 10:58:44 UTC 
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5470
Comment 3 Tomas Babej 2015-11-25 11:43:40 UTC 
Fixed upstream
master: https://git.fedorahosted.org/cgit/freeipa.git/commit/?id=dbc442cc608a49726bcca9749b01dcd363b3ed8f
ipa-4-2: https://git.fedorahosted.org/cgit/freeipa.git/commit/?id=84e479edaaeb64567f4cfc847aa735bbd106220d
Comment 4 Mike McCune 2016-03-28 22:43:24 UTC 
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Comment 6 Sudhir Menon 2016-07-18 10:23:21 UTC 
Traceback is not displayed now when ipa-winsync-migrate command is run without ipa-server installed.

Verified using ipa-server-4.4.0-2.1.el7.x86_64

[root@server ~]# ipa-winsync-migrate 
IPA is not configured on this system.
Comment 8 errata-xmlrpc 2016-11-04 05:40:59 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-2016-2404.html
Note You need to log in before you can comment on or make changes to this bug.