-
Notifications
You must be signed in to change notification settings - Fork 40k
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
Bump to etcd 3.1.12 to pick up critical fix #60998
Conversation
cluster/images/etcd/Makefile
Outdated
REGISTRY?=k8s.gcr.io | ||
# Images should be pushed to staging-k8s.gcr.io, which is aliased to gcr.io/google-containers. | ||
# But currently that does not work, so we must instead push to gcr.io/google-containers directly. | ||
PUSH_REGISTRY?=gcr.io/google-containers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you tell what the error is? Maybe it's related to the one I was seeing yesterday - #60891 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I either get this (for layer pushes):
The push refers to a repository [staging-k8s.gcr.io/etcd]
21172253818c: Retrying in 5 seconds
6689586d0bd6: Retrying in 4 seconds
Or, this (if layers already exist, but something needs to be tagged):
denied: Permission 'storage.objects.create' denied for bucket 'artifacts.google-containers.appspot.com'
Happens using both docker <cmd>
and gcloud docker -- <cmd>
works works if i instead do the same against gcr.io/google-containers
. Permissions issue?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you try gcloud auth login
and authenticate yourself as k8s.production.user@?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also, make sure you have gcloud
185.0.0 or newer and run gcloud beta auth configure-docker
- this should allow docker push
to work.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That fixed the problem. Thanks @ixdy! I'll update this PR.
CHANGELOG-1.9.md
Outdated
@@ -304,7 +304,7 @@ filename | sha256 hash | |||
* Fixes a possible deadlock preventing quota from being recalculated ([#58107](https://github.com/kubernetes/kubernetes/pull/58107), [@ironcladlou](https://github.com/ironcladlou)) | |||
* Fixes a bug in Heapster deployment for google sink. ([#57902](https://github.com/kubernetes/kubernetes/pull/57902), [@kawych](https://github.com/kawych)) | |||
* GCE: Allows existing internal load balancers to continue using an outdated subnetwork ([#57861](https://github.com/kubernetes/kubernetes/pull/57861), [@nicksardo](https://github.com/nicksardo)) | |||
* Update etcd version to 3.1.11 ([#57811](https://github.com/kubernetes/kubernetes/pull/57811), [@xiangpengzhao](https://github.com/xiangpengzhao)) | |||
* Update etcd version to 3.1.12 ([#57811](https://github.com/kubernetes/kubernetes/pull/57811), [@xiangpengzhao](https://github.com/xiangpengzhao)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This appears to be a mistake
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch. Reverting.
7a8afcd
to
4b794b5
Compare
/approve |
/retest |
/test pull-kubernetes-e2e-gke |
pull-kubernetes-e2e-gke failures are failing across the board: https://k8s-gubernator.appspot.com/builds/kubernetes-jenkins/pr-logs/directory/pull-kubernetes-e2e-gke |
/retest |
1 similar comment
/retest |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/assign @mikedanese @sttts |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
[MILESTONENOTIFIER] Milestone Pull Request: Up-to-date for process @jpbetz @mikedanese @sttts @timothysc Pull Request Labels
|
/approve |
/approve no-issue |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker, ixdy, jpbetz, sttts, timothysc, wojtek-t 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 |
/test all [submit-queue is verifying that this PR is safe to merge] |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions here. |
etcd 3.1.12 (as well as 3.2.17 and 3.3.2) was released yesterday to fix a bug critical to kubernetes:
Fix mvcc "unsynced" watcher restore operation.
This will be backported to 1.9 as well.
Release note:
cc @gyuho @wojtek-t @shyamjvs @timothysc @jdumars