…nfig file

…of-#13145-etcd-io#13237-origin-release-3.5

[backport 3.5]: Automated cherry pick of etcd-io#13145 etcd-io#13237

Stop using tip golang version in CI

…ckend out of sync

Fix for v3.5 Ensure that cluster members stored in v2store and backend are in sync

prefixArgs uses os.Setenv in e2e tests instead envMap.
This creates overwrites in some test cases and have an impact
on test quality and isolation between tests.
This PR uses ctlcontext envMap in each tests with high priority
and merges os environment variables with low priority.

Cherry pick "Fix http2 authority header in single endpoint scenario" to release-3.5

fixes: CVE-2021-3711, CVE-2021-35942, CVE-2019-9893

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>

[release-3.5] Dockerfile: bump debian bullseye-20210927

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>

…t from 3.6)

storage/backend: Add a gauge to indicate if defrag is active (backport)

… by multiple peers

cherry-pick to 3.5 from etcd-io#13467 exclude the same alarm type activated by multiple peers

…ying

To fix a bug in the retry logic caused when the auth token is cleared after receiving `ErrInvalidAuthToken` from the server and the subsequent call to `getToken` also fails due to some reason (eg. context deadline exceeded).
This leaves the client without a token and the retry will continue to fail with `ErrUserEmpty` unless the token is refreshed.

Backport PR 13308 to release-3.5

Current checkpointing mechanism is buggy. New checkpoints for any lease
are scheduled only until the first leader change. Added fix for that
and a test that will check it.

To extend lease checkpointing mechanism to cases when the whole etcd
cluster is restarted.

…lease-checkpoint-persist to persist lease remainingTTL

To avoid inconsistant behavior during cluster upgrade we are feature
gating persistance behind cluster version. This should ensure that
all cluster members are upgraded to v3.6 before changing behavior.

To allow backporting this fix to v3.5 we are also introducing flag
--experimental-enable-lease-checkpoint-persist that will allow for
smooth upgrade in v3.5 clusters with this feature enabled.

Backport Lease Checkpoints fix to release-3.5

[3.5] Set the backend again after recovering v3 backend from snapshot

…ock-fix

Backport watchablestore runlock bug fix to release-3.5

…9-11254.

Update dep: gopkg.in/yaml.v2 v2.2.8 -> v2.4.0 due to: CVE-2019-11254 [release 3.5]

Problem: Defrag was implemented before custom bolt options were added.
Currently defrag doesn't restore backend options.
For example BackendFreelistType will be unset after defrag.

Solution: save bolt db options and use them in defrag.

[3.5] Trim the suffix dot from the srv.Target for etcd-client DNS lookup

…heck

[3.5] enhance health check endpoint to support serializable request

porting back from 3.5 from main
PR etcd-io#13334

*: fix IsOptsWithFromKey

…cimal

[3.5] Always print raft term in decimal when displaying member list in json

server/storage/backend: restore original bolt db options after defrag

backport 3.5: etcd-io#13676 load all leases from backend

Fix offline defrag in etcdctl

This should make it easier to bump the golang version

[release-3.5] Update go to 1.16.15

Signed-off-by: Manuel Rüger <manuel@rueg.eu>

[Release-3.5] Makefile: Fix wrong target

This fixes problem where logs json changes format of timestamp.

[release-3.5] Fix inconsistent log format

…e of apply

[release-v3.5] server: Add verification of whether lock was called within out outsid…

[release-3.5] go.mod: Upgrade to prometheus/client_golang v1.11.1

…rease

Reason to store CI and term in backend was to make db fully independent
snapshot, it was never meant to interfere with apply logic. Skip of CI
was introduced for v2->v3 migration where we wanted to prevent it from
decreasing when replaying wal in
etcd-io#5391. By mistake it was added to
apply flow during refactor in
etcd-io#12855 (comment).

Consistency index and term should only be negotiated and used by raft to make
decisions. Their values should only driven by raft state machine and
backend should only be responsible for storing them.

[release-3.5] server: Save consistency index and term to backend even when they decrease