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

Move operator condition e2e to one namespace per spec #2719

Conversation

perdasilva
Copy link
Collaborator

Signed-off-by: perdasilva perdasilva@redhat.com
Description of the change:
This PR moves the operator condition e2e test suite to one namespace per spec

Motivation for the change:
CI stability

Reviewer Checklist

  • Implementation matches the proposed design, or proposal is updated to match implementation
  • Sufficient unit test coverage
  • Sufficient end-to-end test coverage
  • Docs updated or added to /doc
  • Commit messages sensible and descriptive
  • Tests marked as [FLAKE] are truly flaky
  • Tests that remove the [FLAKE] tag are no longer flaky

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 28, 2022
@perdasilva
Copy link
Collaborator Author

/retest-required

Copy link
Contributor

@timflannagan timflannagan left a comment

Choose a reason for hiding this comment

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

It looks like we're leaking a CRD but other than that, this LGTM:

$  k get operators
NAME                                    AGE
a-vwlbs.operator-conditions-e2e-qfp5m   2m1s
$ k get operators a-vwlbs.operator-conditions-e2e-qfp5m -o yaml
apiVersion: operators.coreos.com/v1
kind: Operator
metadata:
  creationTimestamp: "2022-03-29T13:29:36Z"
  generation: 1
  name: a-vwlbs.operator-conditions-e2e-qfp5m
  resourceVersion: "1918"
  uid: 07b7fea3-aa8a-462c-9cc6-e777fb52f8b2
spec: {}
status:
  components:
    labelSelector:
      matchExpressions:
      - key: operators.coreos.com/a-vwlbs.operator-conditions-e2e-qfp5m
        operator: Exists
    refs:
    - apiVersion: apiextensions.k8s.io/v1
      conditions:
      - lastTransitionTime: "2022-03-29T13:29:38Z"
        message: no conflicts found
        reason: NoConflicts
        status: "True"
        type: NamesAccepted
      - lastTransitionTime: "2022-03-29T13:29:38Z"
        message: the initial names have been accepted
        reason: InitialNamesAccepted
        status: "True"
        type: Established
      kind: CustomResourceDefinition
      name: a-vwlbsrcr7g.cluster.com
$ k get crds
NAME                                          CREATED AT
a-vwlbsrcr7g.cluster.com                      2022-03-29T13:29:38Z
catalogsources.operators.coreos.com           2022-03-29T13:27:26Z
clusterserviceversions.operators.coreos.com   2022-03-29T13:27:26Z
installplans.operators.coreos.com             2022-03-29T13:27:28Z
olmconfigs.operators.coreos.com               2022-03-29T13:27:29Z
operatorconditions.operators.coreos.com       2022-03-29T13:27:30Z
operatorgroups.operators.coreos.com           2022-03-29T13:27:31Z
operators.operators.coreos.com                2022-03-29T13:27:33Z
subscriptions.operators.coreos.com            2022-03-29T13:27:33Z

Signed-off-by: perdasilva <perdasilva@redhat.com>
@timflannagan timflannagan force-pushed the refactor_operator_conditions_e2e branch from 9b291de to e7a2061 Compare March 29, 2022 16:53
@timflannagan
Copy link
Contributor

It looks like we're waiting for the namespace changes, so throwing a hold so it's easier to distinguish between which refactoring PRs are ready to land.

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 29, 2022
Copy link
Contributor

@timflannagan timflannagan left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 30, 2022
@openshift-ci
Copy link

openshift-ci bot commented Mar 30, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva, timflannagan

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:
  • OWNERS [perdasilva,timflannagan]

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

@timflannagan
Copy link
Contributor

/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Mar 30, 2022
@openshift-merge-robot openshift-merge-robot merged commit 4a6b318 into operator-framework:master Mar 30, 2022
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants