search

vmware-archive / vsphere-flocker-driver

vSphere Flocker driver
Other
24 stars 16 forks source link

Scanning other servers #23

Closed catdrich closed 8 years ago

catdrich commented 8 years ago

I have set this up yet again, and it's kind of working (I haven't done extensive testing yet). However, I was notified by our hardware area that errors were appearing that involve servers I have NOT set up with the flocker driver, and they aren't on the same datastore that we are using (and defined in the agent.yml)

From vsphere.log: 2016-03-11 08:39:49,207 - vsphere_blockdevice - DEBUG - compute_instance_id: Getting local VMs: gridcon.nwoca.org (vm-2698), nw-ssdtweb-01 (vm-2854), ssdt-web-04 (vm-2855)

All show the IP of 127.0.0.1 when I look in vCenter.

Example error in Vcenter: gridcon.nwoca.org Invalid configuration for device '0'. NWOCALAND\SSDT_Flocker_Service vCenter5

How can we prevent this from happening? I had to stop the services because of these errors, so I'm unable to do more testing.

catdrich commented 8 years ago

I figured this out. In the agent.yml, etc. and when creating the cluster certificate, I couldn't specify the hostname because ONE of the IP's is 127.0.0.1. I had to specify the IP address.