Enable separate rhos release args for compute nodes#3680
Enable separate rhos release args for compute nodes#3680michburk wants to merge 1 commit intoopenstack-k8s-operators:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Build failed (check pipeline). Post https://softwarefactory-project.io/zuul/t/rdoproject.org/buildset/2ca51abff0a843c487020b7bad880825 ✔️ openstack-k8s-operators-content-provider SUCCESS in 2h 44m 17s |
75dfd35 to
006eeea
Compare
859b760 to
930fa24
Compare
Adds a var to the reproducer task where rhos release repos are installed, allowing the calling tasks to use different args from the cifmw_repo_setup_rhos_release_args. Signed-off-by: Michael Burke <michburk@redhat.com>
930fa24 to
ba893af
Compare
Adds a var to the reproducer task where rhos release repos are installed, allowing the calling tasks to use different args from the cifmw_repo_setup_rhos_release_args.
Makes it possible for the compute nodes to run a separate rhel version from the hypervisor/controller-0 and use the correct rhos-release args for this different rhel version.
Note that downstream, many vars like
cifmw_repo_setup_rhos_release_argsare defined in some variable file likedefault-vars.yamland passed to theansible-playbook reproducer.yml ...invocation via-e. Since extravars have the highest precedence in ansible, it is impossible to overwrite these vars with other values, hence ugly variable overriding pattern.