Unable to lanch the litmus choas mesh in the k8 cluster due to fellowing issue

[varaprasadnew]

What happened:

What you expected to happen:

Where can this issue be corrected? (optional)

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

[varaprasadnew]

What happened:

Deployed limtus in the dev envroinment ,, all pods. where up but failed to
subscriber was failed to start
What you expected to happen:

to start the application and run the application

Where can this issue be corrected? (optional)

How to reproduce it (as minimally and precisely as possible):

NAME READY STATUS RESTARTS AGE
pod/chaos-exporter-75bc4cdd8b-njwcp 1/1 Running 0 7h15m
pod/chaos-litmus-auth-server-fd98d7779-cfpdg 1/1 Running 0 6h18m
pod/chaos-litmus-frontend-5fb8c4bf48-nn4tr 1/1 Running 0 7h16m
pod/chaos-litmus-server-5987cb849d-8tspj 1/1 Running 2 (43h ago) 2d6h
pod/chaos-mongodb-0 1/1 Running 0 6h18m
pod/chaos-mongodb-1 0/1 Pending 0 8d
pod/chaos-mongodb-arbiter-0 1/1 Running 0 2d6h
pod/chaos-operator-ce-55bb5f8cf4-7gksq 1/1 Running 0 7h17m
pod/event-tracker-6c689cdf86-qs8cc 1/1 Running 0 5h5m
pod/subscriber-867d8778b8-l4ggr 0/1 CrashLoopBackOff 11 (54s ago) 32m
pod/workflow-controller-f646fdd7b-x2flg 1/1 Running 0 7h15m

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/chaos-exporter ClusterIP 10.43.253.113 8080/TCP 2d1h
service/chaos-litmus-auth-server-service ClusterIP 10.43.192.108 9003/TCP,3030/TCP 8d
service/chaos-litmus-frontend-service ClusterIP 10.43.216.230 9091/TCP 8d
service/chaos-litmus-server-service ClusterIP 10.43.22.240 9002/TCP,8000/TCP 8d
service/chaos-mongodb-arbiter-headless ClusterIP None 27017/TCP 8d
service/chaos-mongodb-headless ClusterIP None 27017/TCP 8d
service/workflow-controller-metrics ClusterIP 10.43.104.59 9090/TCP 2d1h

NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/chaos-exporter 1/1 1 1 2d1h
deployment.apps/chaos-litmus-auth-server 1/1 1 1 8d
deployment.apps/chaos-litmus-frontend 1/1 1 1 8d
deployment.apps/chaos-litmus-server 1/1 1 1 8d
deployment.apps/chaos-operator-ce 1/1 1 1 2d1h
deployment.apps/event-tracker 1/1 1 1 2d1h
deployment.apps/subscriber 0/1 1 0 2d1h
deployment.apps/workflow-controller 1/1 1 1 2d1h

NAME DESIRED CURRENT READY AGE
replicaset.apps/chaos-exporter-75bc4cdd8b 1 1 1 2d1h
replicaset.apps/chaos-litmus-auth-server-fd98d7779 1 1 1 8d
replicaset.apps/chaos-litmus-frontend-5fb8c4bf48 1 1 1 8d
replicaset.apps/chaos-litmus-server-5987cb849d 1 1 1 2d22h
replicaset.apps/chaos-litmus-server-7bd7b74577 0 0 0 8d
replicaset.apps/chaos-operator-ce-55bb5f8cf4 1 1 1 2d1h
replicaset.apps/event-tracker-6c689cdf86 1 1 1 2d1h
replicaset.apps/subscriber-687df95b65 0 0 0 35h
replicaset.apps/subscriber-848b59895c 0 0 0 2d1h
replicaset.apps/subscriber-867d8778b8 1 1 0 32m
replicaset.apps/workflow-controller-f646fdd7b 1 1 1 2d1h

NAME READY AGE
statefulset.apps/chaos-mongodb 1/3 8d
statefulset.apps/chaos-mongodb-arbiter 1/1 8d
GCNagendra.Varaprasa@QXD19WGQ9Y harness #kubectl logs -f subscriber-867d8778b8-l4ggr -n litmus
time="2023-10-20T10:17:52Z" level=info msg="Go Version: go1.20.8"
time="2023-10-20T10:17:52Z" level=info msg="Go OS/Arch: linux/amd64"
time="2023-10-20T10:17:52Z" level=info msg="All infra deployments are up"
time="2023-10-20T10:17:52Z" level=info msg="Starting the subscriber"
time="2023-10-20T10:17:52Z" level=fatal msg="Failed to parse agent confirm data" data="\r\n<title>404 Not Found</title>\r\n\r\n

404 Not Found

\r\n

---

nginx\r\n\r\n\r\n" error="invalid character '<' looking for beginning of value"

Anything else we need to know?:

[Rafouf69]

The same error happened to me with litmus 3.1