Skip to content

vSphere Integrated Containers Appliance v1.4.0
Compare
Choose a tag to compare
@andrewtchin andrewtchin released this 08 May 04:16
v1.4.0
f168720
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

What's in the Release Notes

New Features

vSphere Integrated Containers appliance 1.4.0 includes the following new features in this release:

Download Binaries

Installation and Upgrade

IMPORTANT: If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or later. Due to significant changes in the HTML5 vSphere Client in version 6.7 update 1, previous versions of the vSphere Integrated Containers plug-in for the vSphere Client do not work with that version.

Using vSphere Integrated Containers

For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.

Resolved Issues

The following issues that were documented as known issues in previous releases have been fixed in 1.4.0:

  • Tagging the appliance fails when vCenter password contains colon. #1080
    When registering the appliance with the Platform Services Controller, registration fails with the error Failed to locate VIC Appliance. Please check the vCenter Server provided and try again. This problem results from an issue in vSphere 6.5u1, and occurs if the vCenter Single Sign-On password contains a colon (:).
  • vSphere Integrated Containers appliance support bundle does not include Management Portal logs. #225
    Workaround: Download the Management Portal logs manually.

See also the resolved issues sections of the release notes for each of the other vSphere Integrated Containers components:

Known Issues

The following issues affect the vSphere Integrated Containers appliance:

  • The automated upgrade script marks moved disks as independent #1884
    During the automated upgrade process, disks were marked as independent disks, preventing them from being included in future snapshots. This is fixed in vSphere Integrated Containers 1.4.2.

  • Appliance upgrade script does not support FQDN addresses for the old appliance #1731
    When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

  • Using FQDN when generating certificates for dch-photon results in a <nil> certificate. #925
    When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.

    Workaround: Always specify an IP address in the -vic-ip parameter.

  • Appliance services are not available if accessed through NAT or a reverse proxy. #1172
    The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

    Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

  • vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
    If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

    Workaround: Ignore the warnings and click Yes to proceed with the operation.

  • Deploying the OVA with ovftool results in warnings about file size mismatch. #1166
    If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.

    Workaround: Ignore the error message.

See also the known issues for each of the vSphere Integrated Containers components:

Open Source Components

The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers Engine are available in the LICENSE file.

Assets 2
Loading