keystone auth fails in train and ussuri

[Lars Erik Pedersen]

In stable/train and stable/ussuri all the admin_* parameters was removed from the keystone_authtoken section in authoken.pp. As per the magnum installation doc you still have to set those parameters - and if you don't, keystoneauth will actually fail. This is fixed in victoria by adding the keystone_auth class

So. Either the admin_* parameters needs to be re-added in train and ussuri, or the keystone_auth class needs to be backported to train and ussuri.

I've tested to add the config lines keystone_auth sets, manually in ussuri - and that works perfectly fine.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ussuri
Review: https://review.opendev.org/758981

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/758981
Committed: https://git.openstack.org/cgit/openstack/puppet-magnum/commit/?id=01fe27b73d415f133a9dcce6fe91ffd0729e1ce1
Submitter: Zuul
Branch: stable/ussuri

commit 01fe27b73d415f133a9dcce6fe91ffd0729e1ce1
Author: Jake Yip <email address hidden>
Date: Wed Sep 2 16:42:29 2020 +1000

    New class to support keystone_auth config

    The config section [keystone_auth] is used for service user, which is
    different from [keystone_authtoken]. They used to be managed in the same
    class, but after the deprecation in Change
    I0cea57dd58b4ddc532ee28a045ec4b75b8312919, magnum can no longer fall
    back to use the values in keystone_authtoken/admin_user [1]

    We add a new class to manage [keystone_auth] of the config, to keep it
    distinct from keystone_authtoken

    [1]: https://github.com/openstack/magnum/blob/stable/train/magnum/common/keystone.py#L122-L123

    Closes-Bug: #1900813
    Change-Id: Ib1fe977a151346cd2ab29ad33d7d9dbb86413fe6
    (cherry picked from commit 85b20b0db469a6a0777192a7f94ea454b9d1cce8)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/puppet-magnum 16.4.0 release.