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.
Testing PASSED on RHEL 7.5, puddle 2018-03-29.1. Notes: $ export OS_BAREMETAL_API_VERSION=1.1 $ 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 $ unset OS_BAREMETAL_API_VERSION $ openstack baremetal node trait list host08 $
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://access.redhat.com/errata/RHEA-2018:2086