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

release: Fix verification errors when excluding components #81

Merged
merged 1 commit into from Sep 4, 2019

Conversation

smarterclayton
Copy link
Contributor

Passing --exclude resulted in a verification error because changing
those rules didn't correctly detect that the output is expected to
differ. Instead, we should skip if a user specifies any variants.

Also remove the need to declare "AlwaysInclude", manually verified
that it created the same output.

Needed for creating fake payloads during upgrade testing that lack
machine-config-operator.

Passing --exclude resulted in a verification error because changing
those rules didn't correctly detect that the output is expected to
differ. Instead, we should skip if a user specifies any variants.

Also remove the need to declare "AlwaysInclude", manually verified
that it created the same output.
@smarterclayton
Copy link
Contributor Author

/assign @abhinavdahiya

@openshift-ci-robot openshift-ci-robot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Aug 30, 2019
// another operator.
AlwaysInclude: []string{"cluster-version-operator", "cli", "installer"},
ToImageBaseTag: "cluster-version-operator",
ToImageBaseTag: "cluster-version-operator",
Copy link
Contributor

Choose a reason for hiding this comment

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

Hmm, i am a little surprised as to what changed that the installer always include is not required anymore.. which operator image is requesting this image... looking

Copy link
Contributor

Choose a reason for hiding this comment

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

@abhinavdahiya
Copy link
Contributor

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abhinavdahiya, smarterclayton

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-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit ef1aa2d into openshift:master Sep 4, 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. lgtm Indicates that a PR is ready to be merged. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants