octavia-api's cli app doesn't behave well with haproxy so let's run
under apache and save ourselves some grief. Also adds cleanup for the
octavia-api tls proxy in update and upgrade tasks if it was previously
deployed.
Also updates zuul layout for multinode job to track changes to new
flattened octavia service files.
Closes-Bug: #1815811
Change-Id: Ied7cb31fbf1222694250e4769573bcbb82ba5bea
We now have a deployment directory where we are moving all services.
This is new in Stein and it won't be backported.
Change-Id: I52039deaa8ff459de5afbfeb3e2c54eb8908bb3f
Change order of default tox envlist in order of likeliness to fail on a
new change and add py37 and py36.
Change-Id: If72e480c12385463088e2e0962801cd7095a6f12
We should be running a python3 job for tripleo-heat-templates and since
we dropped the old 3.5 job, let's add the correct 3.6 job.
Change-Id: I93bd7bf988c881496ecee0c5d4e2bc97a5047571
We are running the regular jobs with constraints now so we don't need to
be running this job. Additionally it's not functioning correctly with
the switch to bionic
Change-Id: I41bf5002bd40654d55456a5cdafcef6b76b1f62e
..for Greater Good.
NOTE: for example, standalone jobs are defined as a template in
tripleo-ci, and here we are adding and override the listed jobs for the
dependencies/files options. If a job is added to the standlone template
in tripleo-ci, we need to add the job and dependency here manually.
If we won't, that job will be consumed as is and run w/o dependencies.
That is the price to pay for not having overrides managed centrally in
tripleo-ci. The latter wouldn't work neither as a single template
cannot fit all the specific needs of numerous tripleo repos. So the
final call was made to manage overrides via local overrides for tripleo
repos.
Save CI resources and shorten wait-in-zuul-queue times
for other patches, when pep8 checks failed (that is YAML validation
for this t-h-t repo).
For core openstack python projects it might make sense to
not split them apart and run them all together. For things like
TripleO/Kolla/Puppet/etc where we have layers of interactions that can
be affected by the results from the linters/unit jobs it makes
sense to split them out.
For example, in tripleo since we use packages, if the unit test fails
the integration test may fail because when we go to built the package
with the new source, the unit test int he package build fails. Thus
we know that'll be a wasted execution and you won't actually get any
results.
An alternative Today:
patchset one:
pep8 SUCCESS
integration FAILURE
patchset two:
pep8 SUCCESS
integration FAILURE
patchset three:
pep8 SUCCESS
integration SUCCESS
Future:
patchset one:
pep8 FAILURE
integration SKIPPED
patchset two:
pep8 SUCCESS
integration FAILURE
patchset three:
pep8 SUCCESS
integration SUCCESS
This may not be true for devstack but if the unit
tests are failing, then the code is likely bad (backwards
compatibility/wrong assumptions about change/etc) and we shouldn't be
running an actual deployment.
Related upstream ML threads:
* http://lists.openstack.org/pipermail/openstack-dev/2018-March/
127869.html
* http://lists.openstack.org/pipermail/openstack-discuss/
2019-February/003142.html
Change-Id: I2216773113f8d4e4a2bdff35709ff739f5164a32
Signed-off-by: Bogdan Dobrelya <bdobreli@redhat.com>
Congress doesn't seem to be used anywhere, we never had a bug report or
any sign of somebody out there actually using it.
Let's remove its support in TripleO, to reduce the codebase.
Change-Id: Idca6b12f1c0ca3bc15bedf6469d4063a4dac31fa
The ceph-ansible tasks are now invoked with the tripleo-admin user,
which doesn't by default have write access to /var/lib/mistral, but it
does have sudo access.
This change makes /var/lib/mistral/overcloud/ceph-ansible be owned by
the tripleo-admin user so that subsequent tasks can write to that
directory.
Related-Bug: #1813832
Change-Id: I98bb38078be84cbda3e9a9e338af0d054dc53420
In I7cf36baa80e91d87b1b41c45204c61cf87846d34 we started using the
tripleo-standalone-scenarios-full instead of carrying custom
layout for the standalone jobs in projects. Looks like we forgot
to remove the gate definitions here.
Change-Id: I2c3940c7903f9fd4b9d0ec1aca8741182b9c76cd
Fixes reported problem of job running only in check and not in gate:
tripleo-ci-centos-7-scenario000-multinode-oooq-container-updates
Change-Id: I7df8d811287c7605b1b406420de1eb17ae555346
Following addition of [1], replace use of multinode with
standalone job for scenario004
1. https://review.openstack.org/#/c/619520/
Change-Id: Iff1e83dd227fc2e03924f41592f82a555053425d
These are containerized scenario multinode jobs that were
wrongly named.
Depends-On: https://review.openstack.org/#/c/619337
Change-Id: I804b7a39159445cb75ecc8e93897fd7f0f24b630
This job is required to cover designate.
UPDATE:
- Also ensure we run all jobs if zuul.d/* are changed.
- Removed:
tripleo-ci-centos-7-scenario003-multinode-oooq-container
Change-Id: I31ae7f873617b69bfd8fee7010bab133e384795b
Story: https://tree.taiga.io/project/tripleo-ci-board/us/338
https://review.openstack.org/#/c/619337/ switched the jobs to a noop for
master and since this file is branched we no longer need to keep this
template definition in THT.
Change-Id: I305c175392089e103dec85461f289ab38127398d
Normally the listed services are omitted from the scenario jobs
because they are often covered by many other "default" jobs. However,
in the case of the update job, this is our only update job, so we need
to try to run it on a full set of services which are deployed by the
job. Otherwise we risk breaking the gate by merging something that
affects update job without testing it by the update job.
Change-Id: I8115333bb3be27a461f7dab9aba20749ed695a49
An incorrectly indented regexp was causing jobs not to be triggered
correctly.
fixing indentation make the jobs trigger correctly
Change-Id: Ic665dd273aab37dbd689c0a51cb0c3e4f0bc1e56
This is a mechanically generated patch to switch the documentation
jobs to use the new PTI versions of the jobs as part of the
python3-first goal.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: I9e6048085bbd8b1451166f36565f95d556cb8d90
Story: #2002586
Task: #24341
This is a mechanically generated patch to complete step 1 of moving
the zuul job settings out of project-config and into each project
repository.
Because there will be a separate patch on each branch, the branch
specifiers for branch-specific jobs have been removed.
Because this patch is generated by a script, there may be some
cosmetic changes to the layout of the YAML file(s) as the contents are
normalized.
See the python3-first goal document for details:
https://governance.openstack.org/tc/goals/stein/python3-first.html
Change-Id: Idb328be9749bb0aa1d8e8ac748fefce962829928
Story: #2002586
Task: #24341
Some stuff like the new health check were not exercising the
scenarios, the core part of THT need more covarage.
Change-Id: I34da92f57ef96dd3c1f6c3c525a366a578f720aa
We should test scenario009 when services like mistral, haproxy and
keepalived are modified as these have a direct impact either in the
deployment or openshift's architecture.
Change-Id: I40313aa79c22fca0e53ae398807b8d2b0ac7269b
This scenario tests OpenShift deployment managed by TripleO on BM
nodes. We got the job working last week and it's been working fine
since then.
Let's move it to the check queue as a non-voting job for now and,
eventually, make it voting.
Change-Id: Ief28df449e1e37fb9c73ecaf839d3e335abb3ed8
Moving to non-voting until the gate is green
RDO-Cloud is down and we can not fix the
dist-git.
Related-Bug: #1777168
Change-Id: Ia2c18ff554dc8b980528f1905bbad98dced2c336