Robert, etal.
Well, I finally figured out what was going on. It appears there is a limit on the number of characters you can have in the hostname. I took a shot in the dark and changed my VM name to annachefvm and it worked was able to find it.
Now, though, I'm having another problem. When I create my VM, it is on, say, ds01, created as [ds01]annachefvm.vmdk. When I run the script to create the additional vmdk's, one of which is on ds01 which I believe 'should' create as: [ds01]annachefvm_1.vmdk and another on ds02, which should create as: [ds02]annachefvm_2.vmdk the command fails saying the vmdk already exists. For some reason, it sees annachefvm already there and stops instead of creating it with the suffix. (I have verified that there wasn't, by some fluke, already a vmdk out there by the same name)
Any suggestions?
And secondary to that, after installing knife-vsphere 0.9.8, it appears to still be executing 0.9.7 I confirmed 0.9.8 installed (gems list shows knife-vsphere (0.9.7,0.9.8) How do I force it to use a specific version or am I suppose to uninstall 0.9.7 first (which I thought multiple version could exist due to other potential application requirements.). I know 0.9.8 isn't executing because I added some 'puts' and none of them executed.
So suggestions for that as well would be much appreciated
I'm so incredibly far behind in this. We only have a handful of people who know chef and the only one who has worked with the vsphere plugin is not available, plus being in a close area just makes it impossible to troubleshoot in a timely manner. Doing the work in an unclassified lab as suggested would be great but some of our contracts do not allow us to bill work done outside of the controlled area.
Anyway, I digress with my whiney story. I would truly appreciate any suggestions on the above two issues.
Thanks again for the help, mostly for your patience as I bumble through this learning process !!!
Anna
Sent from my iPhone
On Mar 20, 2014, at 2:24 PM, Anna Redding <
">
> wrote: Robert
Thank you for your line command. Unfortunately, it did not answer the issue but it told me that the next thing I was going to try wasn't going to work. When I printed the code for 0.9.8, I noticed references to the variable specifying the target lun was defined with an underscore as "target_lun". I thought the might be the problem as I have been using a dash not an underscore ... but your example negated that because you use the 'dash' not the underscore.
I cannot give exact command bc the system is in a secured area but I did write down the various pieces so here it is:
strace -o /tmp/strace-vsphere.out knife vsphere vm vmdk add annaVM 4 --vmdk-type thick --vsdc ISP --vshost <vcIP> --target-lun ds03 --vsport 443 --vsinsecure -VV
When I looked at the strace, the DEBUG sections appeared to reflect the correct values.
After reviewing the 22k+ lines of strace info, I could not find any messages that jumped out, definitely none that were preceded by the DEBUG flag.
Any other ideas? Anna
Sent from my iPhone
On Mar 20, 2014, at 12:17 PM, Robert Tsai <
">
> wrote:
Hi Anna,
Sorry to hear its still not working for you. The command I used was knife vsphere vm vmdk add vmname 3 --target-lun SSDGuest knife vsphere vm vmdk vmname 3 --target-lun SSDGuest
[fog][WARNING] Unable to load the 'unf' gem. Your AWS strings may not be properly encoded. Digest::Digest is deprecated; use Digest DEBUG: value for config item vsphere_host: 2.2.2.2 DEBUG: value for config item vshere_path:
DEBUG: value for config item vsphere_port: 443 DEBUG: value for config item vsphere_nossl: DEBUG: value for config item vsphere_user: testuser DEBUG: value for config item vsphere_pass: testpassword DEBUG: value for config item vsphere_insecure: true
DEBUG: value for config item proxy_host: DEBUG: value for config item proxy_port: DEBUG: value for config item vsphere_host: 2.2.2.2 DEBUG: value for config item vshere_path: DEBUG: value for config item vsphere_port: 443
DEBUG: value for config item vsphere_nossl: DEBUG: value for config item vsphere_user: testuser DEBUG: value for config item vsphere_pass: testpassword DEBUG: value for config item vsphere_insecure: true DEBUG: value for config item proxy_host:
DEBUG: value for config item proxy_port: DEBUG: value for config item folder: DEBUG: value for config item vsphere_dc: testdc
|