We tried building a cf bosh release after adding extra rules specific to our application in the following 2 files haproxy.ctmpl.erb (found this in cf-231 only, dint see it in cf-205) haproxy.conf.erb
Also added parameters in spec file that these 2 files are using to fetch the values dynamically from the deployment manifest
After adding these 2 changes, we built a bosh release on top of cf-231 and deployed successfully and all VMs are running. But I could not login to the haproxy VM, but other VMs I can login
We have done the same for cf-205 and works well and could login. Kindly let me know what could be the issue.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is b0:8a:62:f4:91:75:34:71:c1:23:fb:4b:80:1e:33:0d. Please contact your system administrator. Add correct host key in /root/.ssh/known_hosts to get rid of this message. Offending ECDSA key in /root/.ssh/known_hosts:31 remove with: ssh-keygen -f "/root/.ssh/known_hosts" -R 10.20.0.20 ECDSA host key for 10.20.0.20 has changed and you have requested strict checking. Host key verification failed.