From d32e1f3ea56521e0425262fb3df27d9b2522ed86 Mon Sep 17 00:00:00 2001 From: Alfredo Moralejo Date: Thu, 12 Jul 2018 20:10:52 +0200 Subject: [PATCH] Set update_repo to gating_repo_name parameter In previous releases we used gating_repo_name parameter to set the repositories to be used to update container packages. After moving it to tripleo-modify-image role, repo name is hardcoded to gating-repo but in some cases we need to use a different name (as in RDO rdoinfo jobs), so making it configurable using the same parameter seems to be a good option. Change-Id: I1a7a9edde53ecc85bb347f3c7dc3140aac06985e --- .../templates/containers-prepare-parameter.yaml.j2 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/undercloud-deploy/templates/containers-prepare-parameter.yaml.j2 b/roles/undercloud-deploy/templates/containers-prepare-parameter.yaml.j2 index 225c6eaab..698596fc9 100644 --- a/roles/undercloud-deploy/templates/containers-prepare-parameter.yaml.j2 +++ b/roles/undercloud-deploy/templates/containers-prepare-parameter.yaml.j2 @@ -14,7 +14,7 @@ parameter_defaults: tasks_from: yum_update.yml compare_host_packages: true yum_repos_dir_path: /etc/yum.repos.d - update_repo: gating-repo + update_repo: "{{ gating_repo_name|default('gating-repo') }}" {% endif %} set: tag: "{{ container_build_id }}"