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:
Running a ipa-client-install, that fails, has an exit code of 0

> ipa-client-install --domain=abc -p XXX -w XXX  -U
will throw an error:
Unable to find IPA Server to join
Installation failed. Rolling back changes.
IPA client is not configured on this system.

And then 
> echo $?
indicates a zero
as if ipa-client was installed successfully, but looks like this return code is to say that when install failed, it uninstalled successfully....which is not as expected, since I'm checking the status of the client install I just attempted.



Version-Release number of selected component (if applicable):
ipa-client-2.1.1-4.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. run a bad install command like:
ipa-client=install 
or
ipa-client-install --domain=abc -p XXX -w XXX  -U
2. Error is thrown to indicate the client install failed
3. Check exit status 
echo $?
  
Actual results:
0

Expected results:
1

Additional info:

Upstream ticket:
https://fedorahosted.org/freeipa/ticket/1937

Fixed upstream:
master: https://fedorahosted.org/freeipa/changeset/af63731363c23f879ccefcd4b03695f463dbab3f
ipa-2-1: https://fedorahosted.org/freeipa/changeset/e2182d67aecd32903f30a3a0b67450158d6a8776

Verified using ipa-client-2.1.2-2.el6.x86_64


# ipa-client-install -U
One of password and principal are required.
Installation failed. Rolling back changes.
IPA client is not configured on this system.

# echo $?
1

    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:
Cause: ipa-client-install may return success return code even when the installation has failed
Consequence: Automated tools running ipa-client-install cannot use the return code to tell if the installation was successful and would have to parse its output
Fix: Proper error code is returned when ipa-client-install fails
Result: Automated tools can use the return code to check if the installation 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.

http://rhn.redhat.com/errata/RHSA-2011-1533.html