#4768 [RFE] Add option to skip the verify_client_version and proceed at own risk
Closed: Fixed None Opened 8 years ago by adelton.

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


This might be a requirement for formally supporting our API.

This work should be part of 4.2 core, to enable API consumption until we have the thin client.

master:

  • ea7f392 add option to skip client API version check

master:

  • 232458a ipalib: Fix skip_version_check option

Reopening. Per man default.conf(5)

   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.

but calling for example

ipa user-find

against RHEL 6.7 server (ipa-server-3.0.0-47.el6.x86_64) yields

# 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'

instead of

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

Martin explained in

https://www.redhat.com/archives/freeipa-users/2016-January/msg00128.html

that (and why) 2.51 value was used but we don't have a way to skip the check altogether.

A new ticket was opened for the issue: #5601

Reclosing this ticket.

Metadata Update from @adelton:
- Issue assigned to mbabinsk
- Issue set to the milestone: FreeIPA 4.2

6 years ago

Login to comment on this ticket.

Metadata