OCPBUGS-37706: allow TLS1.3 or modern profile to be specified#2135
OCPBUGS-37706: allow TLS1.3 or modern profile to be specified#2135openshift-merge-bot[bot] merged 1 commit intoopenshift:masterfrom
Conversation
|
@sanchezl: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
|
@sanchezl: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
|
/hold until all operators support tls 1.3 Known issues: |
|
@sanchezl: This pull request references Jira Issue OCPBUGS-37706, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. 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. |
|
/jira refresh |
|
@wangke19: This pull request references Jira Issue OCPBUGS-37706, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
The PR has been pre-merge tested, got the expected results, detail see https://issues.redhat.com/browse/OCPBUGS-37706?focusedId=26306896&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-26306896 |
|
/label qe-approved |
|
@sanchezl: This pull request references Jira Issue OCPBUGS-37706, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
|
/test verify-commits |
|
/hold cancel |
|
@sanchezl: the contents of this pull request could not be automatically validated. The following commits could not be validated and must be approved by a top-level approver:
Comment |
|
/retest-required |
|
/retest |
|
/retest-required |
11 similar comments
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/retest-required |
|
/test e2e-aws-ovn-serial |
3 similar comments
|
/test e2e-aws-ovn-serial |
|
/test e2e-aws-ovn-serial |
|
/test e2e-aws-ovn-serial |
|
@sanchezl: 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. |
|
@sanchezl: Jira Issue OCPBUGS-37706: All pull requests linked via external trackers have merged: Jira Issue OCPBUGS-37706 has been moved to the MODIFIED state. 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. |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-pod |
|
[ART PR BUILD NOTIFIER] Distgit: kube-proxy |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-hyperkube |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-kube-apiserver-artifacts |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-hyperkube |
|
[ART PR BUILD NOTIFIER] Distgit: ose-installer-kube-apiserver-artifacts |
|
/cherry-pick release-4.18 |
|
@wangke19: new pull request created: #2315 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 kubernetes-sigs/prow repository. |
No description provided.