From a5df0d1a9bd4f4a24b578ae0596890f7b345381a Mon Sep 17 00:00:00 2001 From: Dmitriy Rabotyagov Date: Thu, 19 May 2022 18:22:00 +0200 Subject: [PATCH] Have a symlink to u_c versioned file With current behavior of u-c file that is stored on repo server and migration to shared FS instead of lsyncd, we don't have any reliable path to check for. Also we have issue, that with updated u-c SHA users catch "unrelated" error in python_venv_build role. As a solution, we can create a symlink to the u-c file, that will have persistant name and be updated with repo_server role run. That would give us both file to verify and it can be used as u-c URI. Change-Id: Ie7bdb9137ed69be465f014fa811b750dbec4e428 Related-Bug: #1943978 --- tasks/repo_install_constraints.yml | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/tasks/repo_install_constraints.yml b/tasks/repo_install_constraints.yml index 00b0ecf..d118b5f 100644 --- a/tasks/repo_install_constraints.yml +++ b/tasks/repo_install_constraints.yml @@ -49,4 +49,13 @@ dest: "{{ repo_service_home_folder }}/repo/constraints/" owner: "{{ repo_service_user_name }}" group: "{{ repo_service_group_name }}" - mode: 0644 \ No newline at end of file + mode: 0644 + +- name: Create a symlink for constraints file + file: + src: "{{ repo_service_home_folder }}/repo/constraints/{{ 'upper_constraints_' ~ requirements_git_install_branch | default('master') ~ '.txt' }}" + dest: "{{ repo_service_home_folder }}/repo/constraints/upper_constraints_cached.txt" + owner: "{{ repo_service_user_name }}" + group: "{{ repo_service_group_name }}" + state: link + mode: 0644