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.

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4768

The error message

{{{
ipa: ERROR: 2.108 client incompatible with 2.65 server
}}}

prevents remote {{{ipa}}} operations even if the specific API calls could very well run against the older server version because they parameters and result and behaviour is exactly the same.

Proposing here new option {{{--ignore-version-mismatch}}} to just skip this check.

The "... client incompatible with ... server" error message could also hint at this new option, with a warning that things might not work.

My main reason for this "workaround" are the container deployments where it might not even be possible to ssh to the container to run the {{{ipa}}} command on the IPA server, and the matrix of client/server combinations might become much richer because it will be much easier to just run image which happens to have different server version than the host/workstation.

When this is implemented, the option should be noted at http://www.freeipa.org/page/Client#Compatibility

Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/ea7f392bb98c1f1c4558ec5d6e84ee7a7c613474

Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/232458a222435c80c28d6179f164673de67e2544

Verified by installing 7.1 server using ipa-server-4.1.0-18.el7.x86_64 and 7.2 client using ipa-client-4.2.0-11.el7.x86_64


# ipa user-find
ipa: ERROR: 2.156 client incompatible with 2.112 server at 'https://cloud-qe-20.testrelm.test/ipa/xml'

# ipa -e skip_version_check=1 user-find
--------------
1 user matched
--------------
  User login: admin
  Last name: Administrator
  Home directory: /home/admin
  Login shell: /bin/bash
  UID: 1455400000
  GID: 1455400000
  Account disabled: False
  Password: True
  Kerberos keys available: True
----------------------------
Number of entries returned 1
----------------------------

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-2015-2362.html