Chandan Kumar (raukadah) f50d529cca Use nodepool_rdo_proxy url instead of rdo trunk url ... Currently in release file, we have rdo trunk url to lay down dlrn and dlrn-deps repo. In a restricted environment having network instability, curl fails with `could not connect to rdo trunk url error` while laying down the repo. RDO trunk contents are already mirrored on different cloud AFS mirror which are easily accessible. Let use that one and avoid these errors. This issue is seen in IBM cloud. Using nodepool_rdo_proxy url exists with in the cloud fixes the issue. Here is the testproject: https://review.rdoproject.org/r/c/testproject/+/44235/2#message-09494ed17f2f9404b1bac0166ce45514d7ba8d12 Closes-Bug: #1982942 Signed-off-by: Chandan Kumar (raukadah) <chkumar@redhat.com> Change-Id: I06a1784931abb7eb1bab7fc9dcd8be2cc14cfb66		2022-07-28 13:39:59 +05:30
..
CentOS-7	Fix ansible-lint and tox-molecule failures	2022-01-10 15:29:31 -03:00
CentOS-8	Add new featureset66 and update tripleo-inventory for mixed OS jobs	2022-07-15 18:19:40 +03:00
CentOS-9	Use nodepool_rdo_proxy url instead of rdo trunk url	2022-07-28 13:39:59 +05:30
RedHat-8	Remove explicit set for whole_disk_image: true	2021-11-16 16:56:53 +00:00