hack/pin-dependency.sh golang.org/x/crypto release-branch.go1.15
hack/pin-dependency.sh golang.org/x/mod release-branch.go1.15
hack/pin-dependency.sh golang.org/x/net release-branch.go1.15
hack/pin-dependency.sh golang.org/x/text v0.3.3
hack/pin-dependency.sh golang.org/x/tools release-branch.go1.15
hack/pin-dependency.sh golang.org/x/xerrors release-branch.go1.15
Did not pin golang.org/x/sys to release-branch.go1.15 because we require a newer level
ref: https://tip.golang.org/doc/go1.15#net/http
Parsing is now stricter as a hardening measure against request smuggling
attacks: non-ASCII white space is no longer trimmed like SP and HTAB,
and support for the "identity" Transfer-Encoding was dropped.
Signed-off-by: Stephen Augustus <saugustus@vmware.com>
This mirrors an earlier fix to the EndpointSlice controller. I'll make a
follow up PR to move this component to a shared package, but that seems
beyond the scope of a bug fix PR.
There's currently no way to know whether an error is for SCTP or
UDP, for example:
Jul 24 09:55:54.469: INFO: netserver-0[e2e-nettest-3476].container[webserver].log
2020/07/24 09:53:52 Started UDP server
2020/07/24 09:53:52 Error occurred. error:protocol not supported
In this case the "Error occurred. error:protocol not supported" is
actually for the SCTP socket. Make that more apparent.
This adjusts tests that were waiting for Pods to be ready to instead
just wait for them to have IPs assigned to them. This relies on the
associated publishNotReadyAddresses field on Services. Additionally this
increases the the length of time we'll wait for EndpointSlices to be garbage
collected from 12s to 30s. Finally, this adds additional logging to
ExpectNoError calls so it's easier to understand where and why a test
failed.
When nodes are added in multiple zones at once, the nodeTree next
function does not return a correct list of nodes but repeats some
This commit resets the index before starting to call next() to
prevent this issue
Special thanks to igraecao for the help in finding the bug
Co-authored-by: igraecao <matvej.yolli@outlook.com>
sig-storage tests that delete pods need to wait for owned resources to
also be cleaned up before returning in the case that resources such as
ephemeral inline volumes are being used. This was previously implemented
by modifying the pod delete call of the e2e framework, which negatively
impacted other tests. This was reverted and now the logic has been moved
to StopPodAndDependents, which is local to the sig-storage tests.
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
