From:
(kolla) 13:11 (s) marcin@puchatek:kolla-ansible$ kolla-genpwd
Traceback (most recent call last):
File "/home/marcin/.virtualenvs/kolla/bin/kolla-genpwd", line 8, in <module>
sys.exit(main())
File "/home/marcin/.virtualenvs/kolla/lib/python3.10/site-packages/kolla_ansible/cmd/genpwd.py", line 135, in main
genpwd(passwords_file, length, uuid_keys, ssh_keys, blank_keys,
File "/home/marcin/.virtualenvs/kolla/lib/python3.10/site-packages/kolla_ansible/cmd/genpwd.py", line 59, in genpwd
with open(passwords_file, 'r') as f:
FileNotFoundError: [Errno 2] No such file or directory: '/etc/kolla/passwords.yml'
To:
(kolla) 13:17 (s) marcin@puchatek:kolla-ansible$ kolla-genpwd
ERROR: Passwords file "/etc/kolla/passwords.yml" is missing
Change-Id: I18a9559daeb3d124a03dcb735ebb01a2cf24f617
Since enabling libvirt SASL authentication, the masakari instance
monitor fails to connect to libvirt. We see the following error in logs:
libvirt.libvirtError: authentication failed: Failed to start SASL
negotiation: -4 (SASL(-4): no mechanism available: No worthy mechs
found)
This change adds support for SASL authentication in Masakari instance
monitor.
Depends-On: https://review.opendev.org/c/openstack/kolla/+/834456
Closes-Bug: #1965754
Change-Id: I974046662b383a12ac6281b725523760a96657bd
It was removed as part of improvements in [1]. But it seems it's
a different type/class of errors and should still be filtered
out here.
This time for all the services to avoid extra copies.
[1] Ie6a95c3ca84df82ca8463cf76054e125cb1ffff1
Change-Id: If7c5b938dc7417831a90f360d6e3655d1ad4084e
The projects started dropping support for Python 3.6 and thus
CentOS Stream 8 which K-A tests against, resulting in broken CI.
This change ensures that we keep upper-contraints also on Yoga as
we do for the images we deploy.
Change-Id: I82c4ff3b246c7db65ac8660b096d4a9a15dda8d7
In the last PTG it was decided to drop the keystone_token_provider variable, because there is no other option anymore.
Signed-off-by: Ramona Rautenberg <rautenberg@osism.tech>
Change-Id: I1ee2c3f9b7dbbbf4633c5874cdbb3c4f8c09e277
Redis Sentinel modifies its config.
Since we now check config in check-containers,
the redis_sentintel container is restarted each time.
This patch together with kolla patch fixes this issue.
Closes-Bug: #1967664
Depends-On: https://review.opendev.org/c/openstack/kolla/+/840954
Change-Id: Ia76329cb851d266cd888f51b7f70a4cdc40e3ac3
"Smoke tests" for barbican, cinder, glance and keystone have been removed as discussed in PTG April 2022.
Signed-off-by: Tim Beermann <beermann@osism.tech>
Change-Id: I613287a31e0ea6aede070e7e9c519ab2f5f182bd
Add an enable_cinder_backend_pure_iscsi and
enable_cinder_backend_pure_fc options to etc/kolla/globals.yml
to enable use of the FlashArray backend.
Update the documentation to include a section on configuring
Cinder with the FlashArray.
Implements: blueprint pure-cinder-driver
Change-Id: I464733f1322237321ed1ffff8636cf30bd1cbb38
This is in the hope to avoid random "Unable to validate token" in
AIO upgrade jobs which restart the Keystone container while
other services are trying to use it (most notably Placement but
also Nova and Neutron).
Change-Id: Ie6a95c3ca84df82ca8463cf76054e125cb1ffff1
Facts define the group key to judge in incloud roles,
remove when statement does not execute to speed up execution
Partially-Implements: blueprint performance-improvements
Change-Id: If22255f1adc07ab16b46f8ad1280efdf7d713d28
With the parameter bifrost_deploy_verbosity it is possible
to set the verbosity of the bootstrap of Bifrost.
This makes it possible to reduce verbosity when running
/bifrost/playbooks/install.yaml if needed.
Change-Id: I5815220f2193a492ae7e1f63443075790ae7aaef
Zed dropped binary images so we need to check does migration from binary
images works.
Dropped all other CI jobs
Change-Id: Id2d7ca01baca8e17a9780345e705ffb6cbffd8a7
We run some nova tasks once per cell, using a condition to match a
single host in the cell. In other similar tasks, we use run_once, which
will fail all hosts if the task fails. Typically these tasks are
critical, and that is desirable. However, with the approach used in
nova-cell to support multiple cells, if a once-per-cell task fails, then
other hosts will continue to execute, which could lead to unexpected
results.
This change adds any_errors_fatal to the plays or blocks that run these
tasks.
Closes-Bug: #1948694
Change-Id: I2a5871ccd4e8198171ef3239ce95f475f3e4b051
