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

OCPBUGS-27105: Rebase etcd 3.5.11 openshift 4.11 #241

Conversation

Elbehery
Copy link

This PR rebases etcd 3.5.11 into openshift-4.11.

This PR has been created by this workflow

  • git rebase --rebase-merges --fork-point v3.5.9 v3.5.11 ( rebasing the changes from upstream 3.5.9 --> 3.5.11 )
  • git cherry-pick 4080293a21e5151bd43015795a01c6870124f894
  • git cherry-pick 9c7fcd1d3a675613017af81b16841363434fd93a

After rebasing, running make locally produce

SUCCESS: etcd_build (GOARCH=amd64)
./bin/etcd --version
etcd Version: 3.5.11
Git SHA: 54d1f5cfb
Go Version: go1.20
Go OS/Arch: darwin/amd64
./bin/etcdctl version
etcdctl version: 3.5.11
API version: 3.5
./bin/etcdutl version
etcdutl version: 3.5.11
API version: 3.5

cc @hasbro17 @dusk125 @tjungblu @soltysh @deads2k

yellowzf and others added 30 commits May 16, 2023 11:35
If start grpc proxy with --resolver-prefix, memberlist will return all alive proxy nodes, when one grpc proxy node is down, it is expected to not return the down node, but it is still return

Signed-off-by: yellowzf <zzhf3311@163.com>
[release-3.5]grpcproxy: fix memberlist results not update when proxy node down
fixes bug with multiple endpoints with same prefix

Signed-off-by: Ramil Mirhasanov <ramil600@yahoo.com>
Signed-off-by: Hubert Zhang <hubert.zyk@gmail.com>
[release-3.5]naming/endpoints: backport of etcd-io#15021, fix endpoints prefix bug
Signed-off-by: scuzk373x@gmai.com <zhuanwajiang@pinduoduo.com>
Signed-off-by: daljitdokal <daljit.dokal@yahoo.co.nz>
[3.5] Backport updating go to latest patch release 1.19.10
Signed-off-by: kkkkun <scuzk373x@gmail.com>
Signed-off-by: kkkkun <scuzk373x@gmail.com>
Mitigates etcd-io#15993 by not checking each key individually for permission
when auth is entirely disabled or admin user is calling the method.

Signed-off-by: Thomas Jungblut <tjungblu@redhat.com>
This contains a slight refactoring to expose enough information
to write meaningful tests for auth applier v3.

Signed-off-by: Thomas Jungblut <tjungblu@redhat.com>
…te workflow.

Signed-off-by: James Blair <mail@jamesblair.net>
…ation

[3.5]  Backport .github/workflows: Read .go-version as a step and not separate workflow
[3.5] etcdserver: fix corruption check when server has just been compacted
[3.5] Early exit auth check on lease puts
Signed-off-by: Sameer Natu <sameer.natu@gmail.com>
Add e2e-arm64.yaml and Tests-arm64.yaml to release-3.5
This reverts commit cb38980, reversing
changes made to f565a94.

Changes reversed as scheduled github actions must exist in default branch.

Signed-off-by: James Blair <mail@jamesblair.net>
Signed-off-by: Allen Ray <alray@redhat.com>
Signed-off-by: Thomas Jungblut <tjungblu@redhat.com>
…flags in snapshot restore command

Signed-off-by: Benjamin Wang <wachao@vmware.com>
Signed-off-by: Thomas Jungblut <tjungblu@redhat.com>
[3.5] Adding optional revision bump and mark compacted to snapshot restore
Revert backport of arm64 scheduled workflows
fix the unexpected blocking when using Barrier.Wait(), e.g.
NewBarrier(client, "a").Wait() will block if key "a" is not existed but "a0" is existed, but it should return immediately.

Signed-off-by: zhangwenkang <zwenkang@vmware.com>
[3.5] clientv3: remove v3.WithFirstKey() in Barrier.Wait()
Signed-off-by: shitao.lst <acm_tach@163.com>
@geliu2016
Copy link

/label cherry-pick-approved

@dusk125
Copy link

dusk125 commented Jan 15, 2024

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 15, 2024
@Elbehery
Copy link
Author

/assign @sandeepknd
/assign @geliu2016

@Elbehery
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@Elbehery: This pull request references Jira Issue OCPBUGS-27105, which is invalid:

  • expected dependent Jira Issue OCPBUGS-27102 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@sandeepknd
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Jan 19, 2024
@Elbehery
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@Elbehery: This pull request references Jira Issue OCPBUGS-27105, which is invalid:

  • expected dependent Jira Issue OCPBUGS-27102 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@dusk125
Copy link

dusk125 commented Jan 19, 2024

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 19, 2024
Copy link

openshift-ci bot commented Jan 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dusk125, Elbehery

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 19, 2024
@Elbehery
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@Elbehery: This pull request references Jira Issue OCPBUGS-27105, which is invalid:

  • expected dependent Jira Issue OCPBUGS-27102 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@Elbehery
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@Elbehery: This pull request references Jira Issue OCPBUGS-27105, which is invalid:

  • expected dependent Jira Issue OCPBUGS-27102 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@soltysh
Copy link
Member

soltysh commented Jan 19, 2024

/remove-label jira/invalid-bug
/label jira/valid-bug

4.12 merge din #240, so manually overriding the bug to allow merges

@openshift-ci openshift-ci bot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 19, 2024
@Elbehery
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@Elbehery: This pull request references Jira Issue OCPBUGS-27105, which is invalid:

  • expected dependent Jira Issue OCPBUGS-27102 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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

Retaining the jira/valid-bug label as it was manually added.

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit e73305f into openshift:openshift-4.11 Jan 19, 2024
7 of 8 checks passed
@openshift-ci-robot
Copy link

@Elbehery: Jira Issue OCPBUGS-27105: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-27105 has been moved to the MODIFIED state.

In response to this:

This PR rebases etcd 3.5.11 into openshift-4.11.

This PR has been created by this workflow

  • git rebase --rebase-merges --fork-point v3.5.9 v3.5.11 ( rebasing the changes from upstream 3.5.9 --> 3.5.11 )
  • git cherry-pick 4080293a21e5151bd43015795a01c6870124f894
  • git cherry-pick 9c7fcd1d3a675613017af81b16841363434fd93a

After rebasing, running make locally produce

SUCCESS: etcd_build (GOARCH=amd64)
./bin/etcd --version
etcd Version: 3.5.11
Git SHA: 54d1f5cfb
Go Version: go1.20
Go OS/Arch: darwin/amd64
./bin/etcdctl version
etcdctl version: 3.5.11
API version: 3.5
./bin/etcdutl version
etcdutl version: 3.5.11
API version: 3.5

cc @hasbro17 @dusk125 @tjungblu @soltysh @deads2k

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

This PR has been included in build ose-etcd-container-v4.11.0-202401191731.p0.ge73305f.assembly.stream for distgit ose-etcd.
All builds following this will include this PR.

@Elbehery
Copy link
Author

/jira refresh

@openshift-ci-robot
Copy link

@Elbehery: Jira Issue OCPBUGS-27105 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

/jira 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 openshift-eng/jira-lifecycle-plugin repository.

@Elbehery Elbehery deleted the rebase-etcd-3.5.11-openshift-4.11 branch February 1, 2024 15:15
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. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. 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