Neat. Thanks Aaron. Now, I know the proper way is to change it manually.
I was worried that because the front-end does not allow me to change it, it 
means something else is not right.

Thanks.

________________________________________
From: Aaron Peeler [aaron_pee...@ncsu.edu]
Sent: Monday, June 07, 2010 8:56 AM
To: vcl-dev@incubator.apache.org
Subject: Re: ESXi host, local disk

For the VCL2.1 version, this will have to be done manually. The web
front-end assumes that xcat provisioning will install the blade with the
hypervisor and place the server into vmhostinuse state.

manually change the stateid to 20 for the computer
update computer set stateid=20 where computerid=1;

I think we are planning or have scheduled a fix in the next release for
putting standalone vmware/hypervisor servers into vmostinuse state.

Aaron


On 6/4/10 5:11 PM, My LinuxHAList wrote:
> Thanks Andy for the input.
>
> Thanks for the idea. Also, I've got an issue where my ESXi host can't
> be switched to the state of "vmhostinuse".
> I was advised that ESXi host needs to be in "vmhostinuse" state.
> However, I can't switch it to the vmhostinuse state from the web
> interface. It would go through fine; but the when I re-checked then it
> switches back to "available" state again.
>
> They were labeled "Warning" in the logs -- if it's considered a
> "must", the label "Critical" could be more effective in conveying the
> message.
>
> Could someone lend a hand in troubleshooting why my ESXi host
> (computer.id=1) can't be switched to vmhostinuse state ?
>
> Below are my tables:
> mysql>  select * from computer;
> +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+------+------------+-----------+---------+-----------------------+----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+
> | id | stateid | ownerid | platformid | scheduleid | currentimageid |
> preferredimageid | nextimageid | imagerevisionid | RAM  | procnumber |
> procspeed | network | hostname              | IPaddress      |
> privateIPaddress | eth0macaddress | eth1macaddress | type           |
> provisioningid | drivetype | deleted | notes | lastcheck | location |
> dsa  | dsapub | rsa  | rsapub | host | hostpub | vmhostid | vmtypeid |
> +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+------+------------+-----------+---------+-----------------------+----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+
> |  1 |       2 |       1 |          1 |          1 |              4 |
>                0 |           0 |               0 | 4096 |          2 |
>      3200 |     100 | vmnode2.local         | 192.168.88.5   | NULL
>          | NULL           | NULL           | blade          |
>     4 | hda       |       0 | NULL  | NULL      | NULL     | NULL |
> NULL   | NULL | NULL   | NULL | NULL    |     NULL |     NULL |
> |  2 |       2 |       1 |          1 |          1 |              4 |
>                0 |           0 |               0 |  512 |          1 |
>      3200 |     100 | vmwarelinux-base10-v1 | 192.168.88.253 | NULL
>          | NULL           | NULL           | virtualmachine |
>     4 | hda       |       0 |       | NULL      | NULL     | NULL |
> NULL   | NULL | NULL   | NULL | NULL    |        1 |     NULL |
> +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+------+------------+-----------+---------+-----------------------+----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+
>
> mysql>  select * from vmhost;
> +----+------------+---------+-------------+-------------+-------------+
> | id | computerid | vmlimit | vmprofileid | vmkernalnic | vmwaredisk  |
> +----+------------+---------+-------------+-------------+-------------+
> |  1 |          1 |       5 |           6 | NULL        | networkdisk |
> +----+------------+---------+-------------+-------------+-------------+
> +----+-------------------------------------------+----------+---------+----------+----------------------------------+------------------------+----------------+--------------------------------+-------------+----------+----------------+
> | id | profilename                               | vmtypeid | imageid
> | nasshare | datastorepath                    | vmpath
> | virtualswitch0 | virtualswitch1                 | vmdisk      |
> username | password       |
> +----+-------------------------------------------+----------+---------+----------+----------------------------------+------------------------+----------------+--------------------------------+-------------+----------+----------------+
> |  1 | VMware GSX standard                       |        3 |       8
> | NULL     | /var/lib/vmware/Virtual Machines | NULL
> | VMnet0         | VMnet2                         | localdisk   | NULL
>      | NULL           |
> |  2 | Vmware ESX standard network mounted share |        5 |       9
> | NULL     | /vmfs/volumes/nfs1               | /vmfs/volumes/storage1
> | VM Network     | Virtual Machine Public Network | networkdisk | NULL
>      | NULL           |
> |  3 | Vmware ESX standard localdisk             |        5 |       9
> | NULL     | /vmfs/volumes/storage1           | NULL
> | VM Network     | Virtual Machine Public Network | localdisk   | NULL
>      | NULL           |
> |  4 | Vmware ESX SAN                            |        5 |       9
> | NULL     | /vmfs/volumes/NetApp             | /vmfs/volumes/storage1
> | Intranet2      | MCNC Public                    | networkdisk | NULL
>      | NULL           |
> |  6 | MyESXiNode                                |        6 |       4
> | NULL     | 192.168.88.4:/export/nfsstore    | /vmfs/volumes/nfsstore
> | VM Network     | Virtual Machine Network        | localdisk   | root
>      | NOTMYPASSWORD |
> +----+-------------------------------------------+----------+---------+----------+----------------------------------+------------------------+----------------+--------------------------------+-------------+----------+----------------+
>
> Thanks
>
> On Fri, Jun 4, 2010 at 2:12 PM, Andy Kurth<andy_ku...@ncsu.edu>  wrote:
>
>> No, the management node must be able to login to the VM via SSH during
>> capture.  If this isn't working, then SSH also won't be working when the
>> image is loaded and reservations will fail.  The management node must be
>> able to SSH into the loaded image to configure several things such as adding
>> the user account, checking for a user connection, etc.
>>
>> It looks like SSH is working from the management node to the VM host. You'll
>> need to get it working to the VM before proceeding.  Your log output shows
>> the VM computer name configured in the VCL database as
>> 'vmwarelinux-base10-v1' matching the image name.  This is a bit odd. You
>> probably will want to come up with a VM naming scheme and change the name of
>> your VM computer first to avoid confusion.  You should be able to do this
>> via Manage Computers ->  Edit Computer Information.  Change the name of the
>> vmwarelinux-base10-v1 computer to something like vm-1.
>>
>> The private IP address of the VM needs to be in /etc/hosts on the management
>> node so that the hostname vm-1 resolves to its private address.  You should
>> be able to run "ping vm-1".
>>
>> Next, get SSH working from the management node to vm-1.  The following
>> command should work:
>> ssh -i /etc/vcl/vcl.key -l root -p 22 -x vm-1
>>
>> Once SSH is working, shut down the VM and save a copy of it for safety.
>>   Power it back on and attempt the VCL image capture process again.
>>
>> Hope this helps,
>> Andy
>>
>>
>> My LinuxHAList wrote:
>>
>>> Ryan, thanks for the input and helpful discussion. I had a similar
>>> discussion with another helpful user on the topic.
>>>
>>> I think the management node was going to ssh into the vm machine to
>>> set ethernet to dhcpd, configure the sshd, shut it down, de-register
>>> it from vmware, etc.
>>>
>>> My original intention is that if I've properly setup the image; set
>>> ethernet to dhcpd, etc., then this would obviate the needs for the
>>> management node to login (and thus safely ignore the warnings).
>>>
>>> By having done what the management node going to do and put it in the
>>> image, will I be able to skip the step of having the management node
>>> to login to the image ?
>>>
>>> The process did copy over:
>>> ./golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmx
>>> ./golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmdk
>>> ./golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1-flat.vmdk
>>>
>>> Thanks
>>>
>>> On Tue, Jun 1, 2010 at 6:04 PM, Ryan Johnson<rjoh...@gwmail.gwu.edu>
>>> wrote:
>>>
>>>> I don't think you are quite there yet.  VCL needs to be able to ssh into
>>>> the
>>>> image to perform some configuration.  I am pretty sure the VM you are
>>>> trying
>>>> to capture an image of needs to be registered with the host and powered
>>>> on.
>>>>   From the looks of the error below, the VM may not have been registered
>>>> with
>>>> the host.  Or perhaps the Image you are trying to capture is a registered
>>>> VM, but its name does not match the virtual machine VCL is looking for.
>>>>
>>>> 2010-06-01 13:52:28|13095|1:10|image|esx.pm:capture(661)|Powered off:
>>>> Virtual Machine vmwarelinux-base10-v1 not found.
>>>>
>>>> I real issue again has to do with this error where VCL is unable to SSH
>>>> into
>>>> the VM.
>>>>
>>>> |13095|1:10|image| ---- WARNING ----
>>>> |13095|1:10|image| 2010-06-01
>>>> 13:52:07|13095|1:10|image|utils.pm:run_ssh_command(6252)|attempt 1/3:
>>>> failed to execute SSH command on vmwarelinux-base10-v1: echo
>>>> vmwarelinux-base10-v1>  /root/currentimage.txt, exit status: 255, SSH
>>>> exits with the exit status of the remote command or with 255 if an
>>>> error occurred, output:
>>>> |13095|1:10|image| ssh output (echo vmwar...): ssh:
>>>> vmwarelinux-base10-v1: Name or service not known
>>>> |13095|1:10|image| ( 0) utils.pm, notify (line: 737)
>>>> |13095|1:10|image| (-1) utils.pm, run_ssh_command (line: 6252)
>>>> |13095|1:10|image| (-2) esx.pm, capture (line: 650)
>>>> |13095|1:10|image| (-3) image.pm, process (line: 162)
>>>> |13095|1:10|image| (-4) vcld, make_new_child (line: 596)
>>>> |13095|1:10|image| (-5) vcld, main (line: 341)
>>>>
>>>> On Tue, Jun 1, 2010 at 3:55 PM, My LinuxHAList
>>>> <mylinuxhal...@gmail.com>wrote:
>>>>
>>>>
>>>>> I went ahead to switch it to NFS (helpful users have suggested it to
>>>>> me as work-arounds).
>>>>> I hope that I'm done with my initial image (given the logs entries, I
>>>>> think I'm done with the initial image creation - please point out if
>>>>> I'm wrong).
>>>>>
>>>>> This message might be more appropriate to vcl-user.
>>>>>
>>>>> ===========================================================
>>>>> OUTPUT for vcld run on 2010-06-01 13:50:35
>>>>> ===========================================================
>>>>> 2010-06-01 13:50:35|13091|vcld:main(116)|vcld environment variable set
>>>>> to 1 for this process
>>>>> 2010-06-01 13:50:35|13091|utils.pm:rename_vcld_process(7901)|renamed
>>>>> process to 'vcld vcld'
>>>>> 2010-06-01 13:50:35|13091|utils.pm:
>>>>> get_management_node_info(6815)|management
>>>>> node info retrieved from database for managementnode
>>>>> 2010-06-01 13:50:35|13091|vcld:main(127)|retrieved management node
>>>>> information from database
>>>>> 2010-06-01 13:50:35|13091|vcld:main(140)|management_node_id
>>>>> environment variable set: 1
>>>>> 2010-06-01 13:50:35|13091|vcld:main(148)|management node checkin
>>>>> interval is 5 seconds
>>>>> 2010-06-01 13:50:35|13091|vcld:main(149)|vcld started on
>>>>> managementnode.local
>>>>> 2010-06-01 13:50:40|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:50:40
>>>>> 2010-06-01 13:50:45|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:50:45
>>>>> 2010-06-01 13:50:50|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:50:50
>>>>> 2010-06-01 13:50:55|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:50:55
>>>>> 2010-06-01 13:51:00|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:00
>>>>> 2010-06-01 13:51:05|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:05
>>>>> 2010-06-01 13:51:10|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:10
>>>>> 2010-06-01 13:51:15|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:15
>>>>> 2010-06-01 13:51:20|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:20
>>>>> 2010-06-01 13:51:25|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:25
>>>>> 2010-06-01 13:51:30|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:30
>>>>> 2010-06-01 13:51:35|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:35
>>>>> 2010-06-01 13:51:40|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:40
>>>>> 2010-06-01 13:51:45|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:45
>>>>> 2010-06-01 13:51:50|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:50
>>>>> 2010-06-01 13:51:55|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:51:55
>>>>> 2010-06-01 13:52:00|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:00
>>>>> 2010-06-01 13:52:05|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:05
>>>>> 2010-06-01 13:52:05|13091|1:10|image|utils.pm:
>>>>> reservation_being_processed(9634)|computerloadlog
>>>>> 'begin' entry does NOT exist for reservation 10
>>>>> 2010-06-01 13:52:05|13091|1:10|image|utils.pm:
>>>>> reservation_being_processed(9686)|reservation
>>>>> is NOT currently being processed
>>>>> 2010-06-01 13:52:05|13091|1:10|image|vcld:main(276)|reservation 10 is
>>>>> NOT already being processed
>>>>>
>>>>> |13091|1:10|image| ---- WARNING ----
>>>>> |13091|1:10|image| 2010-06-01
>>>>>
>>>>> 13:52:05|13091|1:10|image|utils.pm:get_request_info(5218)|preferredimageid
>>>>> is not set for computer id=2
>>>>> |13091|1:10|image| ( 0) utils.pm, notify (line: 737)
>>>>> |13091|1:10|image| (-1) utils.pm, get_request_info (line: 5218)
>>>>> |13091|1:10|image| (-2) vcld, main (line: 280)
>>>>>
>>>>> 2010-06-01 13:52:05|13091|1:10|image|utils.pm:
>>>>> get_request_info(5354)|standalone
>>>>> affiliation found: Local
>>>>> 2010-06-01 13:52:05|13091|1:10|image|utils.pm:
>>>>> get_management_node_info(6815)|management
>>>>> node info retrieved from database for managementnode
>>>>> 2010-06-01 13:52:05|13091|1:10|image|vcld:main(281)|retrieved request
>>>>> information from database
>>>>> 2010-06-01 13:52:05|13091|1:10|image|utils.pm:
>>>>> get_management_node_info(6815)|management
>>>>> node info retrieved from database for managementnode
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13091|1:10|image|DataStructure.pm:is_parent_reservation(854)|returning
>>>>> true: parent reservation ID for this request: 10
>>>>> 2010-06-01 13:52:05|13091|1:10|image|utils.pm:
>>>>> update_request_state(2186)|request
>>>>> 1 state updated to: pending, laststate to: image
>>>>> 2010-06-01
>>>>> 13:52:05|13091|1:10|image|utils.pm:insertloadlog(4710)|inserted
>>>>> computer=2, begin, beginning to process, state is image
>>>>> 2010-06-01 13:52:05|13091|1:10|image|vcld:make_new_child(509)|loaded
>>>>> VCL::image module
>>>>> 2010-06-01 13:52:05|13095|1:10|image|vcld:make_new_child(582)|vcld
>>>>> environment variable set to 0 for this process
>>>>> 2010-06-01 13:52:05|13091|1:10|image|vcld:make_new_child(566)|current
>>>>> number of forked kids: 1
>>>>> 2010-06-01 13:52:05|13095|1:10|image|Module.pm:new(132)|constructor
>>>>> called, class=VCL::image
>>>>> 2010-06-01 13:52:05|13095|1:10|image|Module.pm:new(154)|VCL::image
>>>>> object created
>>>>> 2010-06-01 13:52:05|13095|1:10|image|State.pm:initialize(85)|obtained
>>>>> a database handle for this state process, stored as $ENV{dbh}
>>>>> 2010-06-01 13:52:05|13095|1:10|image|State.pm:check_image_os(839)|no
>>>>> corrections need to be made to image OS: vmwarelinux
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|DataStructure.pm:is_parent_reservation(854)|returning
>>>>> true: parent reservation ID for this request: 10
>>>>> 2010-06-01 13:52:05|13095|1:10|image|utils.pm:
>>>>> rename_vcld_process(7863)|reservation
>>>>> count: 1
>>>>> 2010-06-01 13:52:05|13095|1:10|image|utils.pm:
>>>>> rename_vcld_process(7882)|PARENTIMAGE:
>>>>> 1
>>>>> 2010-06-01 13:52:05|13095|1:10|image|utils.pm:
>>>>> rename_vcld_process(7883)|SUBIMAGE:
>>>>> 0
>>>>> 2010-06-01 13:52:05|13095|1:10|image|utils.pm:
>>>>> rename_vcld_process(7901)|renamed
>>>>> process to 'vcld VCL::image 1:10 image imaging'
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|DataStructure.pm:is_parent_reservation(854)|returning
>>>>> true: parent reservation ID for this request: 10
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|DataStructure.pm:is_parent_reservation(854)|returning
>>>>> true: parent reservation ID for this request: 10
>>>>> 2010-06-01 13:52:05|13095|1:10|image|State.pm:initialize(121)|attempting
>>>>> to load provisioning module: VCL::Module::Provisioning::esx
>>>>> 2010-06-01 13:52:05|13095|1:10|image|esx.pm:initialize(138)|esx vmware
>>>>> toolkit root path found: /usr/lib/vmware-vcli/apps
>>>>> 2010-06-01 13:52:05|13095|1:10|image|esx.pm:initialize(140)|vmware ESX
>>>>> module initialized
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|State.pm:initialize(127)|VCL::Module::Provisioning::esx
>>>>> module loaded
>>>>> 2010-06-01 13:52:05|13095|1:10|image|Module.pm:new(132)|constructor
>>>>> called, class=VCL::Module::Provisioning::esx
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|Module.pm:new(154)|VCL::Module::Provisioning::esx
>>>>> object created
>>>>> 2010-06-01 13:52:05|13095|1:10|image|esx.pm:initialize(138)|esx vmware
>>>>> toolkit root path found: /usr/lib/vmware-vcli/apps
>>>>> 2010-06-01 13:52:05|13095|1:10|image|esx.pm:initialize(140)|vmware ESX
>>>>> module initialized
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|State.pm:initialize(131)|VCL::Module::Provisioning::esx
>>>>> provisioner object created
>>>>> 2010-06-01 13:52:05|13095|1:10|image|State.pm:initialize(145)|attempting
>>>>> to load OS module: VCL::Module::OS::Linux
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|State.pm:initialize(151)|VCL::Module::OS::Linux
>>>>> module loaded
>>>>> 2010-06-01 13:52:05|13095|1:10|image|Module.pm:new(132)|constructor
>>>>> called, class=VCL::Module::OS::Linux
>>>>> 2010-06-01
>>>>> 13:52:05|13095|1:10|image|Module.pm:new(154)|VCL::Module::OS::Linux
>>>>> object created
>>>>> 2010-06-01
>>>>>
>>>>> 13:52:05|13095|1:10|image|State.pm:initialize(154)|VCL::Module::OS::Linux
>>>>> OS object created
>>>>> 2010-06-01 13:52:05|13095|1:10|image|State.pm:initialize(169)|returning
>>>>> 1
>>>>> 2010-06-01 13:52:05|13095|1:10|image|vcld:make_new_child(593)|VCL::image
>>>>> object created and initialized
>>>>> No recipient addresses found in header
>>>>> 2010-06-01 13:52:05|13095|1:10|image|utils.pm:mail(1348)|SUCCESS --
>>>>> Sending mail To: , VCL IMAGE Creation Started: vmwarelinux-base10-v1
>>>>> 2010-06-01 13:52:05|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'ls -1 /export/nfsstore/golden 2>&1' 2>&1
>>>>> 2010-06-01 13:52:07|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6262)|run_ssh_command
>>>>> output:
>>>>> |13095|1:10|image| none
>>>>> 2010-06-01 13:52:07|13095|1:10|image|utils.pm:run_ssh_command(6276)|SSH
>>>>> command executed on 192.168.88.4, returning (0, "none")
>>>>>
>>>>> |13095|1:10|image| ---- WARNING ----
>>>>> |13095|1:10|image| 2010-06-01
>>>>> 13:52:07|13095|1:10|image|esx.pm:does_image_exist(926)|image
>>>>> /export/nfsstore/golden/vmwarelinux-base10-v1 does NOT exists
>>>>> |13095|1:10|image| ( 0) utils.pm, notify (line: 737)
>>>>> |13095|1:10|image| (-1) esx.pm, does_image_exist (line: 926)
>>>>> |13095|1:10|image| (-2) image.pm, process (line: 135)
>>>>> |13095|1:10|image| (-3) vcld, make_new_child (line: 596)
>>>>> |13095|1:10|image| (-4) vcld, main (line: 341)
>>>>>
>>>>> 2010-06-01 13:52:07|13095|1:10|image|image.pm:process(145)|image
>>>>> vmwarelinux-base10-v1 does not exist in the repository
>>>>> 2010-06-01
>>>>> 13:52:07|13095|1:10|image|DataStructure.pm:_automethod(697)|data
>>>>> structure updated:
>>>>> $self->request_data->{reservation}{10}{image}{lastupdate}
>>>>> |13095|1:10|image| image_lastupdate = 2010-06-01 13:52:07
>>>>> 2010-06-01
>>>>> 13:52:07|13095|1:10|image|DataStructure.pm:_automethod(697)|data
>>>>> structure updated:
>>>>> $self->request_data->{reservation}{10}{imagerevision}{datecreated}
>>>>> |13095|1:10|image| imagerevision_date_created = 2010-06-01 13:52:07
>>>>> 2010-06-01 13:52:07|13095|1:10|image|image.pm:process(161)|calling
>>>>> provisioning module's capture() subroutine
>>>>> 2010-06-01 13:52:07|13095|1:10|image|esx.pm:
>>>>> capture(593)|**********************************************************
>>>>> 2010-06-01 13:52:07|13095|1:10|image|esx.pm:capture(594)|Entering ESX
>>>>> Capture routine
>>>>> 2010-06-01 13:52:07|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'ls -1 /export/nfsstore/inuse/vmwarelinux-base10-v1 2>&1'
>>>>> 2>&1
>>>>> 2010-06-01 13:52:07|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6262)|run_ssh_command
>>>>> output:
>>>>> |13095|1:10|image| vmwarelinux-base10-v1-flat.vmdk
>>>>> |13095|1:10|image| vmwarelinux-base10-v1.nvram
>>>>> |13095|1:10|image| vmwarelinux-base10-v1.vmdk
>>>>> |13095|1:10|image| vmwarelinux-base10-v1.vmsd
>>>>> |13095|1:10|image| vmwarelinux-base10-v1.vmx
>>>>> |13095|1:10|image| vmwarelinux-base10-v1.vmxf
>>>>> |13095|1:10|image| vmware.log
>>>>> 2010-06-01 13:52:07|13095|1:10|image|utils.pm:run_ssh_command(6276)|SSH
>>>>> command executed on 192.168.88.4, returning (0,
>>>>> "vmwarelinux-base10-v1-flat.vmd...")
>>>>> 2010-06-01 13:52:07|13095|1:10|image|esx.pm:capture(646)|found
>>>>> previous name= vmwarelinux-base10-v1
>>>>> 2010-06-01 13:52:07|13095|1:10|image|esx.pm:capture(648)|SSHing to
>>>>> node to configure currentimage.txt
>>>>> 2010-06-01 13:52:07|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on vmwarelinux-base10-v1:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> vmwarelinux-base10-v1 'echo vmwarelinux-base10-v1>
>>>>> /root/currentimage.txt' 2>&1
>>>>>
>>>>> |13095|1:10|image| ---- WARNING ----
>>>>> |13095|1:10|image| 2010-06-01
>>>>> 13:52:07|13095|1:10|image|utils.pm:run_ssh_command(6252)|attempt 1/3:
>>>>> failed to execute SSH command on vmwarelinux-base10-v1: echo
>>>>> vmwarelinux-base10-v1>  /root/currentimage.txt, exit status: 255, SSH
>>>>> exits with the exit status of the remote command or with 255 if an
>>>>> error occurred, output:
>>>>> |13095|1:10|image| ssh output (echo vmwar...): ssh:
>>>>> vmwarelinux-base10-v1: Name or service not known
>>>>> |13095|1:10|image| ( 0) utils.pm, notify (line: 737)
>>>>> |13095|1:10|image| (-1) utils.pm, run_ssh_command (line: 6252)
>>>>> |13095|1:10|image| (-2) esx.pm, capture (line: 650)
>>>>> |13095|1:10|image| (-3) image.pm, process (line: 162)
>>>>> |13095|1:10|image| (-4) vcld, make_new_child (line: 596)
>>>>> |13095|1:10|image| (-5) vcld, main (line: 341)
>>>>>
>>>>> 2010-06-01 13:52:07|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6172)|sleeping
>>>>> for 2 seconds before making next SSH attempt
>>>>> 2010-06-01 13:52:09|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6184)|attempt
>>>>> 2/3: executing SSH command on vmwarelinux-base10-v1:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> vmwarelinux-base10-v1 'echo vmwarelinux-base10-v1>
>>>>> /root/currentimage.txt' 2>&1
>>>>>
>>>>> |13095|1:10|image| ---- WARNING ----
>>>>> |13095|1:10|image| 2010-06-01
>>>>> 13:52:09|13095|1:10|image|utils.pm:run_ssh_command(6252)|attempt 2/3:
>>>>> failed to execute SSH command on vmwarelinux-base10-v1: echo
>>>>> vmwarelinux-base10-v1>  /root/currentimage.txt, exit status: 255, SSH
>>>>> exits with the exit status of the remote command or with 255 if an
>>>>> error occurred, output:
>>>>> |13095|1:10|image| ssh output (echo vmwar...): ssh:
>>>>> vmwarelinux-base10-v1: Name or service not known
>>>>> |13095|1:10|image| ( 0) utils.pm, notify (line: 737)
>>>>> |13095|1:10|image| (-1) utils.pm, run_ssh_command (line: 6252)
>>>>> |13095|1:10|image| (-2) esx.pm, capture (line: 650)
>>>>> |13095|1:10|image| (-3) image.pm, process (line: 162)
>>>>> |13095|1:10|image| (-4) vcld, make_new_child (line: 596)
>>>>> |13095|1:10|image| (-5) vcld, main (line: 341)
>>>>>
>>>>> 2010-06-01 13:52:09|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6172)|sleeping
>>>>> for 15 seconds before making next SSH attempt
>>>>> 2010-06-01 13:52:10|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:10
>>>>> 2010-06-01 13:52:15|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:15
>>>>> 2010-06-01 13:52:20|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:20
>>>>> 2010-06-01 13:52:24|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6184)|attempt
>>>>> 3/3: executing SSH command on vmwarelinux-base10-v1:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> vmwarelinux-base10-v1 'echo vmwarelinux-base10-v1>
>>>>> /root/currentimage.txt' 2>&1
>>>>>
>>>>> |13095|1:10|image| ---- WARNING ----
>>>>> |13095|1:10|image| 2010-06-01
>>>>> 13:52:24|13095|1:10|image|utils.pm:run_ssh_command(6252)|attempt 3/3:
>>>>> failed to execute SSH command on vmwarelinux-base10-v1: echo
>>>>> vmwarelinux-base10-v1>  /root/currentimage.txt, exit status: 255, SSH
>>>>> exits with the exit status of the remote command or with 255 if an
>>>>> error occurred, output:
>>>>> |13095|1:10|image| ssh output (echo vmwar...): ssh:
>>>>> vmwarelinux-base10-v1: Name or service not known
>>>>> |13095|1:10|image| ( 0) utils.pm, notify (line: 737)
>>>>> |13095|1:10|image| (-1) utils.pm, run_ssh_command (line: 6252)
>>>>> |13095|1:10|image| (-2) esx.pm, capture (line: 650)
>>>>> |13095|1:10|image| (-3) image.pm, process (line: 162)
>>>>> |13095|1:10|image| (-4) vcld, make_new_child (line: 596)
>>>>> |13095|1:10|image| (-5) vcld, main (line: 341)
>>>>>
>>>>>
>>>>> |13095|1:10|image| ---- WARNING ----
>>>>> |13095|1:10|image| 2010-06-01
>>>>> 13:52:24|13095|1:10|image|utils.pm:run_ssh_command(6285)|failed to run
>>>>> SSH command after 3 attempts, command: /usr/bin/ssh -i
>>>>> /etc/vcl/vcl.key  -l root -p 22 -x vmwarelinux-base10-v1 'echo
>>>>> vmwarelinux-base10-v1>  /root/currentimage.txt' 2>&1, exit status:
>>>>> 255, output:
>>>>> |13095|1:10|image| ssh output (echo vmwar...): ssh:
>>>>> vmwarelinux-base10-v1: Name or service not known
>>>>> |13095|1:10|image| ( 0) utils.pm, notify (line: 737)
>>>>> |13095|1:10|image| (-1) utils.pm, run_ssh_command (line: 6285)
>>>>> |13095|1:10|image| (-2) esx.pm, capture (line: 650)
>>>>> |13095|1:10|image| (-3) image.pm, process (line: 162)
>>>>> |13095|1:10|image| (-4) vcld, make_new_child (line: 596)
>>>>> |13095|1:10|image| (-5) vcld, main (line: 341)
>>>>>
>>>>> 2010-06-01 13:52:24|13095|1:10|image|esx.pm:capture(658)|Power off
>>>>> command: /usr/lib/vmware-vcli/apps/vm/vmcontrol.pl --server 'vmnode2'
>>>>> --vmname vmwarelinux-base10-v1 --operation poweroff --username root
>>>>> --password 'notmypassword'
>>>>> 2010-06-01 13:52:25|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:25
>>>>> 2010-06-01 13:52:28|13095|1:10|image|esx.pm:capture(661)|Powered off:
>>>>> Virtual Machine vmwarelinux-base10-v1 not found.
>>>>> 2010-06-01 13:52:28|13095|1:10|image|esx.pm:capture(663)|Waiting 5
>>>>> seconds for power off
>>>>> 2010-06-01 13:52:30|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:30
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'mkdir /export/nfsstore/golden/vmwarelinux-base10-v1'
>>>>> 2>&1
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6262)|run_ssh_command
>>>>> output:
>>>>> |13095|1:10|image| none
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:run_ssh_command(6276)|SSH
>>>>> command executed on 192.168.88.4, returning (0, "none")
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'cp
>>>>> /export/nfsstore/inuse/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmdk
>>>>>
>>>>> /export/nfsstore/golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmdk'
>>>>> 2>&1
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6262)|run_ssh_command
>>>>> output:
>>>>> |13095|1:10|image| none
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:run_ssh_command(6276)|SSH
>>>>> command executed on 192.168.88.4, returning (0, "none")
>>>>> 2010-06-01 13:52:33|13095|1:10|image|esx.pm:capture(679)|COPIED VMDK
>>>>> SUCCESSFULLY
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'cp
>>>>> /export/nfsstore/inuse/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmx
>>>>> /export/nfsstore/golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmx'
>>>>> 2>&1
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6262)|run_ssh_command
>>>>> output:
>>>>> |13095|1:10|image| none
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:run_ssh_command(6276)|SSH
>>>>> command executed on 192.168.88.4, returning (0, "none")
>>>>> 2010-06-01 13:52:33|13095|1:10|image|esx.pm:capture(688)|COPIED VMX
>>>>> SUCCESSFULLY
>>>>> 2010-06-01 13:52:33|13095|1:10|image|esx.pm:capture(691)|Rewriting
>>>>> VMDK and VMX files with new image name
>>>>> 2010-06-01 13:52:33|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'sed -i "s/vmwarelinux-base10-v1/vmwarelinux-base10-v1/"
>>>>> /export/nfsstore/golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmx'
>>>>> 2>&1
>>>>> 2010-06-01 13:52:34|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6262)|run_ssh_command
>>>>> output:
>>>>> |13095|1:10|image| none
>>>>> 2010-06-01 13:52:34|13095|1:10|image|utils.pm:run_ssh_command(6276)|SSH
>>>>> command executed on 192.168.88.4, returning (0, "none")
>>>>> 2010-06-01 13:52:34|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'sed -i "s/vmwarelinux-base10-v1/vmwarelinux-base10-v1/"
>>>>>
>>>>> /export/nfsstore/golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1.vmdk'
>>>>> 2>&1
>>>>> 2010-06-01 13:52:34|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6262)|run_ssh_command
>>>>> output:
>>>>> |13095|1:10|image| none
>>>>> 2010-06-01 13:52:34|13095|1:10|image|utils.pm:run_ssh_command(6276)|SSH
>>>>> command executed on 192.168.88.4, returning (0, "none")
>>>>> 2010-06-01 13:52:34|13095|1:10|image|esx.pm:capture(705)|Preparing to
>>>>> ssh to 192.168.88.4 copy vmdk-flat from
>>>>>
>>>>>
>>>>> /export/nfsstore/inuse/vmwarelinux-base10-v1/vmwarelinux-base10-v1-flat.vmdk
>>>>> to
>>>>>
>>>>> /export/nfsstore/golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1-flat.vmdk
>>>>> 2010-06-01 13:52:34|13095|1:10|image|esx.pm:capture(706)|SSHing to
>>>>> copy vmdk-flat file
>>>>> 2010-06-01 13:52:34|13095|1:10|image|utils.pm:
>>>>> run_ssh_command(6180)|executing
>>>>> SSH command on 192.168.88.4:
>>>>> |13095|1:10|image| /usr/bin/ssh -i /etc/vcl/vcl.key  -l root -p 22 -x
>>>>> 192.168.88.4 'cp
>>>>>
>>>>>
>>>>> /export/nfsstore/inuse/vmwarelinux-base10-v1/vmwarelinux-base10-v1-flat.vmdk
>>>>>
>>>>>
>>>>> /export/nfsstore/golden/vmwarelinux-base10-v1/vmwarelinux-base10-v1-flat.vmdk'
>>>>> 2>&1
>>>>> 2010-06-01 13:52:35|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:35
>>>>> 2010-06-01 13:52:40|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:40
>>>>> 2010-06-01 13:52:45|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:45
>>>>> 2010-06-01 13:52:50|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:50
>>>>> 2010-06-01 13:52:55|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:52:55
>>>>> 2010-06-01 13:53:00|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:00
>>>>> 2010-06-01 13:53:05|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:05
>>>>> 2010-06-01 13:53:10|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:10
>>>>> 2010-06-01 13:53:15|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:15
>>>>> 2010-06-01 13:53:20|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:20
>>>>> 2010-06-01 13:53:25|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:25
>>>>> 2010-06-01 13:53:30|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:30
>>>>> 2010-06-01 13:53:35|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:35
>>>>> 2010-06-01 13:53:40|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:40
>>>>> 2010-06-01 13:53:45|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:45
>>>>> 2010-06-01 13:53:50|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:50
>>>>> 2010-06-01 13:53:55|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:53:55
>>>>> 2010-06-01 13:54:00|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:00
>>>>> 2010-06-01 13:54:05|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:05
>>>>> 2010-06-01 13:54:11|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:10
>>>>> 2010-06-01 13:54:16|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:16
>>>>> 2010-06-01 13:54:21|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:21
>>>>> 2010-06-01 13:54:26|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:26
>>>>> 2010-06-01 13:54:31|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:31
>>>>> 2010-06-01 13:54:36|13091|vcld:main(165)|lastcheckin time updated for
>>>>> management node 1: 2010-06-01 13:54:36
>>>>>
>>>>>
>>>>> On Sat, May 29, 2010 at 2:34 PM, Ryan Johnson<rjoh...@gwmail.gwu.edu>
>>>>> wrote:
>>>>>
>>>>>> SSH is disabled by default on the ESXi host and is 'unsupported' by
>>>>>>
>>>>> Vmware.
>>>>>
>>>>>>   I've noticed this behavior as well, where the command succeeds but it
>>>>>> is
>>>>>> not reflected in the return code.  You can enable SSH by going to the
>>>>>>
>>>>> ESXi
>>>>>
>>>>>> console.  If you go the NFS route make sure to use the address of the
>>>>>> NFS
>>>>>>
>>>>> on
>>>>>
>>>>>> the exporting computer rather than address of the mount of the ESXi
>>>>>> host
>>>>>>
>>>>> or
>>>>>
>>>>>> you will run into the same problems if SSH is not enabled.  The idea
>>>>>> that
>>>>>> the VCL developers have expressed is that using an NFS setup
>>>>>> distributes
>>>>>>
>>>>> the
>>>>>
>>>>>> workload among multiple drives which improves performance.
>>>>>>
>>>>>> On Sat, May 29, 2010 at 2:21 PM, My LinuxHAList
>>>>>> <mylinuxhal...@gmail.com
>>>>>> wrote:
>>>>>>
>>>>>>
>>>>>>> Replying to my own thread:
>>>>>>>
>>>>>>>
>>>>>>>>> (2) Any updates from an old issue:
>>>>>>>>>
>>>>>>>>>
>>>>>>> http://www.mail-archive.com/vcl-dev@incubator.apache.org/msg00900.html
>>>>>>>
>>>>>>>>>   The target is ESXi 3.5 host.
>>>>>>>>>
>>>>>>> To get familiarity of the software, I've been using ESXi 3.5 local
>>>>>>> disk storage; so I specify the datastore to be ESXi's IP:/PATH.
>>>>>>>
>>>>>>> Hence, during image capture phase, the ssh commands seem to be going
>>>>>>> off to the ESXi host.
>>>>>>> The command seems to succeed all the time; however the return code is
>>>>>>> mostly 255 and sometimes 0.
>>>>>>> It's weird because I'm certain that commands being sent were
>>>>>>> successful; I reproduced it manually the weird behavior
>>>>>>> ( similar to
>>>>>>> http://www.mail-archive.com/vcl-dev@incubator.apache.org/msg00900.html
>>>>>>> )
>>>>>>>
>>>>>>> I take that this is an sshd oddity on ESXi host.
>>>>>>>
>>>>>>> I saw entries of "localdisk" or "networkdisk" on vmprofile. Not sure
>>>>>>> how they are used.
>>>>>>>
>>>>>>> Is the setup of ESXi with local disk considered to be a supported
>>>>>>> option
>>>>>>>
>>>>> ?
>>>>>
>>>>>>> If so, how would I get around the sshd oddity for the ESXi's
>>>>>>> IP:/DATASTOREPATH issues during image capture ? Or I should do things
>>>>>>> differently for localdisk.
>>>>>>>
>>>>>>> I'll switch to NFS so that I can move forward.
>>>>>>>
>>>>>>> I wish to get some understanding on potentially what I did wrong or
>>>>>>> what I did was simply an "unsupported" setup.
>>>>>>>
>>>>>>> Thanks again.
>>>>>>>
>>>>>>>
>>


--

Aaron Peeler
Program Manager
Virtual Computing Lab
NC State University
aaron_pee...@ncsu.edu
919-513-4571

Reply via email to