search

adoptium / infrastructure

This repo contains all information about machine maintenance.
Apache License 2.0
86 stars 101 forks source link

Jenkins access issues for `vagrant` machines #2778

Open sxa opened 2 years ago

sxa commented 2 years ago

The infra-vagrant machines have been using an explicit user list to determine who can use them. This should not be the case and the default access for all people in the committers/triage teams should be able to run on those systems (Or possible restricted to the infrastructure* teams)

It's unclear why this was originally done, but I have so far failed to be able to switch it to work any other way. This issue will cover trying to resolve that.

sxa commented 1 year ago

Tested today and it's still a problem: 13:02:13 ?bethgriggs? lacks permission to run on ?infra-ibmcloud-vagrant-x64-1.5? (Same for all five agents) from https://ci.adoptopenjdk.net/view/Tooling/job/VagrantPlaybookCheck/1594/console

sxa commented 1 year ago

Added @bethgriggs to AdoptOpenJDK*infrastructure today and it worked, so that will need some extra analysis to detmine why. Compare https://ci.adoptium.net/job/VagrantPlaybookCheck/OS=Ubuntu2004,label=vagrant/1640/console (FAILED) with https://ci.adoptium.net/job/VagrantPlaybookCheck/OS=Ubuntu2004,label=vagrant/1643/console (worked) So at least we know it's somehow group membership related.

sxa commented 1 year ago

https://ci.adoptium.net/job/VagrantPlaybookCheck/1641/console worked while Beth was added into the infrastructure team, but https://ci.adoptium.net/job/VagrantPlaybookCheck/1646/ still seems to be failing after removing her from that team again, but adding her explicitly to the VPC job ACL.

sxa commented 1 year ago

I'm going to remove this from the March milestone just now as we have a solution (Add users to the infrastructure team) but this should be available to infrastructure-triage too.