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-1463: add [apigroup] annotation to skip tests for MicroShift #28061

Merged
merged 3 commits into from Jul 26, 2023

Conversation

chiragkyal
Copy link
Member

@chiragkyal chiragkyal commented Jul 18, 2023

add [apigroup:operator.openshift.io] and [apigroup:oauth.openshift.io] annotations to skip tests for MicroShift
USHIFT-1463

@chiragkyal chiragkyal changed the title add [apigroup:oauth.openshift.io] for failing OAuthServer test add [apigroup] annotation to skip tests for MicroShift Jul 18, 2023
@chiragkyal
Copy link
Member Author

/retest

@chiragkyal chiragkyal changed the title add [apigroup] annotation to skip tests for MicroShift USHIFT-1463: add [apigroup] annotation to skip tests for MicroShift Jul 19, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 19, 2023

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

In response to this:

add [apigroup] annotation to skip tests for MicroShift

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-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 19, 2023
@openshift-ci-robot
Copy link

openshift-ci-robot commented Jul 19, 2023

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

In response to this:

add [apigroup] annotation to skip tests for MicroShift
USHIFT-1463

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-robot
Copy link

openshift-ci-robot commented Jul 19, 2023

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

In response to this:

add [apigroup:operator.openshift.io] and [apigroup:oauth.openshift.io] annotations to skip tests for MicroShift
USHIFT-1463

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.

@ingvagabund
Copy link
Member

@chiragkyal to make the review easier and faster would you please provide a location or a reason for why these additional groups are needed? It can be either a client invocation, need for an endpoint that is exposed only when e.g. oauth server is running, etc. Some of the dependencies can be hidden pretty deep.

@chiragkyal
Copy link
Member Author

@ingvagabund I will try to elaborate on my understanding and reasoning for this change.

  • multinetpolicy.go
    "[sig-network][Feature:MultiNetworkPolicy][Serial] should enforce a network policies on secondary network IPv6 [Suite:openshift/conformance/serial]"
    "[sig-network][Feature:MultiNetworkPolicy][Serial] should enforce a network policies on secondary network IPv4 [Suite:openshift/conformance/serial]"
    

These tests depend upon networks.operator.openshift.io resource under operator.openshift.io apigroup which is not present in MicroShift and causes error

multinetpolicy.go:193: the server could not find the requested resource (get networks.operator.openshift.io cluster)

getCluserNetwork() is looking for this resource.


  • redirect_uris.go

    "[sig-auth][Feature:OAuthServer] OAuthClientWithRedirectURIs must validate request URIs according to oauth-client definition [Suite:openshift/conformance/parallel]"
    

    It depends upon oauthclients.oauth.openshift.io and getting invoked inside generateRedirectURIOAuthClient()

  • well_known.go

    "[sig-auth][Feature:OAuthServer] well-known endpoint should be reachable [apigroup:route.openshift.io] [Suite:openshift/conformance/parallel]"
    

    It also depends upon oauth.openshift.io apigroup.

As oauth.openshift.io is not present in MicroShift, there are errors while running these tests.

-> redirect_uris.go:60: the server could not find the requested resource (post oauthclients.oauth.openshift.io)

-> well_known.go:32: the server could not find the requested resource

  • storageclass.go

    "[sig-storage][Feature:DisableStorageClass][Serial] should not reconcile the StorageClass when StorageClassState is Unmanaged": " [Suite:openshift/conformance/serial]"
    "[sig-storage][Feature:DisableStorageClass][Serial] should reconcile the StorageClass when StorageClassState is Managed": " [Suite:openshift/conformance/serial]"
    "[sig-storage][Feature:DisableStorageClass][Serial] should remove the StorageClass when StorageClassState is Removed": " [Suite:openshift/conformance/serial]"
    

    These tests depend upon clustercsidrivers.operator.openshift.io and getting invoked inside GetSCState() function which is causing error in MicroShift due to missing operator.openshift.io apigroup.

    storageclass.go:148: the server could not find the requested resource (get clustercsidrivers.operator.openshift.io topolvm.io)
    

As per my understanding, all these tests somehow need oauth.openshift.io or operator.openshift.io apigroup which are not present in MicroShift. So, adding annotations can help skip them.

@ingvagabund
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 25, 2023
@ingvagabund
Copy link
Member

/approve

@chiragkyal
Copy link
Member Author

/assign stlaz

@chiragkyal
Copy link
Member Author

/assign bparees

@jsafrane
Copy link
Contributor

/approve
storage test tag

@mfojtik
Copy link
Member

mfojtik commented Jul 25, 2023

/lgtm
/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 25, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chiragkyal, ingvagabund, jsafrane, mfojtik

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 Jul 25, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 716645d and 2 for PR HEAD 3f9c724 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jul 25, 2023

@chiragkyal: 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-aws-ovn-single-node-upgrade 3f9c724 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-openstack-ovn 3f9c724 link false /test e2e-openstack-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/test-infra repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD d9d76e2 and 1 for PR HEAD 3f9c724 in total

@openshift-merge-robot openshift-merge-robot merged commit 7b00201 into openshift:master Jul 26, 2023
21 of 23 checks passed
@chiragkyal chiragkyal deleted the fix-oauth branch July 26, 2023 09:07
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.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants