Version v1.1.0 includes useful updates needed for supporting the
PowerConnect 6248, such as support for 'enable' and quirky differences
in the CLI.
Change-Id: I1a9e0471f34183c85002de30c395b82baa5f3ef4
If using the kayobe --limit <hosts> argument, only those hosts matching
the limit will have an inventory generated for Kolla Ansible. This can
cause problems for Kolla Ansible, even when using a similar limit via
--kolla-limit <hosts>, since it gathers facts for all hosts, and expects
all host variables to be defined.
This change adds a new 'ignore_limit' argument to the playbook running
methods, which allows us to override and ignore the --limit argument
provided by the user, ensuring that we always run these plays.
Change-Id: I104d6af48ddd916460ee454e17a50a2475de6bff
Story: 2004805
Task: 28960
Fixes an issue where multiple NTP daemons could be running on the
overcloud hosts, due to Kolla Ansible deploying a chrony container by
default starting with the Rocky release.
Kayobe now overrides this default, to ensure that chrony does not conflict
with the NTP daemon deployed on the host. To use the containerised chrony
daemon instead, set ``kolla_enable_chrony`` to ``true`` in
``${KAYOBE_CONFIG_PATH}/kolla.yml``. This will also disable the host NTP
daemon.
To ensure that chrony is not running, Kayobe removes the chrony container
if ``kolla_enable_chrony`` is ``false`` in the following commands:
* ``kayobe overcloud service deploy``
* ``kayobe overcloud service reconfigure``
* ``kayobe overcloud service upgrade``
The play in Kayobe is tagged with ``stop-chrony``.
Change-Id: I89a973c0b600abece79bddcba5a46cc28a4f1df9
Story: 2005272
Task: 30122
This is more representative of the typical use case of applying all
security-related package updates rather than just specific ones.
Also escape `*`, since most people will need to do so in their shell.
Change-Id: Ibd602b7fe30d7c6eb7c81b5f028ab6b5852da988
This commit allows Kayobe to generate a global.conf file for use by
Kolla Ansible to override configuration across all OpenStack services.
Change-Id: I6d144a945e1cde06fa9fdd03c30102458c0c9f8d
Story: 2005904
Task: 34153
This network conflicts with the ironic provision-net since both are flat
networks on physnet1. We don't need the external network in our CI, so
don't create it.
Change-Id: Id17d4ea00ceb684b34bf12e911758d504c520de0
Depends-On: https://review.opendev.org/#/c/670129/
This avoids mariadb being ungracefully shut down, which prevents it from
being started again.
This should be reverted once bug 1834332 has been fixed in kolla ansible
stein.
Change-Id: Ic3932d4af5c0a7639dfeb6cda7e1cd3f61d287c6
Story: 2006050
Task: 34743
Updates the minimum version of Ansible from 2.4 to 2.5, and the maximum
supported version from 2.6 to 2.7.
Change-Id: If8071a9b5c85e5e69fbb333e91c84d10c20d80f3
Story: 2006143
Task: 35639
Since Ansible 2.5, the use of jinja tests as filters has been deprecated.
I've run the script provided by the ansible team to 'fix' the jinja filters
to conform to the newer syntax.
This fixes the deprecation warnings.
Change-Id: I775c849c944f82bdfc779c8c530346e7ebedbd2a
1. Sync sphinx dependency with global requirements. It caps python 2 since
sphinx 2.0 no longer supports Python 2.7.
2. Update some URLs to latest
3. Remove unncessary "=="
Change-Id: Idcb616fd3add4d58f22b91865cec8a54fe492092
Commit d8ee0fa027140fb8a7504bd6685b6dcdfe3ac8fe introduced the variable
kolla_enable_keystone without setting a default value and used it to
check whether to template and provide keystone.conf to kolla-ansible,
unlike the extended keystone configuration which was always copied. This
resulted in non-intuitive behaviour if kolla_enable_keystone wasn't
explicitly set by the operator.
This commit sets kolla_enable_keystone to true by default, which matches
the default in kolla-ansible, and uses it instead of hardcoded true
values.
Change-Id: Id090348a6f22f251555fa286a7d24923087122a9
Story: 2005930
Task: 34273
Using Kayobe with cliff 2.15.0 fails with the following error:
kayobe playbook run playbook.yml
invalid conflict_resolution value: 'ignore'
This change restricts cliff to <2.15.0.
Also, fix git cloning previous release repos in CI to allow this patch
to merge.
Zuul provides repositories with all branches containing all prospective
changes, not just the current branch. We can use this in the upgrade
jobs to include changes to the previous release branch when a patch
depends on them.
Change-Id: I7966cf33f6133090d83232504b8c1da4c7817e0c
Depends-On: https://review.opendev.org/665703/
Story: 2005891
Task: 33748
Keystone removed the UUID token provider in Rocky and Kolla Ansible
removed support for configuring it. This commit reflects these changes
in Kayobe.
Change-Id: I5a2c71e7e65f99687437f6a26a0c4a942022f4e9
If password authentication is not disabled on the server, we may be
prompted for a password if the Kayobe Ansible user doesn't exist or
isn't configured for passwordless authentication.
By using BatchMode, the ssh command can fail quickly and proceed to
create the Kayobe Ansible user using the bootstrap user.
Change-Id: If22ed34dc4b6e87f8cf76c302948c955bddf2bc5
This new version makes the kayobe-tox-molecule job fail with:
ImportError: cannot import name py31compat
Change-Id: Ieddf039483649cc7b575019409257b6ce5b3fb99
