decouple our qa from epel testing

dmwm / CRABServer

15 stars 37 forks source link

decouple our qa from epel testing #8463

Closed belforte closed 2 weeks ago

belforte commented 4 weeks ago

by default qa gets rpms from epel-testing, not epel. This introduces too many unknwon, uncontrolled chances, especially hen for one reason or another we have several machiines in qa. At the very least we need to be aware. Better yet be ready to disable/enable as proper. Here are instructions (MM):

belforte commented 4 weeks ago

assigning to me to remember to bfing it up for discussion

belforte commented 3 weeks ago

we discussed in the meeting today. Pending a final review with @mapellidario the conclusions are:

stick to epel production for all our VM’s even in qa
Let other people test epel-testing
Lock FTS client version anyhow, like we do for HTCondor and when an updated comes upstream, validate it.

mapellidario commented 3 weeks ago

uh! this was not easy to catch, good job Stefano (and Wa also?)! I definitely agree with all your decisions

aspiringmind-code commented 2 weeks ago

Fixed by disabling epel-testing in data/hostgroup/vocmsglidein.yaml See https://gitlab.cern.ch/ai/it-puppet-hostgroup-vocmsglidein/-/merge_requests/204

Test passed on crab-dev-tw03 See https://gitlab.cern.ch/ai/it-puppet-hostgroup-vocmsglidein/-/merge_requests/205