Bug 1472363 - [RFE] Change the default API version used by the client to the latest
[RFE] Change the default API version used by the client to the latest
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-ironicclient (Show other bugs)
13.0 (Queens)
Unspecified Unspecified
high Severity medium
: Upstream M2
: 13.0 (Queens)
Assigned To: Dmitry Tantsur
: FutureFeature, Triaged
Depends On:
Blocks: 1473267
  Show dependency treegraph
Reported: 2017-07-18 10:49 EDT by Dmitry Tantsur
Modified: 2018-04-03 05:30 EDT (History)
7 users (show)

See Also:
Fixed In Version: python-ironicclient-2.2.0-1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1671145 None None None 2017-07-18 10:53 EDT
OpenStack gerrit 512989 None master: MERGED python-ironicclient: Set the default API version of OSC CLI to "latest" (I489fee937a356b523eb35379dce3631195132fe5) 2018-02-07 09:35 EST

  None (edit)
Description Dmitry Tantsur 2017-07-18 10:49:00 EDT
It's very inconvenient that we have to provide --os-baremetal-api-version flag every time we use a new version. An error message due to not doing it can also be quite not clear. We have decided on the Pike PTG that we will change the default version from the lowest supported to the highest supported.

No direct impact on TripleO, as it pins the version. We can unpin it for the overcloud.
Comment 5 Dmitry Tantsur 2018-03-29 09:06:24 EDT
Testing PASSED on RHEL 7.5, puddle 2018-03-29.1. Notes:

$ openstack baremetal node trait list host08
Requested API version 1.1 is not supported by the server, client, or
the requested operation is not supported by the requested
version.Supported version range is 1.1 to 1.37
$ openstack baremetal node trait list host08

Note You need to log in before you can comment on or make changes to this bug.