Re: Image capture hitch

2012-06-14 Thread Josh Thompson 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Michael,

You're hitting a bug in 2.2.1.  If you go to Manage Computers-Computer 
Utilities, you can set the VM to the available state successfully.

Josh

On Thursday, June 14, 2012 1:27:21 PM Michael Jinks wrote:
 Hi List.
 
 I'm still trying to capture my first image and I'm confused.
 
 I'm following these instructions:
 
  https://cwiki.apache.org/VCL/create-a-linux-base-image.html
 
 I have a VM running on my ESX server, named vcl-linux-template-1.
 
 It's entered in the database as a machine.  When I perform that step,
 the UI will only allow me to submit the image if it's set to state
 maintenance, which matches what the docs tell me to do, so that seems
 fine.
 
 But, when I run vcld -setup, I get an error:
 
  [...]
  Enter the hostname or IP address of the computer to be captured: ('c'
  to cancel): vcl-linux-template-1
 
  Computer to be captured: vcl-linux-template-1 (ID: 5)
  Provisioning module: provisioning_vmware
  Install type: vmware
 
  ERROR: state of vcl-linux-template-1 is maintenance
 
 Hm, okay.  So I went back to the VCL UI, and tried to set the VM state
 to something else, only other option in the dropdown is available, but
 if I try to submit that I get the same error message as before: Virtual
 machines can only be added in the maintenance state.
 
 What am I missing?
 
 --
 Michael Jinks :: mji...@uchicago.edu :: 773-469-9688
 University of Chicago IT Services
- -- 
- ---
Josh Thompson
VCL Developer
North Carolina State University

my GPG/PGP key can be found at pgp.mit.edu

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.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.17 (GNU/Linux)

iEYEARECAAYFAk/aL3QACgkQV/LQcNdtPQP4XACfeqS7FrtqFfj9+owduoyJUFDc
rtAAn2WI7HSkOIyQQs9yWXOodh7Uj3jI
=+y18
-END PGP SIGNATURE-

next issue, Re: Image capture hitch

2012-06-14 Thread Michael Jinks 
On Thu, Jun 14, 2012 at 02:37:40PM -0400, Josh Thompson wrote:
 
 You're hitting a bug in 2.2.1.  If you go to Manage Computers-Computer 
 Utilities, you can set the VM to the available state successfully.

Thanks.  I had looked around a little for another way to do it but
missed that.

Now I'm a little further and hitting a new problem.  I can start the
capture process, but the capture process fails.  I don't have a
successful instance to compare against, so I'm not sure exactly where
the salient problem is, but I notice this in the log:

 [...]
 2012-06-14
 14:15:57|25286|3:3|image|Module.pm:create_mn_os_object(335)|management
 node OS object has already been created, address: 3fc9dc8, returning 1
 2012-06-14
 
14:15:57|25286|3:3|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::VIM_SSH
 object created for computer vcl-linux-template-1, address: 432a330
 2012-06-14 14:15:57|25286|3:3|image|VIM_SSH.pm:initialize(126)|VIM
 executable is not available on the VM host, output:
 |25286|3:3|image| bash: vim-cmd: command not found
 |25286|3:3|image| bash: vmware-vim-cmd: command not found
 [...]

That's strange, because when I ssh from my management node to the ESX
machine, I see:

 ~ # which vim-cmd
 /bin/vim-cmd

I also notice that during vcld -setup, it never asks which hypervisor
is running the VM we want to capture, so how does it know where to ssh
to run vim-cmd?  ...And that makes me wonder, is it connecting to the
wrong host to do the capture?

It isn't connecting to the VM itself, at least not according to logs on
that machine.

So I'm confused.

Fixed, Re: next issue, Re: Image capture hitch

2012-06-14 Thread Michael Jinks 
On Thu, Jun 14, 2012 at 03:01:03PM -0500, Michael Jinks wrote:
 
  [...]
  2012-06-14
  14:15:57|25286|3:3|image|Module.pm:create_mn_os_object(335)|management
  node OS object has already been created, address: 3fc9dc8, returning 1
  2012-06-14
  
 14:15:57|25286|3:3|image|Module.pm:new(200)|VCL::Module::Provisioning::VMware::VIM_SSH
  object created for computer vcl-linux-template-1, address: 432a330
  2012-06-14 14:15:57|25286|3:3|image|VIM_SSH.pm:initialize(126)|VIM
  executable is not available on the VM host, output:
  |25286|3:3|image| bash: vim-cmd: command not found
  |25286|3:3|image| bash: vmware-vim-cmd: command not found
  [...]

There were two problems here.  One was that I hadn't finised the steps
in the further steps if using VMware doc, under Assign a VM to a
Virtual Host.

The other was that my ESX machine doesn't store VM's under the default
path listed in the VMware ESX - local storage VM profile.  Fixed that,
now going to try it again.

Bit by bit...

-- 
Michael Jinks :: mji...@uchicago.edu :: 773-469-9688
University of Chicago IT Services