With update of ansible-lint to version >=6.0.0 a lot of new
linters were added, that enabled by default. In order to comply
with linter rules we're applying changes to the role.
With that we also update metdata to reflect current state.
Depends-On: https://review.opendev.org/c/openstack/ansible-role-systemd_service/+/888223
Change-Id: Id92330b3c709201a74612c8353cefa75778eac0c
This change sets the user argument in the cron module which is
required in future versions of ansible when the cron_file argument
is also used.
Filter deprecations for skipped items have also been fixed.
Change-Id: I803cd3c62707880e873662ea86590274b2766d21
Signed-off-by: Kevin Carter <kevin.carter@rackspace.com>
===
[DEPRECATION WARNING]: Using tests as filters is deprecated.
Instead of using `result|search` use `result is search`. This
feature will be removed in version 2.9.
===
Change-Id: I8e856ecaeb82446785dbdcd23688bb0db0a30857
With the more recent versions of ansible, we should now use
"is" instead of the "|" sign for the tests.
This should fix it.
Change-Id: I562dc5430f04c09fdd63b07f0f307a273f232d0a
When the first Keystone container is rebult in an existing environment,
the credential key repository is overwritten with new keys and the
existing keys are overwritten on the other infrastructure hosts without
any migration taking place. This results in an irrevocable loss of
the keys used to encrypt the credentials.
Now we will collect keys from any existing credential keys on the other
containers and use them to rebuild the credential-key repo on the primary
container before performing a key migration and rotation.
If no keys are found on the other containers, we will perform a
credential_setup on the primary container and sync the keys, just
as we would have before.
Closes-Bug: #1667960
Change-Id: Ic616d397574573629273838fbf68ea3f6bdb0468
We need to setup the appropriate directory for credential_setup and run
the keystone-manage credential_setup command.
We created the directory and the '[credential]' stanza in the
keystone.conf, which will ensure we can add additional settings using
config_template if any further are required.
We need to setup the autorotation cron job and distribution for
credential keys.
Additionally, we include all tempest tests now that we are
supporting this feature.
Change-Id: Ifd85ed1a64538ed037e4426cc50238d2b16d51e5
Dmitriy Rabotyagov