We have Debian support for quite a while. While binary target is not
always up-to-date (due to Debian OpenStack team policy of building only
released code, not git snapshots) source images are expected to just
work.
Change-Id: I2ed6061054bcea12d5b38974ee691e9632d32f05
Correct typo in role's playbook in order to be able to deploy
the service with customized policy file.
Change-Id: I252ffaf73dd2a649387ddacc73286b49f36dfdf2
Closes-Bug: #1948835
It seems some cases were missed in reviews and not fixed by
the previous iterations:
Ifc252ae793e6974356fcdca810b373f362d24ba5
I838e526b930d5276d3ce24f5188262af7eb33280
Change-Id: Id57da1c5024e1efc5810baca8fbe18967cf95a68
The copy job for the grafana home dashboard file needs to run
priviliged, otherwise permission denied error occurs.
Closes-Bug: #1947710
Change-Id: Ib15e961e5193af55e45a443305a96667295f3cb7
There seems to be a bug in Galera that causes
TASK [mariadb : Check MariaDB service WSREP sync status]
to fail.
One (in case of 3-node cluster) or more (possible with
more-than-3-node clusters) nodes may "lose the race" and get stuck
in the "initialized" state of WSREP.
This is entirely random as is the case with most race issues.
MariaDB service restart on that node will fix the situation but
it's unwieldy.
The above may happen because Kolla Ansible starts and waits for
all new nodes at once.
This did not bother the old galera (galera 3) which figured out
the ordering for itself and let each node join the cluster properly.
The proposed workaround is to start and wait for nodes serially.
Change-Id: I449d4c2073d4e3953e9f09725577d2e1c9d563c9
Closes-Bug: #1947485
Add file to the reno documentation build to show release notes for
stable/xena.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/xena.
Sem-Ver: feature
Change-Id: I5ec222dde45ed36b70547f4d03612e91fc2ea02e
This change adds the dnsmasq.log for the ironic-dnsmasq container and
also enables more verbose logging when debug logging enabled.
This can be triggered globbaly via 'openstack_logging_debug' or per
service via 'ironic_logging_debug' or 'neutron_logging_debug'.
Change-Id: I0e6b089beb88827effbcc365625eb2df902f5470
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
This change updates documentation, examples and tests to support
Ironic inspection through DHCP-relay. The dnsmasq service should be
configured with more specific format set in the variable
``ironic_dnsmasq_dhcp_range``. See the dnsmasq manual page [1].
[1] https://thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html
Change-Id: I9488a72db588e31289907668f1997596a8ccdec6
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
The section [ovs] is needed only for ovs/ovn configurations.
TrivialFix
Change-Id: If9015b8f53c04cf3257331449ebd50163fabcab0
Signed-off-by: Maksim Malchuk <maksim.malchuk@gmail.com>
Weight for haproxy backend was merged in [1] with
tiny bug, there is need to convert to int to check
conditional <= 256. Otherwise, it's not working as
expected.
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/775627
Change-Id: Icb6f5147ebd2a0be52ba4ef6ba4a00bbd0242d3d
"BINLOG MONITOR" and "SLAVE MONITOR" replace
"REPLICATION CLIENT" (which is now an alias for "BINLOG MONITOR").
The validation in Ansible MySQL collection is too simple to
understand aliases and breaks. Hence, let's use the canonical
names and adapt per service according to its needs.
Change-Id: I1175e4846384accd19942620dc155d0c5728e64b
Updates the default value of 'monasca_ntp_server' from
'external_ntp_servers[0]' to '0.pool.ntp.org'. This is due to the
removal of the 'external_ntp_servers' variable as part of the removal of
Chrony deployment.
Change-Id: I2e7538a2e95c7b8e9280eb051ee634b4313db129
Ignore the monasca_thresh container if it is listed as exited.
The container was recently changed to operate as a 'one shot' container,
submitting a job to storm then exiting. This does not fit with the
usual pattern of Kolla Ansible container usage, but is harmless.
Depends-On: https://review.opendev.org/c/openstack/kolla/+/811977
Change-Id: Id40d2260a67ef604255fb1818d41cdcbc73164d7
chrony is not supported in Xena cycle, remove it from kolla
Moved tasks from chrony role to chrony-cleanup.yml playbook to avoid a
vestigial chrony role.
Co-Authored-By: Mark Goddard <mark@stackhpc.com>
Change-Id: I5a730d55afb49d517c85aeb9208188c81e2c84cf
Since Wallaby, we default to disabling Docker's iptables
management, thus making the code being removed here obsolete.
Change-Id: Ieb7774f2380a811070aea27964a39e4c8cb02083