Category: Uncategorized

Uploading files to a vSphere service might fail

Details

Initiating a file upload to either a content library or datastore, or attempting to deploy an OVF or OVA template, might result in the operation failing with an error:

The operation failed for an undetermined reason. Typically this problem occurs due to certificates that the browser does not trust. If you are using self-signed or custom certificates, open the URL below in a new browser tab and accept the certificate, then retry the operation.

https://target-ip

To resolve this issue follow the solutions below as per the scenario.

Solution 1:

  1. From a client system Web browser, go to the base URL of the vCenter Server system or the vCenter Server Virtual Appliance without appending port numbers or ‘vsphere-client‘ extension.
    For example:
    https://vcenter.domain.com/
  2. Click the Download trusted root CA certificates link at the bottom of the grey box on the right and download the file.
  3. Change the extension of the file to .zip. The file is a ZIP file of all root certificates and all CRLs in the VMware Endpoint Certificate Store (VECS).
  4. Extract the contents of the ZIP file. The result is a .certs folder that contains two types of files. Files with a number as the extension (.0, .1, and so on) are root certificates. Files with an extension that starts with an r (.r0,. r1, and so on) are CRL files associated with a certificate.
  5. Install the certificate files as trusted certificates by following the process that is appropriate for your operating system.
    For most Microsoft Windows systems, you can follow the instructions at Manage trusted root certificates.
Note: Some datastores with special characters will not allow you to download files. In some cases, removing the special characters from the datastore name has allowed us to download. This is a rare problem and the above solution is more likely.

Solution 2: In some cases the serenity database becomes corrupt, reset serenity DB to resolve the issue following the below steps:

  • In appliance:
    # service vsphere-client stop
    rm -rf /etc/vmware-vsphere-client/SerenityDB/serenity/*
    # service vsphere-client start
  • In vSphere 6.5 and higher
    # service-control –stop vsphere-client
    rm -rf /etc/vmware-vsphere-client/SerenityDB/serenity/*
    # service-control –start vsphere-client
  • In Windows:
    # cd <C:\Program Files\VMware\vCenter Server\bin>
    # service-control –stop vspherewebclientsvc
  • Delete the contents of the folders below.
    <C:\programdata\vmware\vCenterServer\data\vSphere Web Client\SerenityDB\serenity>
    #service-control –start vspherewebclientsvc

Creating a new virtual disk for an existing Linux virtual machine 

To create a new virtual disk for an existing Linux virtual machine:
  1. Log in as root on your Linux virtual machine.
  2. Run this command and make note of the sdxentries

    ls /dev/sd*

  3. Log in to the vCenter Server using the vSphere Client.
  4. In the vSphere Client inventory, right-click the virtual machine and select Edit Settings.
  5. Click the Hardware tab and click Add.
  6. Select Hard Disk and click Next.
  7. Complete the wizard.
  8. Reboot the Linux virtual machine.
  9. Log in using the root credentials.
  10. Running the command ls /dev/sd* will now return a new entry.
  11. Create an ext3 file system on the new disk using the new sdx from step 10.

    mkfs -t ext3 /dev/sdx

    You may see an alert that you are performing this operation on an entire device, not a partition. That is correct, as you created a single virtual disk of the intended size. This is assuming you have specified the correct device.

    Caution
    : Ensure you have selected the right device, there is no undo.

  12. Run the fdisk command to verify the existence of the disk you created:

    fdisk -l

  13. Run this command to create a mount point for the new disk:

    mkdir / New_Directory_Name

  14. Run this command to display the current /etc/fstab:

    cat /etc/fstab

  15. Using a text editor, edit fstab and add this line to add the disk to /etc/fstab so that it is available across reboots:

    /dev/sdx /New_Directory_Name ext3 defaults 1 3

    Note: Use a Linux text editor of your choice.

  16. Restart the Linux virtual machine and the new disk is now available.