Skip to content

vSphere Integrated Containers Appliance v1.4.1
Compare
Choose a tag to compare
@zjs zjs released this 03 Jul 17:49
v1.4.1
ad7eb5f
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's in the Release Notes

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.1-5547-ad7eb5f8.ova

Filesize (vic-v1.4.1-5547-ad7eb5f8.ova) = 3402752000
SHA256 (vic-v1.4.1-5547-ad7eb5f8.ova) = fd8b0dc0fbb555a1e4ff1a29425b3cfdb7260ce95f6e8b41c7ce2bb024112133
SHA1 (vic-v1.4.1-5547-ad7eb5f8.ova) = b579b12a2cc639c797f602713ed7ff9c506a37b7
MD5 (vic-v1.4.1-5547-ad7eb5f8.ova) = ed072929426d16c51ad5363ea449af2a

This OVA contains the following component versions:

--admiral vic_v1.4.1 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1.tar.gz \
--vicmachineserver v1.4.1

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.

Changes

Full list of changes from 1.4.0.

New Features

This release includes the bug fixes and enhancements listed below.

Enhancements

See the enhancements for the following vSphere Integrated Containers components:

Resolved Issues

See the resolved issues for each of the vSphere Integrated Containers components:

Additionally, the following other issues have been addressed:

  • The OVF now uses the VMXNET3 adapter. #1746
    Previously, the E1000 adapter was used.
  • The OVF now uses distinct property keys for registry and management ports. #1642
    Previously, the OVF used similar keys for the registry and management ports causing a collision when deploying via the vSphere H5 client. (Note: please refer to the vSphere documentation for information about which vSphere H5 Client versions support deployment of OVAs.)

Known Issues

With the exception of the resolved issue above, v1.4.1 has the same known issues as v1.4.0.

View all

  • 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 are available in the LICENSE file.

Assets 2
Loading