9 Replies Latest reply on Sep 18, 2013 1:30 PM by Desrtrider

    VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails

    Desrtrider Novice

      I have built this several different ways now and I always get this same exact error. I am running as "Admin" so I have every privilege available.

      There are no special characters in the password, I have tried this build file and it has gotten farther on workstation than this (bootable v-app with interface).

      Please help me get to the next step I am stuck here.

       

      Everything looks fine until:

      10/09/2013 18:00:25 [info] Validating available disk space...
      10/09/2013 18:00:25 [info] Preparing the OS installation files.
      10/09/2013 18:00:25 [info] Looking for /opt/vmware/www/ISV/ISO/CentOS-6.4-x86_64-bin-DVD1.iso
      10/09/2013 18:00:25 [info] Validating md5 checksum for /opt/vmware/www/ISV/ISO/CentOS-6.4-x86_64-bin-DVD1.iso (may take a few minutes)
      10/09/2013 18:01:15 [info] Checking application package repositories for packages to be installed...
      10/09/2013 18:01:16 [info] Creating package repositories...
      10/09/2013 18:01:16 [info] Creating the template vm.
      10/09/2013 18:01:17 [info] Transporting VM from Studio to provisioning host; this may take a few minutes...
      10/09/2013 18:02:20 [warn] Unable to upload /opt/vmware/www/build/Tenacity.1/Tenacity.1_provstart.iso to the s-core9 datastore.
      10/09/2013 18:02:20 [warn]
      %3  %7  %11  %15  %19  %23  %26  %30  %34  %38  %42 Failure: (22, 'The requested URL returned error: 401')
      10/09/2013 18:02:20 [error] Encountered a fatal build error!

       

      I am able to use this template for Centos on the workstation to actually install and build a vapp with centos on it-- unfortunately I have to do quite a few

      hacks to make it work properly and I cannot get it to install actual other applications (maybe there is a new release for workstation 10??)

      Thus I switched back to vsphere, and I KNOW my build template is ok, at least to get the OS installed.

       

      What information can I give you or what can I try, thanks!

      Is it actually "sort-of" loading ie %42 or is that a total failure?

        • 1. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
          samdoyle Enthusiast
          VMware Employees

          Hi,

           

          Unfortunately there are times as you can see here where the log doen't provide much help.

           

          If you look in all the logs under /opt/vmware/www/build/<yourpofile.instance>/status such as the verbose and debug logs you might find something more useful.

          Some additional places to look that hopefully might help:

          - Additional logs under /opt/vmware/var/log/*

          - The standard log directory /var/log

          - View the console of the vm being built and cycle through the terminals ALT+F1-F6.

          1 person found this helpful
          • 2. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
            Desrtrider Novice

            This is about all I can find:

            /opt/vmware/share/build doesn't succeed here.. I will try again.-- also I have never seen the console of the vm being built-- it never shows up..

             

             

            11/09/2013 12:35:41 [dbug] Transporting VM between vCenter and Studio via ovftool.
            11/09/2013 12:35:41 [dbug]
            11/09/2013 12:35:41 [dbug] Input Command: </opt/vmware/share/ovftool/ovftool --acceptAllEulas '--name=192.88.51.209_Tenacity.4' '--datastore=san8' '--network=VM MCS Private'    '--diskMode=thin' '/opt/vmware/www/build/Tenacity.4/va/VM-happydays.vmx' 'vi://bahamas%5Cadmin@vcenter.com:443/dcenter1/host/NA Core cluster/'>
            11/09/2013 12:35:41 [dbug] Expect wait-time: <60> max-time: <7200>
            11/09/2013 12:35:41 [dbug] Command to spawn: <rm -f /tmp/asxlixC691; /opt/vmware/share/ovftool/ovftool --acceptAllEulas '--name=192.88.51.209_Tenacity.4' '--datastore=san8' '--network=VM MCS Private'    '--diskMode=thin' '/opt/vmware/www/build/Tenacity.4/va/VM-happydays.vmx' 'vi://bahamas%5Cadmin@vcenter.com:443/dcenter1/host/NA Core cluster/' 2>&1; echo $? > /tmp/asxlixC691>
            11/09/2013 12:35:50 [dbug] Expected times of asking passwords: 1
            11/09/2013 12:35:55 [dbug] Command launched.
            11/09/2013 12:35:55 [dbug] Command stdout: <************
            Opening VI target: vi://bahamas%5Cadmin@vcenter.com:443/dcenter1QA/host/dcenter1cluster/
            Warning:
            - The specified operating system identifier '' (id: 80) is not supported on the selected host. It will be mapped to the following OS identifier: 'Other Linux (64-bit)'.
            Deploying to VI: vi://bahamas%5Cadmin@vcenter.com:443/dcenter1QA/host/dcenter1cluster/
            ^MDisk progress: 0%^MDisk progress: >

            11/09/2013 12:35:55 [dbug] Waiting for command to complete...
            11/09/2013 12:35:55 [dbug] Verbose interval - 60s
            11/09/2013 12:36:02 [dbug] Command stdout: <78%^MDisk progress: 79%^MDisk progress: 80%^MDisk progress: 81%^MDisk progress: 82%^MDisk progress: 83%^MDisk progress: 84%^MDisk progress: 85%^MDisk progress: 86%^MDisk progress: 87%^MDisk progress: 88%^MDisk progress: 89%^MDisk progress: 90%^MDisk progress: 91%
            ^MDisk progress: 92%^MDisk progress: 93%^MDisk progress: 94%^MDisk progress: 95%^MDisk progress: 96%^MDisk progress: 97%^MDisk progress: 98%^MDisk progress: 99%^MDisk Transfer Completed

            Completed successfully
            >

            11/09/2013 12:36:03 [dbug] Command stdout: <>

            11/09/2013 12:36:03 [dbug] VM transporting completed.
            11/09/2013 12:36:03 [dbug]
            11/09/2013 12:36:03 [dbug] Input Command: </opt/vmware/share/build/datastore --verbose --put  --server vcenter.com --port 443 --user bahamas\admin --datastore 'san8' --folder '192.88.51.209_Tenacity.4' --file '/opt/vmware/www/build/Tenacity.4/192.88.51.209_Tenacity.4_provstart.iso' --datacenter 'dcenter1'>
            11/09/2013 12:36:03 [dbug] Expect wait-time: <60> max-time: <7200>
            11/09/2013 12:36:03 [dbug] Command to spawn: <rm -f /tmp/awTKgOXVSo; /opt/vmware/share/build/datastore --verbose --put  --server vcenter.com --port 443 --user bahamas\admin --datastore 'san8' --folder '192.88.51.209_Tenacity.4' --file '/opt/vmware/www/build/Tenacity.4/192.88.51.209_Tenacity.4_provstart.iso' --datacenter 'dcenter1' 2>&1; echo $? > /tmp/awTKgOXVSo>
            11/09/2013 12:36:09 [dbug] Command launched.
            11/09/2013 12:36:09 [dbug] Command stdout: <
            ^M%3 ^M%7 ^M%11 ^M%15 ^M%19 ^M%23 ^M%26 ^M%30 ^M%34 ^M%38 ^M%42>

            11/09/2013 12:36:09 [dbug] Waiting for command to complete...
            11/09/2013 12:36:09 [dbug] Verbose interval - 60s
            11/09/2013 12:36:20 [dbug] Command stdout: < Failure: (22, 'The requested URL returned error: 401')
            >

            11/09/2013 12:36:21 [dbug] Command stdout: <>

            11/09/2013 12:36:21 [warn] Unable to upload /opt/vmware/www/build/Tenacity.4/192.88.51.209_Tenacity.4_provstart.iso to the san8 datastore.
            11/09/2013 12:36:21 [warn]
            ^M%3 ^M%7 ^M%11 ^M%15 ^M%19 ^M%23 ^M%26 ^M%30 ^M%34 ^M%38 ^M%42 Failure: (22, 'The requested URL returned error: 401')

            11/09/2013 12:36:21 [dbug] Ran system shell command "/opt/vmware/share/build/status --set --instance Tenacity.4 --key 'Operation' --value 'canceling' 2>/tmp/qIck4pxHsg"
            11/09/2013 12:36:21 [dbug] system shell command returned: exit 0, signal 0, core 0
            11/09/2013 12:36:21 [error] Encountered a fatal build error!

            • 3. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
              samdoyle Enthusiast
              VMware Employees

              Well the 401 seems to indicate authentication failed.

              Did you try the connection wizard for connecting to your provisioning engine through the web ui?

              • 5. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
                samdoyle Enthusiast
                VMware Employees

                Can you run the:

                /opt/vmware/share/build/datastore --verbose --put  --server vcenter.com --port 443 --user bahamas\admin --datastore 'san8' --folder '192.88.51.209_Tenacity.4' --file '/opt/vmware/www/build/Tenacity.4/192.88.51.209_Tenacity.4_provstart.iso' --datacenter 'dcenter1'

                 

                with the --debug option as well? You will be prompted for a password unless you provide a --password as well.

                1 person found this helpful
                • 6. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
                  Desrtrider Novice


                  hmm, well I got it to run and it has no errors and just gives me the url:

                   

                  https://vcenter.com:443/folder/192.88.51.209_Tenacity.4/192.88.51.209_Tenacity.4_provstart.iso?dcPath=dcenter1

                   

                  D

                  I get no errors or anything..yet I did use the debug command.. however when I try to access the url it does not accept my password for some reason and I KNOW I am typing it correctly...

                   

                  Could the fact that many of the names on my datacenter have spaces in them (sanitized for posting) be influencing this?

                   

                  Are there any alternative VMware offerings that can create/clone a working VM and have an interface so users can change the IP address/etc when deployed?

                  thanks so much Sam!

                   

                  PS I have *NEVER* seen the console of the vm being built and not sure that it is working enough for me to.. I am guessing from your comment that I *should* be able to see this??

                   

                  Message was edited by: Desrtrider

                  • 7. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
                    samdoyle Enthusiast
                    VMware Employees

                    If you have spaces then need to be url encoded. You can do a search for online url encoders/decoders if you want to do this manually but going through the application this is done for you.

                    • 8. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
                      Desrtrider Novice

                      Yes, I have seen this. I actually hard have done the requests with URL encoding -- I think this is one of the issues actually.

                      The code is not identifying and/or encoding the names correctly. I am in the process of bribing our Admin to change them to have underscores/no spaces special characters but no luck yet.

                      SO, even though I issue the command with the appropriate % encoding (%20, %5C) whatever it is just not working properly.

                      • 9. Re: VSphere/Vcenter/ESX 5.0.0 issue: Unable to upload /opt/vmware/www/build/Tenacity.iso to the san-core8 datastore.==> Build fails
                        Desrtrider Novice

                        Ok, I have a build that WORKED, now I see what you mean about watching it build/deploy the guest VM.

                        Here is the solution to my problem: our vcenter uses names with spaces, we also must use domain names for our logins. In addition, every admin password had "special characters" I have meticulously debugged through EACH one of these and more. Basically, it did not matter that I "URL" encoded things, used new tools or edited the various scripts to encode things one way or another,

                        what finally gave us success was to go to a "clean" Vcenter implementation that

                        a) did not use/require a domain name (so no / in credentials)

                        b) had all "original DOS" legal names, ie no spaces, no special characters, etc.

                        c) the passwords contained NO "special characters"

                             (because I changed them that way, "URL" encoding did  not work, tried it)

                         

                        Moral of the story: Build a new, simply configured Vcenter or get to one and use it.

                         

                         

                        (Note: I even downloaded a newer ovftool and tried it every way that I could but did not get any success)