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

ETCD-202: bump etcd v3.5.0 #91

Merged
merged 1,726 commits into from
Aug 2, 2021

Conversation

hexfusion
Copy link

ptabor and others added 30 commits April 17, 2021 12:58
etcdserver: remove temp files in snap dir when etcdserver starting
client: fix check datascale command for https endpoints
Since the Dockerfile files are now per arch, this adjusts to detect ARCH
and builds docker release from the Dockerfile.<ARCH> file.
This fixes so that the ENV vars are taken in the same way as for etcd
binary.
Makefile, build.sh: Fix build process
…ealth_check

etcdhttp/metrics.go: exclude alarms from health check conditionally with `?exclude=NOSPACE`
Makefile: Use `gcloud auth configure-docker` instead of `gcloud docker ...` for test-images
(no)StoreV2 (Part 3): Applying consistency fix: ClusterVersionSet (and co) might get not applied on v2store
…r-testing

mvcc/backend tests: Refactor: Do not mix testing&prod code.
…d as codes.Canceled, codes.DeadlineExceeded instead of 'codes.Unknown'
…text

Errors: `context cancelled` or `context deadline exceeded` are exposed as codes.Canceled, codes.DeadlineExceeded instead of 'codes.Unknown'
Infrequently the test flaked. Reproducable with:

```
  go test go.etcd.io/etcd/tests/v3/integration --run TestFirstCommitNotification --count=500
```

The moveLeader finishes when configchange is commited by quorum.
It doesn't guarantee that the 'empty' record was committed by the new leader.
From time to time happened that appliedLeaderIndex was returning 9
(without empty entry) and the test flaked. In healthy case the
appliedIndex returned 10.

Fixed by putting kv pair after leader change. The pair is guaranteed
to be stored on index when put finishes (so the empty entry as well).
…stCommitNotification

Deflake: TestFirstCommitNotification
etcdserver/mvcc: update tw.trace.Step condition
correct 'backend' (bbolt) context in aspect of membership.

Prior to this change the 'restored' backend used to still contain:
  - old memberid (mvcc deletion used, why the membership is in bolt
bucket, but not mvcc part):
    ```
	mvs := mvcc.NewStore(s.lg, be, lessor, ci, mvcc.StoreConfig{CompactionBatchLimit: math.MaxInt32})
	defer mvs.Close()
	txn := mvs.Write(traceutil.TODO())
	btx := be.BatchTx()
	del := func(k, v []byte) error {
		txn.DeleteRange(k, nil)
		return nil
	}

	// delete stored members from old cluster since using new members
	btx.UnsafeForEach([]byte("members"), del)
    ```
  - didn't get new members added.
@openshift-ci
Copy link

openshift-ci bot commented Jul 28, 2021

@hexfusion: 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.

In response to this:

bump etcd v3.5.0

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 28, 2021
…r when its cert has non empty CN

CARRY:

This patch is required to allow metrics cert to auth with CN in cert.

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

lilic commented Jul 29, 2021

/retest

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
@hexfusion
Copy link
Author

/retest

@openshift-ci
Copy link

openshift-ci bot commented Jul 30, 2021

@hexfusion: 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.

In response to this:

ETCD-202: bump etcd v3.5.0

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.

@hexfusion hexfusion changed the title bump etcd v3.5.0 ETCD-202: bump etcd v3.5.0 Jul 30, 2021
@hexfusion
Copy link
Author

Quorum guard failures fixed by

openshift/cluster-etcd-operator#636

@hexfusion
Copy link
Author

/retest

2 similar comments
@hexfusion
Copy link
Author

/retest

@hexfusion
Copy link
Author

/retest

…on tests with unit

etcd 3.5 will not allow integration tests to run outside of test/integration. This change breaks out the logic into a more testable path allowing coverage and not requiring breaking out discover-etcd-initial-cluster into a seperate module yet.

Signed-off-by: Sam Batschelet <sbatsche@redhat.com>
@hexfusion
Copy link
Author

unit tests should pass with openshift/release#20773. they pass locally so the issue is with CI config.

@lilic
Copy link

lilic commented Aug 2, 2021

/retest

PR was merged.

Copy link

@lilic lilic left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 2, 2021
@openshift-ci
Copy link

openshift-ci bot commented Aug 2, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hexfusion, lilic

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 merged commit a2075eb into openshift:openshift-4.9 Aug 2, 2021
@hexfusion hexfusion deleted the etcd-rebase-v3.5.0 branch August 2, 2021 12:27
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. 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