atiratree
commented
5 years ago I am sorry I cannot reproduce that. It works fine on clean Openshift 3.9 for me. Maybe you could try a newer release of Openshift?
Open nabbdl opened 5 years ago
atiratree
commented
5 years ago I am sorry I cannot reproduce that. It works fine on clean Openshift 3.9 for me. Maybe you could try a newer release of Openshift?
I have deployed the solution on Openshift 3.9. The AlertMangerStateFulset doesn't come up with the following error : component=cluster msg="failed to join cluster" err="3 errors occurred:\n\nFailed to resolve alertmanager-main-0.alertmanager-operated.openshift-monitoring.svc:6783: lookup alertmanager-main-0.alertmanager-operated.openshift-monitoring.svc on 172.30.102.142:53: no such host\n* Failed to resolve alertmanager-main-1.alertmanager-operated.openshift-monitoring.svc:6783 ...
The pod is trying to resolve alertmanager-main-0.alertmanager-operated.openshift-monitoring.svc:6783 instead of "alertmanager-main-0.alertmanager-operated.openshift-monitoring.svc" due to the configuration of the statefulset where "cluster.peer" is defined with "cluster.peer=alertmanager-main-2.alertmanager-operated.openshift-monitoring.svc:6783" instead of "cluster.peer=alertmanager-main-2.alertmanager-operated.openshift-monitoring.svc"