Skip to content
This repository has been archived by the owner on Aug 26, 2021. It is now read-only.

vic_v1.1.1
Compare
Choose a tag to compare
@martin-borisov martin-borisov released this 12 May 14:25
· 1 commit to vic_v1.1 since this release
vic_v1.1.1
f7514f9

Docker hub image: https://hub.docker.com/r/vmware/admiral/ vic_v1.1.1

Resolved Issues

The following issues found in Admiral / vSphere Integrated Containers Management Portal1.1.0 have been fixed in 1.1.1:

  • Cannot move a placement to a different project. #90
    After you create a placement, you cannot move it to a different project, meaning that you cannot assign placements that are created by default when you add a VCH. The value is changed in the dialog, but the change is not applied when you save.
  • Cannot log in to Management tab in vSphere Integrated Containers UI. #91
    After deploying the vSphere Integrated Containers appliance, you can log in to the Registry tab in the vSphere Integrated Containers UI, but you cannot log in to Management tab.

Known Issues

  • VCHs disappear from Admiral UI. #96
    If you add more than 10 VCHs to Admiral, after some time some VCHs disappear from the UI. This issue does not occur with fewer than 10 VCHs. If you have approximately 10 to 20 hosts, the issue might appear. The issue always appears if you have more than 50 VCHs.

  • Time changes in the appliance VM cause vSphere Integrated Containers Management Portal not to function correctly. #77
    If, after deploying the vSphere Integrated Containers appliance, the system clock changes while vSphere Integrated Containers Management Portal is starting, all operations fail with the message Operation already expired, will not queue.

    Workaround: Connect to the vSphere Integrated Containers appliance by using SSH, and run systemctl restart admiral.service to restart the management portal service.

  • Shared data volumes are not supported. #vic/2303
    vSphere Integrated Containers Engine does not support shared data volumes, meaning that multiple containers cannot share a common vSphere volume. As a consequence, using vSphere Integrated Containers Management Portal to provision applications that include containers that share volumes fails when using vSphere Integrated Containers Engine, with the error Server error from portlayer: Failed to lock the file. Do not design or import such templates in vSphere Integrated Containers Management Portal and do not attempt to deploy applications based on such templates when using vSphere Integrated Containers Engine.

Download Binaries

Open-source Admiral project: TBD

Documentation

Open Source Components

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

Assets 2
Loading