Temporarily use tempest master for all builds and fix configs
A fix [1] was introduced in openstack-ansible to use tempest from
the master branch in the AIO, but respecting the installation
from PyPI everywhere else. This allowed users to chose
the appropriate behaviour for their use cases.
This patch [1] also made sure we didn't have anything else to do
when the patch would land on stable branches, as this would
automatically get disabled.
However, as of today, there is still no new version of tempest,
and our stable/rocky branch has been cut. Therefore the fix that
was in place is useless and another approach needs to be
taken.
We will move to use tempest master for master and stable/rocky
branch until the fix that caused this series of patch to
happen is released [2] for tempest on PyPI.
A temporary workaround was also added to ensure ceph can still
be built, by freezing the ceph-ansible role sha.
The checksum fill option, was useful a long time ago, but at this point
its just some lovely technical debt that we carry around like an old
dirty security blanket. This change sets us free from the sins of our
past.
We seem to have a lot of jobs that timeout but seem to be very
close to completing, so let's bump the timeout by 20 minutes.
To make up for it, we drop most of our non-voting jobs because
they are taking up resources and always failing. This should
decrease the amount of resources we're consuming.
Also, instances are failing to launch when jobs hit any nodepool
VMs inside OVH.
Reviewed: https:/ /review. openstack. org/590778 /git.openstack. org/cgit/ openstack/ openstack- ansible/ commit/ ?id=80dfbe783de ae48979c1c0093d 4b03fc99029e15
Committed: https:/
Submitter: Zuul
Branch: master
commit 80dfbe783deae48 979c1c0093d4b03 fc99029e15
Author: Jean-Philippe Evrard <email address hidden>
Date: Fri Aug 10 16:02:18 2018 +0200
Temporarily use tempest master for all builds and fix configs
A fix [1] was introduced in openstack-ansible to use tempest from
the master branch in the AIO, but respecting the installation
from PyPI everywhere else. This allowed users to chose
the appropriate behaviour for their use cases.
This patch [1] also made sure we didn't have anything else to do
when the patch would land on stable branches, as this would
automatically get disabled.
However, as of today, there is still no new version of tempest,
and our stable/rocky branch has been cut. Therefore the fix that
was in place is useless and another approach needs to be
taken.
We will move to use tempest master for master and stable/rocky
branch until the fix that caused this series of patch to
happen is released [2] for tempest on PyPI.
A temporary workaround was also added to ensure ceph can still
be built, by freezing the ceph-ansible role sha.
The checksum fill option, was useful a long time ago, but at this point
its just some lovely technical debt that we carry around like an old
dirty security blanket. This change sets us free from the sins of our
past.
We seem to have a lot of jobs that timeout but seem to be very
close to completing, so let's bump the timeout by 20 minutes.
To make up for it, we drop most of our non-voting jobs because
they are taking up resources and always failing. This should
decrease the amount of resources we're consuming.
Also, instances are failing to launch when jobs hit any nodepool
VMs inside OVH.
[1]: https:/ /github. com/openstack/ openstack- ansible/ commit/ abe0b22c7674444 08a10c0c210aa3b 70f319dc95 /github. com/openstack/ tempest/ commit/ 7d2b636a30057ed 8db8cfd4fe2248f 509b3570f1# diff-5c9acbc10d c9d27b47985cd74 ab100f6
[2]: https:/
Change-Id: I42e0cefb281849 64a50f66b18d8eb a6d2a04eca7
Closes-Bug: 1786095
Signed-off-by: Kevin Carter <email address hidden>