[release-4.18] OCPBUGS-56834: allow TLS1.3 or modern profile to be specified

[openshift-cherrypick-robot]

This is an automated cherry-pick of #2135

/assign wangke19

[openshift-ci-robot]

@openshift-cherrypick-robot: 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:

• 23b3197|UPSTREAM: : allow TLS1.3 or modern profile to be specified: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@openshift-cherrypick-robot: Jira Issue OCPBUGS-37706 has been cloned as Jira Issue OCPBUGS-56834. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-56834: allow TLS1.3 or modern profile to be specified

In response to this:

This is an automated cherry-pick of #2135

/assign wangke19

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-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-56834, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.18.z) matches configured target version for branch (4.18.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note text is set and does not match the template
• dependent bug Jira Issue OCPBUGS-37706 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-37706 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
• bug has dependents

Requesting review from QA contact:
/cc @wangke19

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

This is an automated cherry-pick of #2135

/assign wangke19

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.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 #2315 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[wangke19]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, wangke19
Once this PR has been reviewed and has the lgtm label, please assign deads2k for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[p0lyn0mial]

There’s still no e2e test that automatically validates the modern profile (openshift/origin#29611), and the periodic job (https://prow.ci.openshift.org/job-history/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-tls-13) seems to be permanently failing.

Are we confident about back porting the fix?

/cc @jacobsee @dusk125

[wangke19]

I will take some time to check the root cause for tls13 failed e2e tests.

[p0lyn0mial]

I will take some time to check the root cause for tls13 failed e2e tests.

Thank you!

Also, I have a question for @jacobsee @dusk125: how do we keep track of failures in the periodic job?

[wangke19]

Fixed in PR openshift/origin#29911

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 #2315 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428 #2315

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-tls-13 #2315

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-gcp-ovn openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-tls-13

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/f841c170-4d40-11f0-8f6e-c22952cd3d6f-0

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

[wangke19]

Test results of CI job periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-tls-13: 96a24535-7a0b-4ad3-adeb-bdf2d9b6a5c9, looks good.

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428

[openshift-ci]

@wangke19: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/dc46af30-4db3-11f0-82ac-e8f71330d1dc-0

[wangke19]

/payload-job-with-prs periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-tls-13 openshift/cluster-etcd-operator#1428

The test passed.

[wangke19]

/assign @p0lyn0mial @dusk125 @jacobsee

[openshift-ci]

@openshift-cherrypick-robot: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[wangke19]

Waiting for openshift/origin#29611 first

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[wangke19]

/lifecycle stale

[wangke19]

Depends on openshift/origin#30536