[FOLIO-2660] duplicate roles in folio-ansible and folio-infrastructure Created: 29/Jun/20  Updated: 30/Jun/20  Resolved: 30/Jun/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: Jakub Skoczen Assignee: John Malconian
Resolution: Done Votes: 0
Labels: devops-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
blocks FOLIO-2633 Jenkins builds broken when okapi-3 un... Closed
Sprint: DevOps: sprint 92
Development Team: FOLIO DevOps

 Description   

There are two versions of the tenant-admin-permissions role in folio-infrastructure. One is local to that repository, one comes from the folio-ansible submodule.

The local version was not updated with the improved CQL query (increasing the result set length and excluding the SYS# permissions), so it was not getting all the permissions and the Ansible task was failing as designed.

The reason there are two versions of the role (and several other roles) is because at some point we could not figure out how to set the roles path for Ansible on Jenkins, so we just worked around it. We now know how to do that: create an Ansible configuration file with a roles_path default and use the ANSIBLE_CONFIG environment variable to point to the config file. Then we can remove all the local copies of the roles.

The environment variable update needs to be made in all the Jenkins jobs that use the Jenkins Ansible plugin.



 Comments   
Comment by David Crossley [ 30/Jun/20 ]

This was handled in the context of FOLIO-2633 Closed .

Generated at Thu Feb 08 23:22:18 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.