Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

USHIFT-647: skip sig-cli explain for CRDs in MicroShift #27996

Merged
merged 2 commits into from Jun 29, 2023

Conversation

chiragkyal
Copy link
Member

@chiragkyal chiragkyal commented Jun 23, 2023

This change will check if a cluster is MicroShift and make changes accordingly for [sig-cli] oc explain should contain proper spec+status for CRDs test.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jun 23, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 23, 2023

@chiragkyal: This pull request references USHIFT-647 which is a valid jira issue.

In response to this:

This change will skip [sig-cli] oc explain should contain proper spec+status for CRDs test if no CRDs exist in a cluster.

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/test-infra repository.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 23, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 23, 2023

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

@@ -579,6 +602,9 @@ var _ = g.Describe("[sig-cli] oc explain", func() {
if *controlPlaneTopology == configv1.ExternalTopologyMode {
crdTypesTest = baseCRDTypes
}
if !doesCRDTypesExist(oc, crdTypesTest) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of skipping the test entirely, let's look for MicroShift and set crdTypesTest to the list we expect to see so we can test that explain works with them.

@chiragkyal
Copy link
Member Author

cc @soltysh

@chiragkyal chiragkyal marked this pull request as ready for review June 26, 2023 12:27
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jun 26, 2023
@openshift-ci openshift-ci bot requested review from bparees and csrwng June 26, 2023 12:28
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jun 26, 2023

@chiragkyal: This pull request references USHIFT-647 which is a valid jira issue.

In response to this:

This change will check if a cluster is MicroShift and make changes accordingly for [sig-cli] oc explain should contain proper spec+status for CRDs test.

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/test-infra repository.

@dhellmann
Copy link
Contributor

@chiragkyal are those test failures known issues for this repo?

@soltysh we discussed the approach Chirag is taking in this PR on slack.

/assign @soltysh
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 27, 2023
@chiragkyal
Copy link
Member Author

I do see some of them are failing in other PRs, also.

/retest

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 28, 2023

@chiragkyal: The following test 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-aws-ovn-single-node 200e86e link false /test e2e-aws-ovn-single-node

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

Copy link
Member

@soltysh soltysh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve
/label tide/merge-method-squash

@openshift-ci openshift-ci bot added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Jun 29, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jun 29, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chiragkyal, dhellmann, soltysh

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

The pull request process is described here

Needs approval from an approver in each of these files:

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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 29, 2023
@openshift-merge-robot openshift-merge-robot merged commit d4faa3d into openshift:master Jun 29, 2023
22 of 23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants