New horizon release use [1] for cache backend
instead of [2] as it was in previous versions.
This patch:
1. Removes override from config and
configure only memcached endpoints, not backend
specification itself. This will avoid bugs
in future in case BACKEND will be switched again.
2. Remove 'memcached' context from kolla_address filter
and use 'url' as [1] don't support inet6:[{address}]
for ipv6 but supports [{address}] which 'url' provides.
[1] django.core.cache.backends.memcached.PyMemcacheCache
[2] django.core.cache.backends.memcached.MemcachedCache
Change-Id: Ie3a8f47e7b776b6aa2bb9b1522fdd4514ea1484b
That is the ovs-vsctl default but Ansible module is failing in
reconfigure step - and secure breaks external connectivity in
OVN.
From OVS docs:
fail_mode: optional string, either secure or standalone
When a controller is configured, it is, ordinarily, responsible
for setting up all flows on the switch. Thus, if the connection
to the controller fails, no new network connections can be set
up. If the connection to the controller stays down long enough,
no packets can pass through the switch at all. This setting de‐
termines the switch’s response to such a situation. It may be
set to one of the following:
standalone
If no message is received from the controller for three
times the inactivity probe interval (see inactiv‐
ity_probe), then Open vSwitch will take over responsibil‐
ity for setting up flows. In this mode, Open vSwitch
causes the bridge to act like an ordinary MAC-learning
switch. Open vSwitch will continue to retry connecting to
the controller in the background and, when the connection
succeeds, it will discontinue its standalone behavior.
secure
Open vSwitch will not set up flows on its own when the
controller connection fails or when no controllers are
defined. The bridge will continue to retry connecting to
any defined controllers forever.
The default is standalone if the value is unset, but future ver‐
sions of Open vSwitch may change the default.
Change-Id: Ica4dda2914113e8f8349e7227161cb81a02b33ee
This patch adds check_mode: false to tasks
in restart_services.yml which just checking
some WSREP status and if port is UP.
Closes-Bug: #2052501
Change-Id: I92a591900d85138a87991a18dd4339efd053ef1b
The purpose of this patch is to make it easier to
review changes, because renaming and changing the
file in one patch will generate diff when the entire
file will be deleted on the one hand and new file
(actually just renamed) will be new on the other hand,
which is hard to review.
Change-Id: I17a16ce746faa8898a457cadbb6f996f964a5b6f
The development quickstart document has not been updated for a
while, and it has become desynchronized with the regular quickstart.
Change-Id: I6b14623b73b0032df94f0f633659a1b6dfc15dea
Ironic started enforcing new RBAC policies [1]. Kolla/Kayobe
CI jobs are failing, as K-A doesn't have service role support.
Moreover Ironic RBAC is not yet stable enough [2].
Disable enforcing new policies until fix merges and Kolla
Ansible service role support is added.
[1] https://review.opendev.org/c/openstack/ironic/+/902009
[2] https://review.opendev.org/c/openstack/ironic/+/907148
Related-Bug: #2051837
Change-Id: I424cff6ac96dfe0dd5dc58afca2b785f494c9f02
This patch disables periodic compute.instance.exists
notifications when designate is enabled.
Related-Bug: #2049503
Change-Id: I39fe2db9182de23c1df814d911eec15e86317702
Service user passwords will now be updated in keystone if services are
reconfigured with new passwords set in config. This behaviour can be
overridden.
Closes-Bug: #2045990
Change-Id: I91671dda2242255e789b521d19348b0cccec266f
The version that we were capping to is no longer compatible with latest
upper-constraints.txt, so let us free float again.
The resulting linting errors are included for now to unblock the gate,
these will still need to be discussed or fixed later.
NOTE(kevko): Temporarily disabling horizon deployment, as it's not
possible to unblock gates without it
Co-Authored-By: Michal Arbet <michal.arbet@ultimum.io>
Change-Id: Ib7f72b2663199ef80844a412bc436c6ef09322cc
In Kolla CI K-A upgrade job needs docker_custom_config override
as docker_registry var is being used both for docker daemon
config - for kolla images build, and kolla-ansible container images
sources - where we're using quay.io mirror.
docker_custom_config gets precedence in docker daemon
configuration.
docker_custom_config was removed in [1].
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/904067
Change-Id: I1e890223faf25b1169a49e22a9529f90806d2f3a
Shard allocation is disabled at the start of the OpenSearch upgrade
task. This is set as a transient setting, meaning it will be removed
once the containers are restarted. However, if there is not change in
the OpenSearch container it will not be restarted so the cluster is left
in a broken state: unable to allocate shards.
This patch moves the pre-upgrade tasks to within the handlers, so shard
allocation and the flush are only performed when the OpenSearch
container is going to be restarted.
Closes-Bug: #2049512
Change-Id: Ia03ba23bfbde7d50a88dc16e4f117dec3c98a448
