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

fix(olm): properly detect cluster operator API #710

Conversation

jpeeler
Copy link

@jpeeler jpeeler commented Feb 13, 2019

This was causing vanilla upstream to crash due to attempting to write to
a not present API.

@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 13, 2019
@jpeeler jpeeler added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. and removed approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 13, 2019
@jpeeler
Copy link
Author

jpeeler commented Feb 13, 2019

Will test this further while doing other installer work.

@jpeeler jpeeler force-pushed the clusteroperator-discovery branch from 2d09672 to 128a431 Compare February 13, 2019 20:23
@openshift-ci-robot openshift-ci-robot added approved Indicates a PR has been approved by an approver from all required OWNERS files. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 13, 2019
@jpeeler
Copy link
Author

jpeeler commented Feb 14, 2019

/retest
haven't tested on openshift yet... so this may really be broken

@jpeeler jpeeler force-pushed the clusteroperator-discovery branch from 128a431 to 13066e9 Compare February 14, 2019 16:51
This was causing vanilla upstream to crash due to attempting to write to
a not present API. Also, disable writing operator status by default
since it's OpenShift specific.
@jpeeler jpeeler force-pushed the clusteroperator-discovery branch from 13066e9 to 059498b Compare February 14, 2019 20:40
@jpeeler
Copy link
Author

jpeeler commented Feb 14, 2019

/retest

2 similar comments
@jpeeler
Copy link
Author

jpeeler commented Feb 14, 2019

/retest

@jpeeler
Copy link
Author

jpeeler commented Feb 15, 2019

/retest

Copy link
Member

@njhale njhale left a comment

Choose a reason for hiding this comment

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

Nice!
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 15, 2019
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jpeeler, njhale

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

@jpeeler jpeeler removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 15, 2019
@njhale
Copy link
Member

njhale commented Feb 15, 2019

/retest

3 similar comments
@jpeeler
Copy link
Author

jpeeler commented Feb 15, 2019

/retest

@jpeeler
Copy link
Author

jpeeler commented Feb 15, 2019

/retest

@jpeeler
Copy link
Author

jpeeler commented Feb 16, 2019

/retest

@jpeeler
Copy link
Author

jpeeler commented Feb 16, 2019

/retest

@openshift-merge-robot openshift-merge-robot merged commit cce4af2 into operator-framework:master Feb 16, 2019
ecordell pushed a commit to ecordell/operator-lifecycle-manager that referenced this pull request Mar 8, 2019
…r-discovery

fix(olm): properly detect cluster operator API
@ecordell ecordell added the kind/bug Categorizes issue or PR as related to a bug. label Mar 19, 2019
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. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants