Infrastructure/ansible
1
0
Fork 0
Code Issues Pull requests 6 Projects Releases Packages Wiki Activity Actions

greenwave: don't gate c-p-standard on container tests

Browse source 
This was wrong and I'm surprised we never noticed till now. We
don't schedule these tests on critical-path-standard so we should
not gate on them. The alternative fix is to keep gating and start
testing, but the only thing that's actually in c-p-standard is
fprintd-pam and we don't pull fprintd stuff into containers, so
there's no sense testing it, really.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2024-04-03 08:15:44 -07:00
parent 660a436c50
commit ca49eaacbc
1 changed files with 0 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
roles/openshift-apps/greenwave/templates/fedora.yaml
View file

@ -174,11 +174,9 @@ decision_contexts:
- bodhi_update_push_testing_critpath
- bodhi_update_push_testing_core_critpath
- bodhi_update_push_testing_critical-path-base_critpath
- bodhi_update_push_testing_critical-path-standard_critpath
- bodhi_update_push_stable_critpath
- bodhi_update_push_stable_core_critpath
- bodhi_update_push_stable_critical-path-base_critpath
- bodhi_update_push_stable_critical-path-standard_critpath
subject_type: bodhi_update
rules:
# This list needs to stay synced with openQA if tests are added or renamed.