openstack/openstack-ansible-repo_server
Code Issues Proposed changes

Have a symlink to u_c versioned file

Browse Source 
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
This commit is contained in:
Dmitriy Rabotyagov 2022-05-19 18:22:00 +02:00 committed by Dmitriy Rabotyagov
parent 1f39aa0239
commit a5df0d1a9b
1 changed files with 10 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
tasks/repo_install_constraints.yml
View File

@ -49,4 +49,13 @@
dest: "{{ repo_service_home_folder }}/repo/constraints/" dest: "{{ repo_service_home_folder }}/repo/constraints/"
owner: "{{ repo_service_user_name }}" owner: "{{ repo_service_user_name }}"
group: "{{ repo_service_group_name }}" group: "{{ repo_service_group_name }}"
mode: 0644 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