OTA-1764: CVO: Add an Optional TLS Scanner Presubmit Job#76044
OTA-1764: CVO: Add an Optional TLS Scanner Presubmit Job#76044openshift-merge-bot[bot] merged 2 commits intoopenshift:mainfrom
Conversation
|
/pj-rehearse pull-ci-openshift-cluster-version-operator-main-e2e-agnostic-ovn |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
e7be9bb to
6a0a818
Compare
|
/pj-rehearse ? |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-cluster-version-operator-main-tls-scanner |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
baf6449 to
817b0e9
Compare
|
/pj-rehearse pull-ci-openshift-cluster-version-operator-main-tls-scanner |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
@DavidHurta: The following test failed, say
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. |
817b0e9 to
a01df69
Compare
|
@DavidHurta: This pull request references OTA-1764 which is a valid jira issue. 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. |
A failing test of the tls-scanner-run step [1] does not fail the whole job [2]. At least, as of the moment. Thus, make the job optional. An always passing job has no significant value. Thus, the job is intended to be used to verify TLS changes explicitly. We'll depend on existing periodic testing and fix things when a regression is reported, if not caught during merging. Use an AWS cluster profile in combination with stronger compute nodes to handle the tls-scanner-run step. The default node type fails to schedule the needed pods by the step. The node type was chosen based on other tls-scanner jobs in the openshift/release repository. [1]: https://steps.ci.openshift.org/reference/tls-scanner-run [2]: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_release/76044/rehearse-76044-pull-ci-openshift-cluster-version-operator-main-tls-scanner/2031796334276644864
a01df69 to
44c491a
Compare
|
@DavidHurta: This pull request references OTA-1764 which is a valid jira issue. 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. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-cluster-version-operator-main-tls-scanner |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
[REHEARSALNOTIFIER]
Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: DavidHurta, fao89 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 |
|
/pj-rehearse ack |
|
@DavidHurta: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
To be used to verify openshift/cluster-version-operator#1338 changes.