Github Action failed due to the unit test of TestCluster about easegress HOT 2 CLOSED

@zhao-kun Thanks for the suggestion.

• I am working on open an issue for the Easegress cluster behavior-changing proposal which can help to solve the cluster testing failure in the Github testing env. (Changing to ETCD cluster solution directly or continuing improving current cluster implementation. Should comparing with other distributing productions' solutions.)
• Speaking about the cluster test case failure

register cluster name test-cluster failed: create client failed: couldn't open sink "/tmp/eg-test/test-member-001/log/etcd_client.log": open /tmp/eg-test/test-member-001/log/etcd_client.log: no such file or directory

It's weird to me that it can't be reproduced successfully every time in my development env. And sometimes the Github test can successfully go through too! If the tmp directory is the root cause, it should be failed every time. Or maybe Github testing doesn't run in the same docker-backend every time?

Summary

1. I will change the directory to os.TempDir in this test case.
2. The issue for Easegress cluster behavior is still necessary.

from easegress.

We can easily reproduce the issue with make build-docker, but we need slightly modify build/package/Dockerfile with

diff --git a/build/package/Dockerfile b/build/package/Dockerfile
index eccdafa..39ff169 100644
--- a/build/package/Dockerfile
+++ b/build/package/Dockerfile
@@ -1,10 +1,10 @@
-FROM golang:alpine AS builder
-RUN apk --no-cache add make git
+FROM golang AS builder
+#RUN apk --no-cache add make git

WORKDIR /opt/easegress
COPY . .

-RUN make clean && make build
+RUN make clean && make test && make build

Actually, it's almost failed every time, you can re-run all jobs in Actions[1]

it should be failed every time.

[1]https://github.com/megaease/easegress/actions

from easegress.