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-4.3] Bug 1821318: feat(packagemanifest): add default os/arch labels if not present #1432

Conversation

shawn-hurley
Copy link
Member

@shawn-hurley shawn-hurley commented Apr 7, 2020

Description of the change:
Manual cherry-pick of: #1220

Motivation for the change:

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 /docs
  • Commit messages sensible and descriptive

@openshift-ci-robot
Copy link
Collaborator

@shawn-hurley: This pull request references Bugzilla bug 1821318, which is invalid:

  • expected dependent Bugzilla bug 1796080 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED instead
  • expected dependent Bugzilla bug 1819891 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (DUPLICATE) instead
  • expected dependent Bugzilla bug 1796080 to target the "4.4.0" release, but it targets "4.2.z" instead
  • expected dependent Bugzilla bug 1819891 to target the "4.4.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1821318: feat(packagemanifest): add default os/arch labels if not present

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 added the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Apr 7, 2020
@shawn-hurley shawn-hurley changed the title Bug 1821318: feat(packagemanifest): add default os/arch labels if not present [release-4.3] Bug 1821318: feat(packagemanifest): add default os/arch labels if not present Apr 7, 2020
@shawn-hurley
Copy link
Member Author

/bugzilla refresh

@openshift-ci-robot
Copy link
Collaborator

@shawn-hurley: This pull request references Bugzilla bug 1821318, which is invalid:

  • expected dependent Bugzilla bug 1796080 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED instead
  • expected dependent Bugzilla bug 1819891 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (DUPLICATE) instead
  • expected dependent Bugzilla bug 1796080 to target the "4.4.0" release, but it targets "4.2.z" instead
  • expected dependent Bugzilla bug 1819891 to target the "4.4.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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
Copy link
Collaborator

@shawn-hurley: This pull request references Bugzilla bug 1821318, which is invalid:

  • expected dependent Bugzilla bug 1796080 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED instead
  • expected dependent Bugzilla bug 1819891 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (DUPLICATE) instead
  • expected dependent Bugzilla bug 1796080 to target the "4.4.0" release, but it targets "4.2.z" instead
  • expected dependent Bugzilla bug 1819891 to target the "4.4.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

[release-4.3] Bug 1821318: feat(packagemanifest): add default os/arch labels if not present

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.

@ecordell
Copy link
Member

ecordell commented Apr 7, 2020

/test unit

@shawn-hurley
Copy link
Member Author

/bugzilla refresh

@openshift-ci-robot
Copy link
Collaborator

@shawn-hurley: This pull request references Bugzilla bug 1821318, which is invalid:

  • expected dependent Bugzilla bug 1796080 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED instead
  • expected dependent Bugzilla bug 1819891 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (DUPLICATE) instead
  • expected dependent Bugzilla bug 1796080 to target the "4.4.0" release, but it targets "4.2.z" instead
  • expected dependent Bugzilla bug 1819891 to target the "4.4.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@ecordell
Copy link
Member

ecordell commented Apr 7, 2020

/test unit

@ecordell
Copy link
Member

ecordell commented Apr 8, 2020

the unit test failure looks legit and related to these changes

@shawn-hurley
Copy link
Member Author

/bugzilla refresh

@openshift-ci-robot
Copy link
Collaborator

@shawn-hurley: This pull request references Bugzilla bug 1821318, which is invalid:

  • expected dependent Bugzilla bug 1796080 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED instead
  • expected dependent Bugzilla bug 1819891 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (DUPLICATE) instead
  • expected dependent Bugzilla bug 1796080 to target the "4.4.0" release, but it targets "4.2.z" instead
  • expected dependent Bugzilla bug 1819891 to target the "4.4.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@shawn-hurley
Copy link
Member Author

/retest

@shawn-hurley
Copy link
Member Author

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. label Apr 28, 2020
@openshift-ci-robot
Copy link
Collaborator

@shawn-hurley: This pull request references Bugzilla bug 1821318, which is invalid:

  • expected dependent Bugzilla bug 1796080 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ASSIGNED instead
  • expected dependent Bugzilla bug 1819891 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is CLOSED (DUPLICATE) instead
  • expected dependent Bugzilla bug 1796080 to target a release in 4.4.0, 4.4.z, but it targets "4.2.z" instead
  • expected dependent Bugzilla bug 1819891 to target a release in 4.4.0, 4.4.z, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/bugzilla refresh

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.

@shawn-hurley
Copy link
Member Author

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Apr 28, 2020
@openshift-ci-robot
Copy link
Collaborator

@shawn-hurley: This pull request references Bugzilla bug 1821318, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.3.z) matches configured target release for branch (4.3.z)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1804851 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1804851 targets the "4.4.0" release, which is one of the valid target releases: 4.4.0, 4.4.z
  • bug has dependents

In response to this:

/bugzilla refresh

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.

@ecordell
Copy link
Member

/approve
/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 28, 2020
@openshift-ci-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ecordell, shawn-hurley

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-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 28, 2020
@openshift-bot
Copy link
Contributor

/retest

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

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

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

@sdodson
Copy link

sdodson commented May 1, 2020

@shawn-hurley Can you cherry-pick-approved this PR while I track down why I was removed from the operator-framework org?

@shawn-hurley shawn-hurley added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 1, 2020
@openshift-bot
Copy link
Contributor

/retest

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

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

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

@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 7048c43 into operator-framework:release-4.3 May 1, 2020
@openshift-ci-robot
Copy link
Collaborator

@shawn-hurley: All pull requests linked via external trackers have merged: operator-framework/operator-lifecycle-manager#1432. Bugzilla bug 1821318 has been moved to the MODIFIED state.

In response to this:

[release-4.3] Bug 1821318: feat(packagemanifest): add default os/arch labels if not present

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.

@shawn-hurley
Copy link
Member Author

/cherry-pick release-4.2

@openshift-cherrypick-robot

@shawn-hurley: #1432 failed to apply on top of branch "release-4.2":

error: Failed to merge in the changes.
Using index info to reconstruct a base tree...
M	pkg/package-server/provider/registry.go
M	pkg/package-server/provider/registry_test.go
M	pkg/package-server/storage/reststorage.go
M	pkg/package-server/storage/subresources_test.go
M	test/e2e/packagemanifest_e2e_test.go
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/packagemanifest_e2e_test.go
CONFLICT (content): Merge conflict in test/e2e/packagemanifest_e2e_test.go
Auto-merging pkg/package-server/storage/subresources_test.go
Auto-merging pkg/package-server/storage/reststorage.go
CONFLICT (content): Merge conflict in pkg/package-server/storage/reststorage.go
Auto-merging pkg/package-server/provider/registry_test.go
CONFLICT (content): Merge conflict in pkg/package-server/provider/registry_test.go
Auto-merging pkg/package-server/provider/registry.go
CONFLICT (content): Merge conflict in pkg/package-server/provider/registry.go
Patch failed at 0001 feat(packagemanifest): add default os/arch labels if not present

In response to this:

/cherry-pick release-4.2

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.

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. bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants