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

Remove operatorgroup queueinformer #2753

Merged
merged 1 commit into from
Apr 29, 2022

Conversation

exdx
Copy link
Member

@exdx exdx commented Apr 27, 2022

Description of the change:
An operatorgroup queueinformer was introduced in #2728.
The operatorgroup syncer was calling the syncResolvingNamespace
function, which expects a namespace object as an argument, with an
operatorgroup instead. This led to casting errors.

Since there is no need for an operatorgroup queueinformer, only a lister, the queueinformer can be removed entirely.

Motivation for the change:
Downstream bug

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

@exdx exdx changed the title Remove syncResolvingNamespace syncer from operatorgroup queueinformer Remove operatorgroup queueinformer Apr 27, 2022
@exdx exdx requested a review from awgreene April 28, 2022 17:31
@awgreene
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2022
@awgreene
Copy link
Member

The commit message is a bit off eh? We should probably just mention that we no longer:

  • Use a queue informer.
  • Kickoff the syncNamespace function whenever we get an operatorGroup event.

@exdx
Copy link
Member Author

exdx commented Apr 28, 2022

The commit message is a bit off eh? We should probably just mention that we no longer:

* Use a queue informer.

* Kickoff the syncNamespace function whenever we get an operatorGroup event.

Yeah I think it's probably overly-verbose. I will fix it up.

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2022
@awgreene
Copy link
Member

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 29, 2022
@awgreene
Copy link
Member

/hold

Commit has @exdx's signature as its header.

@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 Apr 29, 2022
@exdx exdx force-pushed the fix/og-syncer branch 2 times, most recently from af29d9c to e032d48 Compare April 29, 2022 13:15
@exdx
Copy link
Member Author

exdx commented Apr 29, 2022

Fixed! Sorry about that.

/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 Apr 29, 2022
@openshift-ci
Copy link

openshift-ci bot commented Apr 29, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: awgreene, exdx, 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 [awgreene,timflannagan]

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

Removes the unneccesary operatorgroup queueinformer, since only an
operatorgroup lister is needed. Also ensures that the syncResolvingNamespace function is no longer triggered by operatorgroup events.

Signed-off-by: Daniel Sover <[email protected]>
@timflannagan
Copy link
Member

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 29, 2022
@openshift-merge-robot openshift-merge-robot merged commit dc7b00b into operator-framework:master Apr 29, 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.

4 participants