Skip to content

Conversation

@danwinship
Copy link
Contributor

4.2 version of #93. Also includes belated glide.yaml fixup for 4.2 deps...

We were requesting api/library-go/client-go master instead of
release-4.2.

Also lock down the versions of some other deps that we don't want to
gratuitously update.
@openshift-ci-robot
Copy link
Contributor

@danwinship: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

WIP: [4.2] Use k8s.io/client-go fork with informer fix, run update-deps

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Jan 20, 2020
@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 20, 2020
@danwinship
Copy link
Contributor Author

/test all

1 similar comment
@danwinship
Copy link
Contributor Author

/test all

@danwinship danwinship force-pushed the fork-k8s-client-go-4.2 branch from d4b6f1f to 6d1ccb4 Compare January 22, 2020 14:09
@danwinship danwinship changed the title WIP: [4.2] Use k8s.io/client-go fork with informer fix, run update-deps [4.2] Use k8s.io/client-go fork with informer fix, run update-deps Jan 22, 2020
@openshift-ci-robot
Copy link
Contributor

@danwinship: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[4.2] Use k8s.io/client-go fork with informer fix, run update-deps

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 the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 22, 2020
@danwinship danwinship changed the title [4.2] Use k8s.io/client-go fork with informer fix, run update-deps Bug 1794029: [4.2] Use k8s.io/client-go fork with informer fix, run update-deps Jan 22, 2020
@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 Jan 22, 2020
@openshift-ci-robot
Copy link
Contributor

@danwinship: This pull request references Bugzilla bug 1794029, which is invalid:

  • expected dependent Bugzilla bug 1794022 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is POST 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.

Details

In response to this:

Bug 1794029: [4.2] Use k8s.io/client-go fork with informer fix, run update-deps

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.

@danwinship
Copy link
Contributor Author

/retest
/bugzilla refresh

@openshift-ci-robot
Copy link
Contributor

@danwinship: This pull request references Bugzilla bug 1794029, which is invalid:

  • expected dependent Bugzilla bug 1794022 to be in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), but it is ON_QA 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.

Details

In response to this:

/retest
/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.

@danwinship
Copy link
Contributor Author

/retest
/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Jan 31, 2020
@openshift-ci-robot
Copy link
Contributor

@danwinship: This pull request references Bugzilla bug 1794029, 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.

Details

In response to this:

/retest
/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 openshift-ci-robot removed the bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. label Jan 31, 2020
@dcbw
Copy link
Contributor

dcbw commented Feb 5, 2020

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Feb 5, 2020
@openshift-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danwinship, dcbw

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@ashcrow
Copy link
Member

ashcrow commented Feb 6, 2020

There are a lot of differences between the original and this backport. However, I believe this to be due to the amount of change and enhancements that have occurred between 4.2 and master.

@ashcrow ashcrow added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 6, 2020
@openshift-merge-robot openshift-merge-robot merged commit 098a641 into openshift:release-4.2 Feb 6, 2020
@openshift-ci-robot
Copy link
Contributor

@danwinship: All pull requests linked via external trackers have merged. Bugzilla bug 1794029 has been moved to the MODIFIED state.

Details

In response to this:

Bug 1794029: [4.2] Use k8s.io/client-go fork with informer fix, run update-deps

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.

@danwinship danwinship deleted the fork-k8s-client-go-4.2 branch February 7, 2020 13:33
@danwinship
Copy link
Contributor Author

There are a lot of differences between the original and this backport. However, I believe this to be due to the amount of change and enhancements that have occurred between 4.2 and master.

It's not 4.2 vs master, it's just that we previously had basically 4.2.0 (or maybe even 4.2 alpha or something), and now we have something 4.2.z-ish with various bugfixes.

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/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. 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.

5 participants