Automated cherry pick of #12165

[cfc4n]

Cherry pick of #12165 on release-3.4.

#12165: etcdserver: check authinfo if it is not

[cfc4n]

semaphoreci info is

--- FAIL: TestV2CurlClientBoth (0.93s)
    v2_curl_test.go:56: failed put with curl (read /dev/ptmx: input/output error (expected "{\"action\":\"set\",\"node\":{\"key\":\"/foo\",\"value\":\"bar\",\"", got ["curl: (7) Failed to connect to localhost port 20000: Connection refused\r\n"]))
    v2_curl_test.go:47: error closing etcd processes (exit status 1)

I tested sudo HOST_TMP_DIR=/tmp TEST_OPTS="GOARCH=386 PASSES='build e2e'" make docker-test on my MacBook ,and It works without fail message.
https://gist.github.com/cfc4n/eae914c2316d132f3df42627b6e8303a

@mitake Can you reset CI to recheck it? Thanks.

[mitake]

@cfc4n Got it, I restarted travis. In semaphore only 386 is failing, I think it's a nondeterministic issue.

[cfc4n]

ping
/cc @mitake @jingyih

[mitake]

@cfc4n Sorry for my late reply. I think this PR can be merged because failed test cases are limited:

• linux-amd64-functional tends to be fleaky and it actually passes on my local env with this PR
• linux-amd64-grpcproxy is allowed to fail
• e2e test cases are only failing for 386 so the issue would be non deterministic

[mitake]

LGTM, thanks! Defer to @jingyih

[cfc4n]

@cfc4n Sorry for my late reply. I think this PR can be merged because failed test cases are limited:

• linux-amd64-functional tends to be fleaky and it actually passes on my local env with this PR
• linux-amd64-grpcproxy is allowed to fail
• e2e test cases are only failing for 386 so the issue would be non deterministic

thank you for review. and Is it same problem with #12365 ?

[mitake]

@cfc4n #12365 is failing because of TARGET=linux-amd64-integration-4-cpu, but TARGET=linux-amd64-integration-1-cpu was passed successfully. I think the issue is non deterministic. Anyway I'll look at the PR.

[mitake]

@cfc4n Do you have a reason to close this PR (and #12365)? I think it can be merged to the stable releases. If it's ok for you, could you reopen?

[bbiao]

@cfc4n Hi，will release-3.14 branch cherry-pick these commits again and fix problem mentioned in #12165 ?