TRT-2066: Use OTE generated labels for skips in test-kubernetes-e2e.sh

[smg247]

As part of the deprecation and removal of the annotation framework, we must allow test-kubernetes-e2e.sh to retain current functionality without relying on the annotations. In order to do this, we can rely on the OTE binary's list tests command to get the spec names and their labels. This is possible because the specs have been updated here to also include the reason why they are being skipped as a label, alongside adding the environmentSelector. These labels will then be stored in a map from the spec name to the labels in a generated file. This map will then be appended to the spec name for only the purpose of determining if a test should be skipped in the script.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@smg247: 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:

• 6c66b51|PoC to use OTE generated labels for skips in test-kubernetes-e2e.sh: 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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: smg247
Once this PR has been reviewed and has the lgtm label, please assign tkashem 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

[openshift-ci-robot]

@smg247: 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:

• 6c66b51|PoC to use OTE generated labels for skips in test-kubernetes-e2e.sh: does not specify an upstream backport in the commit message
• e6e59b2|invoke the binary rather than rely on the stored output: 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]

@smg247: 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:

• 6c66b51|PoC to use OTE generated labels for skips in test-kubernetes-e2e.sh: does not specify an upstream backport in the commit message
• e6e59b2|invoke the binary rather than rely on the stored output: does not specify an upstream backport in the commit message
• ea6eff3|cleanup label generation: 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]

@smg247: 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:

• 65b3f12|add the option to omit the annotations when running 'list tests' that is useful when generating the labels, and some more cleanup: does not specify an upstream backport in the commit message
• 6c66b51|PoC to use OTE generated labels for skips in test-kubernetes-e2e.sh: does not specify an upstream backport in the commit message
• e6e59b2|invoke the binary rather than rely on the stored output: does not specify an upstream backport in the commit message
• ea6eff3|cleanup label generation: 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]

@smg247: 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:

• 7abe027|UPSTREAM: : use OTE for spec filtering in e2e tests. this necessitates generating labels that match specs, and appending them to the spec name for that purpose only.: 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.

[smg247]

/hold for #2254 and #2256

[openshift-ci-robot]

@smg247: 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:

• 47a1ac7|UPSTREAM: : use OTE for spec filtering in e2e tests. this necessitates generating labels that match specs, and appending them to the spec name for that purpose only.: 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]

@smg247: This pull request references TRT-2066 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 sub-task to target the "4.19.0" version, but no target version was set.

In response to this:

As part of the deprecation and removal of the annotation framework, we must allow test-kubernetes-e2e.sh to retain current functionality without relying on the annotations. In order to do this, we can rely on the OTE binary's list tests command to get the spec names and their labels. This is possible because the specs have been updated here to also include the reason why they are being skipped as a label, alongside adding the environmentSelector. These labels will then be stored in a map from the spec name to the labels in a generated file. This map will then be appended to the spec name for only the purpose of determining if a test should be skipped in the script.

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]

@smg247: 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:

• 9e967b8|UPSTREAM: : use OTE for spec filtering in e2e tests. this necessitates generating labels that match specs, and appending them to the spec name for that purpose only.: 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.

[smg247]

/hold cancel

[smg247]

/test verify

[smg247]

/test verify

[smg247]

/test verify

[smg247]

/retest-required

[openshift-ci-robot]

@smg247: 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:

• 93f3228|UPSTREAM: : use OTE for spec filtering in e2e tests. this necessitates generating labels that match specs, and appending them to the spec name for that purpose only.: 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.

[smg247]

/retest-required

[smg247]

/retest-required

[openshift-ci]

@smg247: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-agnostic-ovn-cmd	93f3228	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/k8s-e2e-aws-ovn-serial	93f3228	link	false	/test k8s-e2e-aws-ovn-serial
ci/prow/okd-scos-e2e-aws-ovn	93f3228	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-csi	93f3228	link	false	/test e2e-aws-csi
ci/prow/k8s-e2e-gcp-serial	93f3228	link	true	/test k8s-e2e-gcp-serial
ci/prow/k8s-e2e-gcp-ovn	93f3228	link	true	/test k8s-e2e-gcp-ovn

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.