Currently ovs_dpdk molecule jobs are failing with openvswitch
package is not available.
test_deps_setup_tripleo for test_deps role fixes the issue.
Fixed the package name for openvswitch.
updated the job timig also.
Switch to ubi:8.2 base image in molecule job to fix package
conflict issue caused by ubi:8.3
Closes-Bug: #1905683
Closes-Bug: #1905687
Change-Id: Ie77be94849bba28f322a09d254be650a9ec687f5
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
This change converts our use of CentOS7/88 to UBI8, which should
provide a better test environment which will match that of
production for future releases of TripleO. While this image change
will better match production clouds thanks in large part to TCIB,
it will also remove our use of docker.io (dockerhub) which fraught
with peril due to the ongoing API rate limits saga.
Story: 2006061
Task: 34774
Change-Id: I067046e5fd4d56cd88712f553e25a61db60ced7f
Signed-off-by: Kevin Carter <kecarter@redhat.com>
This role is meant to help moving the HA pcs tasks to pure deployment
steps run on the host and not in containers any more. We tested this
ansible review with the THT patches at
https://review.opendev.org/#/q/status:open+project:openstack/tripleo-heat-templates+branch:master+topic:pcs_host3
Here is the testing protocol that was used in order to verify we did
not break anything:
1) Deployed overcloud + tempest
2) Ran a successful redeploy
2.1) Verified that a redeploy restarted containers globally when the
configuration for the service changed
2.2) Verified that a redeploy did not restart containers which config
did not change
2.3) Verified that the ordering of restarting bundles allows for
brownfield deployments (i.e. first the bundle is restarted due
to new bind-mounts and then the bundle is restarted with new
configuration)
2.4) Verified that converge step after minor update is successful
3) Ran an initial successful minor update
3.1) Verified that the new image is indeed being run by pacemaker
(i.e. :pcmklatest tag is applied to the new containers)
3.2) Verified that after converge no container is restarted
4) Re-run a subsequent successful noop minor update
4.1) Verify that containers are not restarted a second time after
the cluster is stopped and started
Depends-On: I367cf4b65300be8dca0190b9adeab549018d4a56
Change-Id: Iaa7e89f0d25221c2a6ef0b81eb88a6f496f01696
Related-Bug: #1863442
Chandan Kumar (raukadah)
Kevin Carter
Michele Baldessari