Generated clouds.yaml broken in noauth mode

[Mark Goddard]

Steps to reproduce
------------------

Deploy bifrost without keystone enabled.

Attempt to use the openstack client to list nodes:

OS_CLOUD=bifrost openstack baremetal node list

Expected result
---------------

Nodes are listed

Actual result
-------------

Missing parameter(s):
Set a cloud-name with --os-cloud or OS_CLOUD

Environment
-----------

Bifrost deployed in a CentOS container using stable/queens branch @ 4f7c0eab1d93dab8caae20ff7752579d6722b931.

clouds.yaml:

# WARNING: This file is managed by bifrost.
clouds:
  bifrost:
    auth_type: "none"
    url: http://localhost:6385

Workaround
----------

Reverting to the old format of clouds.yaml allows the client to work:

# WARNING: This file is managed by bifrost.
clouds:
  bifrost:
    auth_type: None
    auth: {}
    url: http://localhost:6385

It is also possible to remove the 'auth: {}' line.

[Mark Goddard (mgoddard)]

Here's the change that switched to the none auth_type: https://github.com/openstack/bifrost/commit/21ca45937a9cb36c6f04073182bf2edea8acbd5d.

[Mark Goddard (mgoddard)]

ironic==10.2.0.dev81
keystoneauth1==3.4.0
keystonemiddleware==4.21.0
openstacksdk==0.11.3
os-client-config==1.29.0
python-ironicclient==2.2.0
python-keystoneclient==3.15.0
python-openstackclient==3.14.0

[Pavlo Shchelokovskyy (pshchelo)]

might be related to https://bugs.launchpad.net/python-openstackclient/+bug/1724283

[Mark Goddard (mgoddard)]

Thanks for the link to that issue. I checked keystoneauth in my environment, and I do have Vlad's change (https://review.openstack.org/515730), which was included in keystoneauth1 3.4.0.

I tested Vlad's patch to osc-lib (https://review.openstack.org/#/c/512699/11), but this did not help. Perhaps because it's checking auth_type == none in the CLI options rather than those from clouds.yaml?

[Mark Goddard (mgoddard)]

Proposed solution: https://review.openstack.org/#/c/550573. That appears to fix the issue, in combination with https://review.openstack.org/#/c/512699.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/bifrost 5.0.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/bifrost 5.1.0 release.