Make sure your ssh identity key is listed in the Management node info. in your vcl web interface Management nodes Edit Management Node Information
Edit Double check the path for "End Node SSH Identity Key Files:" and make sure it's populated and has the correct path to the private ssh identity key. Then restart vcld as that data is cached on the management node. -Aaron On Thu, Aug 9, 2012 at 10:42 AM, William Robinson <[email protected]> wrote: > ssh. i noticed that as well, but as far as i can ascertain, ssh is working. > > will > > > On 08/09/2012 10:40 AM, Michael Jinks wrote: >> >> I notice this: >> >> <snip> >>> >>> 2012-08-08 >>> 15:36:55|7443|10:10|image|VMware.pm:get_vmhost_api_object(1522)|creat >>> ed API object: VCL::Module::Provisioning::VMware::vSphere_SDK >>> 2012-08-08 >>> 15:36:55|7443|10:10|image|vSphere_SDK.pm:is_restricted(1502)|access t >>> o the VM host via the vSphere SDK is restricted due to the license: >>> RestrictedVe >>> rsionFault >>> 2012-08-08 15:37:19|7443|10:10|image|OS.pm:is_ssh_responding(644)|vclhv01 >>> is NOT >>> responding to SSH, SSH command failed, port 22: open, port 24: closed >>> 2012-08-08 15:37:19|7443|10:10|image|VMware.pm:initialize(307)|unable to >>> control >>> OS of VM host vclhv01 using VCL::Module::OS::Linux::UnixLab OS object >>> because V >>> M host is not responding to SSH >> >> >> Do you mean to use the SDK to access your VMware machine, or do you >> expect to use SSH? >> >> > -- Aaron Peeler Program Manager Virtual Computing Lab NC State University All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties.
