This patch adds support for conditionally setting a minimum allowed TTL value with designate.
Note: also cleans up a previous conditional to take advantage of a new
wallaby heat template syntax for if's that don't have an 'else'.
Change-Id: Id80e5b07ff3080835162c2a301a7a48be9787959
Many of the designate services perform background syncrhonization
tasks and can lag a bit on shutdown, especially on heavily loaded or
large scale systems. Increasing the stop grace periods reduces the
likelihood that the system might get into a non-consistent state or a
state where a great deal of reconciling needs to occur on restart.
Change-Id: If521662eb4c47ada45cf0a9edd0a58db8a1d038d
There is a possibility that haproxy container crashed and restarted
with another UUID, while the deployment is trying to reload it
after reconfiguring the certificates, by sending a
`kill -HUP <uuid-of-the-container>`. In that case, ingore errors
for the commands block, since there is no longer need to reload the
newly created container.
Related rhbz#1973674
Change-Id: I4b40d73ab329dc219ee7a387201b0747a6233ed4
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
Adds new NovaCronArchiveDeleteRowsTaskLog parameter which controls to
also archive task_log records while archiving the database. Defaults to
true.
Depends-On: https://review.opendev.org/c/openstack/puppet-nova/+/801924
Change-Id: I59dc05ec26703bf92121a46a5ac0b3786d5e0a18
Related-Bug: #1877189
Since PyYAML 5.1, yaml.load without specifying the Loader option is
deprecated and shows the following warning.
YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated,
as the default Loader is unsafe.
Please read https://msg.pyyaml.org/load for full details.
This change replaces yaml.load by yaml.safe_load (which is effectively
same as adding Loader=yaml.SafeLoader) to get rid of that warning
message. Also, existing all usage of yaml.load with the Loader option
are also replaced so that we to make all implementation to load yaml
files consistent.
Change-Id: Id44fa2354429b944fbc0809f63db558bb7de23f7
The correct variable name in tripleo-ansible/roles/tripleo_ovn_cluster/templates/ovn_cluster.j2
is OVN_NORTHD_OPTS. With this change we see that the ovn_northd process
starts correctly with all the right parameters:
root 104187 0.0 0.0 43056 8868 ? S 16:57 0:00
\_ /usr/bin/ovn-northd --no-chdir -vconsole:emer -vsyslog:err
-vfile:info --pidfile=/run/openvswitch/ovn-northd.pid
--log-file=/var/log/openvswitch/ovn-northd.log
--private-key=/etc/pki/tls/private/ovn_dbs.key
--certificate=/etc/pki/tls/certs/ovn_dbs.crt --ca-cert=/etc/ipa/ca.crt
--ovnnb-db=ssl:172.17.1.132:6641,ssl:172.17.1.58:6641,ssl:172.17.1.50:6641
--ovnsb-db=ssl:172.17.1.132:6642,ssl:172.17.1.58:6642,ssl:172.17.1.50:6642
Reported-By: Jakub Libosvar <jlibosva@redhat.com>
Change-Id: I50cf3b7d79d8cd139ae514438e147df73901a366
To help operators protect their workload, they can now enable the
KernelArgsDeferReboot role parameter. This will prevent the tripleo-kernel
ansible module from automatically rebooting nodes even if KernelArgs
were changed unexpectedly.
Change-Id: I52e43f264a03775b6d609444f8da1a36d9565281
The cephfs_enable_snapshots parameter was deprecated in Manila[1]
during Victoria and was removed during Wallaby. Now Manila always
enables snapshot support for CephFS backend. Following that deprecation
in Manila, the corresponding parameter of puppet-manila was deprecated
during the Victoria cycle [2] and it is being removed during the Xena
cycle.
This deprecates the corresponding parameter from tripleo-heat-tempaltes
because it has no effect since Wallaby.
[1] 2d7c46445396b0db780ba456ffb9284b177a6ae4
[2] 2388d7510d600e358c76becf13d08581b489f2a7
Co-Authored-By: Goutham Pacha Ravi <gouthampravi@gmail.com>
Change-Id: I81565290603eb60c8c18e64c95ead7b761e8cb78
In some cases OS of VM shuts down very slowly. After post_reboot_delay
(120 sec) ansible logs in to VM and runs "systemctl
is-system-running | grep -qE "running|degraded" which works perfectly on
RHEL/CentOS 7/8. Ansible will be puzzled as it doesn't detect any other
statuses. This issue was solved in ansible 2.10 by redesigning reboot
module where "boot_time_command" verifies boot_id before and after
reboot. However, we cannot backport ansible 2.10 to product so this
patch adds a little check to detect OS version to keep it simple. This
works as leapp installs RHEL8 in disconnected mode after reboot, ansible
won't be able to connect until leapp is done.
Resolves: rhbz#1980542
Change-Id: I6190ee794dce461077b08b486aef18cbf9cc04b3
Post upgrade tasks are limited to 4-1 steps, so these
tasks are not executed.
Deleting nova-consoleauth is failing with some of the CIs and this is
mostly a best-effort kind of task, so adding ignore_errors.
Also, replacing some yes/nos with boolean as it's best practice.
Related: https://bugzilla.redhat.com/1921112
Change-Id: I0bc39170569c42a0be31233fd7ec068613547790
The OctaviaPostWorkflowName parameter used to define name of
the mistral workflow to run post deployment tasks for Octavia. However
all post tasks have been migrated from independent mistral workflow to
external_deploy_task[1], and the parameter has had no effect since
that migration.
[1] 3def4e0384c22e9d7d6821ab74a372d188a2d0ac
Change-Id: I419daa040f5998440af956fadab62ec26abed4dc
The commit e2680bbf7eba8b40424083900d21ec285754c86f removed usage
of CephManilaClientKey in manila-backend-cephfs.yaml but it didn't
remove comments about the parameter.
Change-Id: I65c1ef66833109d10882981f4a4f5852ee31acf0