Bug 1297811 - The ipa -e skip_version_check=1 still issues incompatibility error when called against RHEL 6 server
Summary: The ipa -e skip_version_check=1 still issues incompatibility error when calle...
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.2
Hardware: All
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Namita Soman
URL:
Whiteboard:
Keywords: ZStream
Depends On:
Blocks: 1298104
TreeView+ depends on / blocked
 
Reported: 2016-01-12 14:19 UTC by Jan Pazdziora
Modified: 2016-11-04 05:48 UTC (History)
9 users (show)

(edit)
Clone Of:
: 1298104 (view as bug list)
(edit)
Last Closed: 2016-11-04 05:48:33 UTC


Attachments (Terms of Use)


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

Description Jan Pazdziora 2016-01-12 14:19:56 UTC
Description of problem:

The change from bug 1211589 / ticket https://fedorahosted.org/freeipa/ticket/4768 introduced new option skip_version_check which is documented in man default.conf(5) as

    skip_version_check <boolean>

        Skip client vs. server API version checking. Can lead to errors/strange behavior when newer clients talk to older servers. Use with caution.

It works when used with RHEL 7.2 IPA client enrolled against (say) RHEL 7.1 server but does not work against RHEL 6 server.

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

ipa-admintools-4.2.0-15.el7.x86_64

On server, ipa-server-3.0.0-47.el6.x86_64 is installed.

How reproducible:

Deterministic.

Steps to Reproduce:
1. ipa user-find
2. ipa -e skip_version_check=1 user-find

Actual results:

# ipa user-find
ipa: ERROR: 2.156 client incompatible with 2.49 server at u'https://ipa.example.com/ipa/xml'
# ipa -e skip_version_check=1 user-find
ipa: ERROR: 2.51 client incompatible with 2.49 server at u'https://ipa.example.com/ipa/xml'

Expected results:

# ipa user-find
ipa: ERROR: 2.156 client incompatible with 2.49 server at u'https://ipa.example.com/ipa/xml'
# ipa -e skip_version_check=1 user-find

users listed, no error

Additional info:

Comment 1 Jan Pazdziora 2016-01-12 14:24:28 UTC
With ipa-server-3.0.0-25.el6.x86_64 from RHEL 6.4 which reports API version 2.46, and when forcing the client version to that value,

   # ipa user-find 

still fails with

   ipa: ERROR: Unknown option: no_members

with no incompatibility error.

With ipa-server-3.0.0-42.el6.x86_64 and ipa-server-3.0.0-47.el6.x86_64, the incompatibility error happens.

Comment 2 Jan Cholasta 2016-01-12 14:36:44 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/5601

Comment 5 Martin Kosek 2016-01-12 15:57:55 UTC
Blocking integration of other product, setting high sev/prio.

Comment 9 Sudhir Menon 2016-08-05 08:39:22 UTC
Client incompatible error is not displayed.
Verified using RHEL7.3 client and RHEL6.8 Server

ipa-server-3.0.0-50.el6.1.x86_64
ipa-client-4.4.0-4.el7.x86_64

[root@client ~]# ipa user-find
--------------
1 user matched
--------------
  User login: admin
  Last name: Administrator
  Home directory: /home/admin
  Login shell: /bin/bash
  UID: 639000000
  GID: 639000000
  Account disabled: False
  Password: True
  Kerberos keys available: True
----------------------------
Number of entries returned 1
----------------------------
[root@client ~]# 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: 639000000
  GID: 639000000
  Account disabled: False
  Password: True
  Kerberos keys available: True
----------------------------
Number of entries returned 1
----------------------------

Comment 11 errata-xmlrpc 2016-11-04 05:48:33 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.