What happened:
In EKSA cluster, if I install storage service rook/ceph and create wordpress in it.
Then upgrade the version of kuernetes of the EKSA cluster will stuck.
What you expected to happen:
I expect to see upgrade works even with rook/ceph/wordpress
How to reproduce it (as minimally and precisely as possible):
upgrade EKSA cluster with kubernetes 1.27.11 (stuck)
Anything else we need to know?:
There is smoking boots log like this:
{"level":"info","ts":1711485549.163217,"caller":"syslog/receiver.go:113","msg":"host=10.20.22.226 facility=daemon severity=ERR app-name=9c576943b82e procid=3895 msg=\"Error: worker Finished with error: failed to get workflow context: rpc error: code = Unavailable desc = connection error: desc = \\\"transport: Error while dialing dial tcp 10.20.22.223:42113: connect: connection refused\\\"\\n\"","service":"github.com/tinkerbell/boots","pkg":"syslog"}
What happened: In EKSA cluster, if I install storage service rook/ceph and create wordpress in it. Then upgrade the version of kuernetes of the EKSA cluster will stuck.
What you expected to happen: I expect to see upgrade works even with rook/ceph/wordpress
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: There is smoking boots log like this:
{"level":"info","ts":1711485549.163217,"caller":"syslog/receiver.go:113","msg":"host=10.20.22.226 facility=daemon severity=ERR app-name=9c576943b82e procid=3895 msg=\"Error: worker Finished with error: failed to get workflow context: rpc error: code = Unavailable desc = connection error: desc = \\\"transport: Error while dialing dial tcp 10.20.22.223:42113: connect: connection refused\\\"\\n\"","service":"github.com/tinkerbell/boots","pkg":"syslog"}
Environment: