This job is failing due to some updates in setuptools and there is
no reason to run it, since it's testing only two roles that have not
being update in the last 3 years. Basically, setuptools complains to
install PyYAML because it has on version 5.4.1 the option license_file
that was deprecated. Updating PyYAML also requires to update all
molecule packages, that introduce different failures, in a snowball
effect.
Change-Id: Id5c21dcea9d183c7fac347323893415f4620cee5
This only works for train->wallaby and t-q-e is branchless. Since this
functionality is deprecated and going to be removed, let's drop the job
from here.
Change-Id: I1cb328d78955b6ff4b8373e767c5bc2dbca10b79
* execute repoclosure directly after the repos are setup
* if zuul.repoclosure is defined, stop multinode-standalone.yml
from fully executing.
* new playbook add in 785690 that exits after repoclosure
Depends-On: https://review.opendev.org/c/openstack/tripleo-ci/+/785690
Change-Id: I420d04c4ae83f8471a2cdd8db1a1d1fa5db63e30
As part of [1] - optimize the zuul layout so that content-provider
doesn't run if openstack-tox-linters is not green. Only applies
to the check queue.
[1] https://review.opendev.org/q/topic:tripleo-ci-reduce
Change-Id: I658458c4cf4b66a8fca40a619bc18f511962b913
using just the build tag allows build-test-packages
to be skipped appropriately in child jobs.
using both tags: undercloud-upgrade, build
allows build-test-packages to run w/o the build
tag. This is not the behavior we're expecting.
Change-Id: Ia693ad7f93749d320264f72ffd18e13196c499ac
When provider_job is set to true, it will pull the container
images from quay.io and will push it to local
registry using non_tripleo_containers.yml.
When consumer_job is set to true in child job, then
custom_ceph_parameters will be setted to true and ceph containers
related namespace will be changed to local registry
to pull the ceph containers so that container built and pushed
to local registry in provider job, will be consumed here.
It also adds standalone job which depends on content provider
job and updates the ceph tag.
Setting +standalone_container_ceph_updates to false as with in
tasks it is setted default to false.
Moved local registry host and port to extra-commons role
to easily share between roles.
It also fix the non_tripleo_containers playbook to exclude kolla
containers for train release.
Note to self:
tripleo-standalone-scenarios-pipeline will be added later
once standalone-upgrade job is ported to centent provider.
Change-Id: Ie3f7bafe3b6ee8a7879ebb3d1d5b47b20181b452
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Co-authored-by: Alex Schultz <aschultz@redhat.com>
If the undercloud nodes is created with entries already
in the /etc/resolv.conf file, the entries added to point to
the IPA server will be added after the existing entries.
This will cause the iIPA enrollment of the client to fail.
This review removes the existing entries before adding the
search domain to avoid the enrollment errors.
Change-Id: I67ebe6c429e89f6f303bf23ca5959e00d6a46df8
This review triggers the job:
tripleo-ci-centos-8-standalone-on-multinode-ipa
to create a multinode setup of two nodes having FreeIPA
server along with standalone deployment
Change-Id: I2f0b0bbcdc7b162f0f25851f20bcdb342ac5b645
We weren't testing containerized tempest in standalone job due the
missing logic on tempest-setup.sh script. This patch adds the logic for
when containerized tempest runs in standalone, copying the clouds.yaml
file instead of the stackrc/undercloudrc and also maintain the logic
when you execute tempest in the ovb, copying the rc file.
This also ensures that /var/lib/tempestdata and /var/log/tempest
directories exists in order to not fail the execution of containerized
tempest.
https://tree.taiga.io/project/tripleo-ci-board/issue/836
Depends-On: https://review.openstack.org/#/c/643212/
Change-Id: I90204150085a1c9b943f9e054c0420a8a5e66538
Related-Bug: 1819440
Will invoke the standalone scenario jobs - Related change in the
template is in [1] so that we get these jobs on changes to the
standalone role. Tracked by CI team in [2]
[1] Ifcbf232b123b4b03856bab448d87dba5a8c7fd43 # tripleo-ci
[2] https://tree.taiga.io/project/tripleo-ci-board/task/625
Change-Id: I9f05d42f84830e4ce7371f2bf284eabef6658acb
Makes those files conformant with current linting rules and avoids
linting errors when we need to toch them again.
Previous doing "pre-commit run -a" uncovered these errors, now is no
longer reporting any other errors.
Change-Id: Ie4cf229c8f11c2b55b323eac23c89483b26d3781
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: I32948e7c6f027bfe7f9660b46d1427de62225af6
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: I5f26ba900e813897cc5f29f97d2a02c708832583
Story: #2002586
Task: #24341
As tripleo-quickstart-extras is branchless repo sometimes there is
need to test code with specific branch or not to break a specific
branch deployment.
Run multinode containers job for release -2 and -1 from master.
Change-Id: Id72870f4d9855749e5d1e048c918fe16f6ab2a35
Depends-On: I31ead90f16473647a1ed60af625f7399699ad112
Zuul no longer requires the project-name for in-repo configuration.
Omitting it makes forking or renaming projects easier.
Change-Id: I80e37a8a3f51aa10bd26fb7aaaff013b7c646057
Define the zuul v3 layout for jobs that we want to execute.
Depends-On: Ie8aa85fe7a8ee556cc1b46e215d329e95913290c
Change-Id: I43ea5bdff4cd282728493047676bc39f045d464a
Ghanshyam Mann