The config that sets some jobs as optional (because ci-operator config doesn't record that) was lost when new jobs were cloned to the release-4.1 branches, causing a large number of jobs that are not required to be required (launch-aws, e2e-vsphere).
We need to either manually update these jobs to have the correct optional/always_run settings, or move the optional/always_run config to ci-operator and have the generator.
The optional jobs need to be disabled quickly on release-4.1 so that we don't block fixes going into that branch.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.