trunk.registry.rdoproject.org going to decomission
soon. This patch remove trunk.registry from
tripleo-ci repo.
This patch also removes Dockerfile_rhui.j2 template,
which is used internally. No need to keep it in the
upstream.
Signed-off-by: Amol Kahat <amolkahat@gmail.com>
Change-Id: I11bc7cc37af6271fac7c651c8598a741cf0af783
The linked script was removed in 0977f8502d
some time ago, as part of a general refactoring effort.
Signed-off-by: Jiri Podivin <jpodivin@redhat.com>
Change-Id: I655fdc3d28debe07f529a26df24cdcefb88dfdc8
Changing container registry in testenv to quay so that periodic and check/gate jobs pull from quay instead of trunk.registry.rdoproject
We are doing this only for master, wallaby c9, wallabyc8 and train c8 at the moment
testproj: https://review.rdoproject.org/r/c/testproject/+/42265
Change-Id: Iaa1b172335e662457fb94410093d20892df7327b
Some variables like tempestmail_log_server and tempest_track_resources
are no longer required because it belongs to validate-tempest role, that
is deprecated now. Other variables like tempest_test_image_path and
tempest_tempest_conf_overrides should be used only when required. In the
case of these testenv, this is overriding what is in tempest.yml task in
tripleo-quickstart-extras, making it hard to change cirros image.
Removing here will have no impact, and all common tempest variables
should indeed be centralized in tempest.yml task.
Change-Id: I66da92fcabf204ab9ed3653132ee5221c220c5a0
We should never use registry_ip_address var instead relying on
registry_ip_address_branch to avoid related-bug.
This removes registry_ip_address from returned zuul data and
updates the last few references to it.
For the install-built-repo pre-run play we can't rely on
release to determine the right ip_address_branch. This re-uses
logic from the build-containers role after moving it to its own
tasks file to prevent duplication.
Change-Id: Id594d301d18bc33753e56ef3b7519e36a396cd82
Related-Bug: 1904565
https://review.opendev.org/#/c/752685 changed all
jobs to use trunk.registry.rdoproject.org registry
for all rdo third party jobs but in RDO we run jobs
that build/deploy containers so we have to use
the local registry that is setup in jobs instead of relying on
external registeries.
This patch ensures correct registeries are used.
Change-Id: I9245d4c89e63ec71a102240e9ceaad18b5b14878
In order to reduce dependency on docker.io, let's consume
containers from rdo registry in software factory jobs and
since they exists in same cloud, so it will pretty much
faster.
We are setting the same for rdo and vexxhost cloud.
Depends-On: https://review.opendev.org/#/c/753265/
Change-Id: I372be4816b9c068259f7742a5be68dbb5934dd2b
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
The image URL should be defined in release files.
Currently, the OVB settings are overwriting the 'human-
readable' URLs with hash-related ones and failing jobs
in the component pipeline.
Change-Id: I1a8eb6d4458177e6ff84923e60d2194ce1e24888
The url download.cirros-cloud.net is blocked
from rdo nodes. Create a backup of the image
on images.rdoproject.org
Related-Bug: 1867807
Change-Id: Ibe5ff806539479fb94d4a61aff9ac06a883a6895
Previously the images were hosted on rdo-cloud which was pointed
to certain IP address for rcm server and other images were hosted
on images.rdoproject.org.
In order to move the images to a new host, we can have created
images-vexxhost.r.o and tested the migration there. Since it
is working fine.
In order to reuse the name images.r.o in the new cloud, we need
to switch off the old server and populate the new dns images.r.o
on new cloud via taking an intermediate dns images-vexxhost.r.o
dns. We tested the intermediate dns.
https://softwarefactory-project.io/r/#/c/17428 populates the dns
record to images.rdoproject.org and also keeps
images-vexxhost.rdoproject.org domain. In order to keep the name
consistent, it switches to images.rdoproject.org and reuse the same.
https://tree.taiga.io/project/tripleo-ci-board/task/1538
Depends-On: https://softwarefactory-project.io/r/#/c/17428
Change-Id: Idb97bdf4a7fe6d1d924ceded238c1d3dcdcb372c
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
in ovb and ovb-rdocloud.yaml, for RHEL-8 overcloud_image_url and
ipa_image_url, release and dlrn_hash/tag was hardcoded to master
and due to this master image gets pulled in train job also leading
to unwanted to RHEL8 fs01 train job.
Closes-Bug: #1853978
Change-Id: I737c6c272448eca14683b845563102afd0fc0f96
Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com>
Use dynamical settings for DNS, avoid using them as extra vars
Depends-On: https://review.openstack.org/636438
Change-Id: I13e3cacef6a4a37765ee79ce9029d38bc1ce4d3d
Determining the root cause of ironic issues
is difficult when using an unstable cloud.
By default let's dump the network traffic to
make our lives easier.
Related-Bug: #1797526
Depends-On: Ibee6ba188585f80f0f7d136c81146096cb4432c2
Change-Id: I68f05756770909bea53b288f10dd255a9e3c8129
Required for testing fs053 - where the cloud
and logging hosts have to be set.
Also add browbeat playbook to ovb playbooks list.
Only to be run conditionally.
Change-Id: Ice5de11d0c0ac0a808a0036f57a3f91b73a961bd
- OVB and multinode/singlemode jobs are passed different settings
files based on the location where the jobs run. This review
changes toci-gate-test to pass both the general and rdocloud
multinode setting files as is the case with OVB.
- Removes the period job registry definitions.
These should be passed in release files only.
- Sets update_containers to run with
containerized_overcloud or containerized_undercloud
Closes-Bug: #1775874
Change-Id: I8f498073f1df9de70372f09b8c43e0d4adb5b42a
Because of problems with 7.5 centos and containers disable
containers update on OVB as it was disabled in multinode:
I95c2492dceaebc123a9bed2d6cec06a9fdbcc70d
Change-Id: I02efde7bb3ba32f562a1b3ed7331711d593d603f
Jobs are downloading the image from cirros (which leads sometimes to dns
error) even though the image is cached locally. Change it to use the
local cirros image instead of download it again
Change-Id: I5f9607bc029a68f4a73a12305ea8e1d605551f15
We started to use the same namespace in all docker registries, so
configure it always as tripleo{{release}}
Change-Id: Ie5ee173dd35a6a5fa22d3c5a7bc0a3e4d57f9672
With https://review.openstack.org/#/c/545873/ docker
registry variables always set to "docker.io" for both
periodic and patch jobs because comparison of string
is done with integer which returns "false" always, this patch
fixes it.
Change-Id: Iea10d6bff3b0c0b3f440372326ec221d94e95838
Use trunk.registry.rdoproject.org for periodic (promotion) jobs
only, and docker.io for patch jobs.
Change-Id: I91aebe40667f6737fdf2676dd4e8030076c6eaa8
This reverts commit 958d374d6a.
This commit changed docker registry for promotion jobs, so it's
blocking all promotions now. Let's find another way to use
docker.io for patches only and rdoproject for promotions only.
Change-Id: I735380d7e68139a6faf207bd46c5495206fa804e
trunk.registry.rdoproject.org is not meant for production or stable
use. It is a staging ground where containers are tested for promotion
purposes before being pushed to docker.io.
Change-Id: I21635497924f440ecc6ee1bad2410b552ac752c1
This review adds the setting to enable updating the containers
to the RDO Cloud testenv config files.
Change-Id: Ib1dd68dc547159384a3aba47543f1a37a4a781b5
Configure all RDO cloud jobs to send statistics from ARA to
InfluxDB server in RDo cloud.
Depends-On: I50da9da53a702982f53d148b9851657612f237e5
Change-Id: I97504da321a70837756265ada74ce52354a58f08
zuul-cloner is now checking out changes to
"/home/zuul/git.openstack.org/openstack"
Closes-Bug: #1737042
Change-Id: I9739dbcac551f234b595060cf257be91247a5d65
Tempestmail needs to know in which url the logs are stored.
By default it uses logs.openstack.org, however, since these jobs are
being executed in rdo-cloud and logs stored in a different server, this
set is required when the email is send point to the proper url.
Change-Id: I9ccb073da4485a1d0fc9fe6ae8cca3d36dd6f081
Depends-On: Iab9b448551d1a2ed59b47f91d5a9bcc204e0a703
Jobs deploying with containerized overcloud are running with
docker.io -based settings. This review changes jobs running
on RDO Cloud to use rdoproject images and container settings.
Depends-On: Id8f0e4e2af57e8840d0aeb7eb9b9620e48d05279
Change-Id: I4d15094f9b8d0e4a9463a5f9b4e7a689a1585211
It's a loss of time and useless since we have no access to the machines
to debug if needed.
Change-Id: Ia4291c18c8b4fe331b0b8b09eb605abc0776f7e0
Co-Authored-By: Alex Schultz <aschultz@redhat.com>
Related-Bug: #1659065
Like we already do for multinode jobs, enable Debug: True in all OVB
jobs run by TripleO and RDO CIs.
It will activate debug=true for OpenStack services which should help
people who debug the CI jobs to have more verbosity.
Note: we have to override workers_args and include the defaults values
again:
bdb69476fd/roles/overcloud-deploy/tasks/pre-deploy.yml (L169)
Change-Id: Icb46dd9d0b59c26b1e2dcbec0d2574daee9ebf6a
With master deploys, especially containeried builds,
the undercloud (when created) and baremetal nodes need
more resources. This review changes those flavors to be xlarge
to avoid 'no available hosts' errors.
Change-Id: Id18095fe90f727f14af35e318fff856aaa5984a6
Adding settings to make tripleo-ci OVB jobs work in RDO Cloud.
- add and conditionally load infrastructure servers IP settings
- disable network sharing since we are not admins in RDO Cloud
- modify flavor settings to match RDO Cloud requirements
- add additional ovb environment file for RDO Cloud settings
Change-Id: I032d6e3558a44d4f90a0de092dec980e95d1f33e
Ghanshyam Mann
yatinkarel