Closed rd37 closed 9 years ago
The bug/issue resulted when bellecs was migrated to a VM. The hostname on the VM was set to 'bellecs' rather than 'bellecs.heprc.uvic.ca', the CS was then writing 'bellecs' into the condor_config.local file for the condor_host variable. This caused the condor client to be unable to find the condor host.
But if CS doesn't know its hostname, what else can it do?
If the host machine's hostname is mis-configured, then cloud-scheduler propagates the wrong hostname to the condor clients.