TRT-1776: finish FIPS replacement of blocking aws job #64042
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@sosiouxme: This pull request references TRT-1776 which is a valid jira issue. Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
openshift-ci
bot
added
the
approved
openshift-ci-robot
added
the
rehearsals-ack
|
[REHEARSALNOTIFIER] |
|
@sosiouxme: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sosiouxme, stbenjam The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
This was my blunder in openshift#64042 - the intention was to replace the aws job, not the azure one.
This was my blunder in #64042 - the intention was to replace the aws job, not the azure one.
This was my blunder in openshift#64042 - the intention was to replace the aws job, not the azure one.
This was my blunder in openshift#64042 - the intention was to replace the aws job, not the azure one.
This was my blunder in openshift#64042 - the intention was to replace the aws job, not the azure one.
This was my blunder in openshift#64042 - the intention was to replace the aws job, not the azure one.
3 participants
Job runs like https://prow.ci.openshift.org/view/gs/test-platform-results/logs/aggregated-aws-ovn-upgrade-4.19-micro-fips-release-openshift-release-analysis-aggregator/1912361927552536576 show this aggregating the right job and getting historical comparisons (although with the AWS account issues lately the bar may be a bit low). Occasionally we even get a success (when we are lucky enough to have 6+ jobs get past install). 4.20 looks similar.
This change should reduce AWS account contention a bit by removing 10 aws job runs from every 4.19/4.20 payload.