Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
baremetal
Hey!
I followed the documentation https://rancher.com/docs/rancher/v2.x/en/installation/ha/ and after the restart, cattle-cluster-agent restarts itself all the time.
Redeployment of that workload fixes the issue temporarily, after the restart must be redeployed again.
Log:
INFO: Environment: CATTLE_ADDRESS=10.42.0.8 CATTLE_CA_CHECKSUM=88809bea5138e9e83757cb3cc5d8f73225cc3d81b599c81c7346276590c0e271 CATTLE_CLUSTER=true CATTLE_INTERNAL_ADDRESS= CATTLE_K8S_MANAGED=true CATTLE_NODE_NAME=cattle-cluster-agent-5b788677c6-mfmwb CATTLE_SERVER=https://rancher.docker.zz
INFO: Using resolv.conf: nameserver 10.43.0.10 search cattle-system.svc.cluster.local svc.cluster.local cluster.local options ndots:5
ERROR: https://rancher.docker.zz/ping is not accessible (Could not resolve host: rancher.docker.zz)
RancherOS Version: (ros os version) v1.5.3
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.) baremetal
Hey!
I followed the documentation
https://rancher.com/docs/rancher/v2.x/en/installation/ha/
and after the restart,cattle-cluster-agent
restarts itself all the time.Redeployment of that workload fixes the issue temporarily, after the restart must be redeployed again.
Log:
Regards, TheAifam5