Comment 2 for bug 1982942

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-quickstart (master)

Reviewed: https://review.opendev.org/c/openstack/tripleo-quickstart/+/851214
Committed: https://opendev.org/openstack/tripleo-quickstart/commit/f50d529ccafd173bec580d806b171ffffacd564a
Submitter: "Zuul (22348)"
Branch: master

commit f50d529ccafd173bec580d806b171ffffacd564a
Author: Chandan Kumar (raukadah) <email address hidden>
Date: Wed Jul 27 17:31:51 2022 +0530

    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) <email address hidden>
    Change-Id: I06a1784931abb7eb1bab7fc9dcd8be2cc14cfb66