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

test(catalog): add e2e test to verify configmap changes are detected #670

Merged

Conversation

ecordell
Copy link
Member

and recorded on the catalogsource object

This was an attempt to replicate an issue marketplace was seeing, but the test appears to pass with no additional changes.

@openshift-ci-robot openshift-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 15, 2019
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2019
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.

/lgtm

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

njhale commented Jan 15, 2019

/hold

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 15, 2019
@njhale
Copy link
Member

njhale commented Jan 15, 2019

/lgtm cancel
/hold cancel
/test e2e-aws
/joke

@openshift-ci-robot
Copy link
Collaborator

@njhale: I really want to buy one of those supermarket checkout dividers, but the cashier keeps putting it back.

In response to this:

/lgtm cancel
/hold cancel
/test e2e-aws
/joke

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 removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Jan 15, 2019
@njhale
Copy link
Member

njhale commented Jan 15, 2019

/test e2e-aws

@@ -55,8 +55,8 @@ var (
// NOTE: The $Format strings are replaced during 'git archive' thanks to the
// companion .gitattributes file containing 'export-subst' in this same
// directory. See also https://git-scm.com/docs/gitattributes
gitVersion string = "v0.0.0-master+$Format:%h$"
gitCommit string = "$Format:%H$" // sha1 from git, output of $(git rev-parse HEAD)
gitVersion string = "v0.0.0-master+7d04d0e2"
Copy link

Choose a reason for hiding this comment

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

This doesn't look right.

Copy link
Member Author

Choose a reason for hiding this comment

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

It looks like client-go updated the way they generate version strings? What looks off to you?

Copy link

Choose a reason for hiding this comment

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

Copy link
Member Author

Choose a reason for hiding this comment

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

are we seeing the result of:

// NOTE: The $Format strings are replaced during 'git archive' thanks to the
// companion .gitattributes file containing 'export-subst' in this same
// directory. See also https://git-scm.com/docs/gitattributes

I wonder if k8s.io changed to start serving the git archive instead of the git repo?

Copy link

Choose a reason for hiding this comment

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

Maybe so, will assume that's correct.

Copy link

Choose a reason for hiding this comment

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

Nick's PR actually undoes the change in operator-registry, so maybe it was a mistake after all. - operator-framework/operator-registry#19.

@ecordell ecordell force-pushed the configmap-changes branch 2 times, most recently from 32f031c to 4bc3b50 Compare January 15, 2019 19:37
@njhale
Copy link
Member

njhale commented Jan 15, 2019

/retest

2 similar comments
@ecordell
Copy link
Member Author

/retest

@ecordell
Copy link
Member Author

/retest

@njhale
Copy link
Member

njhale commented Jan 16, 2019

/test e2e-aws-olm

3 similar comments
@ecordell
Copy link
Member Author

/test e2e-aws-olm

@ecordell
Copy link
Member Author

/test e2e-aws-olm

@njhale
Copy link
Member

njhale commented Jan 16, 2019

/test e2e-aws-olm

@openshift-ci-robot openshift-ci-robot added size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jan 16, 2019
@njhale
Copy link
Member

njhale commented Jan 17, 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.

/lgtm

@openshift-ci-robot openshift-ci-robot added lgtm Indicates that a PR is ready to be merged. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed lgtm Indicates that a PR is ready to be merged. labels Jan 18, 2019
and recorded on the catalogsource object.

Also verifies that the pod is updated when the configmap changes.
grpc sourcetype takes a new `image` field which specifies an image
which is expected to serve a registry API over grpc on port 50051.
we shouldn't process an installplan unless it has had its status set
by the subscription resolver
and retrigger catalog sync if we attempt to resolve with an unhealthy
catalog

this should fix issues where subscriptions fail when created immedately
after a catalog is updated
@openshift-ci-robot openshift-ci-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jan 18, 2019
@ecordell
Copy link
Member Author

/retest

1 similar comment
@ecordell
Copy link
Member Author

/retest

@smarterclayton
Copy link
Collaborator

/cc so I know when this merges, creates a lot of spam in the e2e runs

@ecordell
Copy link
Member Author

/retest

@njhale
Copy link
Member

njhale commented Jan 18, 2019

/cc so I know when this merges, creates a lot of spam in the e2e runs

@smarterclayton Do all of our PRs create spam in the e2e runs?

@njhale
Copy link
Member

njhale commented Jan 18, 2019

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ecordell, 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

@ecordell
Copy link
Member Author

/retest

1 similar comment
@ecordell
Copy link
Member Author

/retest

@openshift-merge-robot openshift-merge-robot merged commit f3b9375 into operator-framework:master Jan 18, 2019
@ecordell ecordell deleted the configmap-changes branch January 23, 2019 13:29
ecordell pushed a commit to ecordell/operator-lifecycle-manager that referenced this pull request Mar 8, 2019
…nges

test(catalog): add e2e test to verify configmap changes are detected
@njhale njhale added the kind/feature Categorizes issue or PR as related to a new feature. 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/feature Categorizes issue or PR as related to a new feature. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants