6.3 Stable Release Notes

8 September 2020

We are happy to introduce OnApp 6.3 (6.3.0-31). This document lists features, improvements, and fixes implemented for all available OnApp components within the 6.3 Edge 1, 6.3 Edge 2, or 6.3. 

Before You Upgrade

You can update to OnApp 6.3 Stable from OnApp 6.2, 6.3 Edge 1, or from 6.3 Edge 2. For details, refer to the Upgrade Guide

Highlights

Here you can find the key features that we deliver as a part of OnApp 6.3. You can also check other features and improvements and see the list of issues that were fixed in OnApp 6.3.

Migration from Xen to KVM (Windows)

Previously it was possible to migrate only Linux-based VSs from Xen to KVM. In 6.3 Edge 1, OnApp introduces the possibility to migrate Windows-based virtual servers from Xen to KVM compute resource. The most time-consuming operations are performed with the virtual server being online, so the required downtime period is as short as possible. 

Edge Accelerator Operator Dashboard

Now you can learn more about your accelerator performance and track the amount of bandwidth used by accelerated websites in the Operator Dashboard menu. The Dashboard also allows you to view bandwidth statistics generated for the last 24 hours or more. 

Sub-allocated IP Pools

Now you can manage your VMware Cloud Edge Gateways easier with the ability to view sub-allocated IP pools. Therefore, your configurations on VMware Cloud side are now more accurately rendered on OnApp side.

Passthrough Host CPU Configuration Model

Passthrough host CPU is one of the CPU model configurations, that allows to group compute resources with similar CPU performance characteristics into compute zones. Passthrough host CPU model configuration passes the host CPU model and features directly to the guest VS. This mode provides the maximum available capabilities of the host's CPU to VS's virtual CPU. 

Updated UI

In OnApp 6.3, we updated the user interface with the new look and feel for all UI components. Among others, now the following UI components match the new layout design: tables, pop-up windows, instance packages card view, steps in wizards, labels, action buttons, and group form components.

Virtual Network Interface support and custom network configuration for Integrated Storage

Added support for virtual network interfaces and the ability to view, create, and edit advanced network interfaces for Integrated Storage compute resources and smart servers. Also, if you have complex network configuration, you can now can configure networks manually to make them compatible with OnApp Integrated Storage. Manual configuration may be performed for network interfaces bonding or one network interface, depending on your environment.

Live log for migrations and transactions

Now users can inspect their transactions in real time. Also for the full migrate and hot full migrate it is possible to watch the migration process in real time.

OVA install method for OnApp Control Panel

OnApp now supplies an official method to install the OnApp Control Panel via OVA, which can speed up how long it takes to install your cloud if you virtualize your control panel on other virtualization platforms. Not only will it install CentOS & OnApp, but also configure networking, MySQL, RabbitMQ and more.


The following table lists all the features, improvements, and fixes included into OnApp 6.3 Stable for all available components. 


Features & Improvements

TypeKeyRelease Notes
OnApp Cloud

Feature

CORE-15996Now you can learn more about your accelerator performance with the bandwidth statistics available at the Operator Dashboard page.

Feature

CORE-15321

Now you can select Network Appliance as operating system and TiMOS as distribution when converting OVA into KVM-based template.

Please, contact your account manager to enable this feature for your cloud.

Feature

CORE-16508Now you can migrate your Windows-based VSs from Xen to KVM compute resources. 

Feature

CORE-16202Now you can select passthrough host CPU configuration model for a compute zone, so that host CPU model and features will pass directly to the guest VS.

Feature

CORE-14397Now you can view, create, and edit advanced network interfaces for compute resources with Integrated Storage and smart servers.

Feature

CORE-14862Now you can use VPN to enhance the security of disaster recovery replication.

Feature

CORE-14396Added support for virtual network interfaces and the ability to view, create, and edit advanced network interfaces for Integrated Storage compute resources and smart servers.

Feature

CORE-16912Updated the scooby version to 0.0.5 for Control Panel servers.

Feature

CORE-16854Updated the OnApp licensing certificates to be compatible with OpenSSL 1.1

Improvement

CORE-12680Now you can restrict users from editing default Integrated Storage datastore cache settings if they don't have the corresponding permission.

Improvement

CORE-14301

Added support for AMD-based KVM CentOS 7 CloudBoot compute resources intended for smart servers deployment.

Improvement

CORE-14935Now you can edit XML configuration for smart servers.

Improvement

CORE-16558Now you can increase the Integrated Storage controller DB size for backup servers to store larger volumes of data.

Improvement

CORE-14470

Now the GRUB version is detected for OVA templates to improve OVA converting and OVA VS provisioning.

Improvement

CORE-14632Now you receive an event notification when auto-backup is postponed.

Improvement

CORE-14976Improved data security with automated disk wiping on source data store after Hot Full migration between LVM data stores.

Improvement

CORE-16372

Now you can restrict users from viewing recovery point size of their own or any VSs if they don't have the corresponding permission.

Improvement

CORE-16571Improved the process of applying Windows licensing type of a parent template group to child groups as well.

Improvement

CORE-15479Removed the popups containing irrelevant information on the Integrated Storage nodes from the IS Disk Details page.

Improvement

CORE-15657Improved disk formatting to avoid errors during VS rebuild.

Improvement

CORE-16124Improved security of data transferring in Federation by creating new routes for passing credentials

Improvement

CORE-16159Now, when you enable DRaaS on a VS with Integrated Storage, the transaction is successful even if multiple IP addresses are associated with this VS.

Improvement

CORE-16175Updated the kernel for shadow VSs with DRaaS functionality to avoid crashes on Xen compute resources with Integrated Storage after update to OnApp 6.0.

Improvement

CORE-16182Now, if connection with a backup server is lost during the VS creation and Build disk transaction fails, the rollback is executed and you may rebuild or destroy the VS.

Improvement

CORE-16270Updated the OnApp service on Control Panel for CentOS 7 compute resources.

Improvement

CORE-16271Updated the onapp-ssh-agent service on Control Panel for CentOS 7 compute resources.

Improvement

CORE-16272Updated the onapp-vnc-proxy service on Control Panel for CentOS 7 compute resources.

Improvement

CORE-16247Now the VNC console window on the VS Overview page is size-consistent for windows-based VSs on both CentOS 6 and CentOS 7 KVM compute resources.

Improvement

CORE-12074Now the SDN Network label contains a clickable link to the IP Nets page.

Improvement

CORE-6162Improved the placement of menu items in the Tools dropdown at the VS Overview page for the VSs in recovery mode.

Improvement

CORE-12390Improved login security by removing the message confirming specific emails in the system at the Password Recovery page.

Improvement

CORE-14976Improved data security with automated disk wiping on source data store after Hot Full migration between LVM data stores.

Improvement

CORE-16437Improved data security with automated disk destruction on source data store after Xen to KVM migration between LVM and IS data stores.

Improvement

CORE-15165

CORE-15166

CORE-14281

Updated the following UI components to match the new layout design: tables, pop-up windows, instance packages card view, and form steps in wizards.

Improvement

CORE-17163Improved logging for hot on Xen and KVM compute resources and hot full migration on KVM compute resources.

Improvement

CORE-5499Now you don't need to have the Update own virtual server and Read own virtual servers permissions enabled to edit firewall rules.

Improvement

CORE-17142Now you can use symbols for the URL signing key used to securely access your CDN resources.

Improvement

CORE-14710Allowed to use IPv6 while filling the info about CDN resource.

Improvement

CORE-14539Added a No IP address found label to the IP Report page in case there are no IP addresses in the IP Report. 

Improvement

CORE-16474Added a measurement unit (minutes) to the Failover timeout field at the Compute Zone Details page.

Improvement

CORE-16774Now the template price is automatically updated after VS migration from Xen to KVM.

Improvement

CORE-16691Now the Backups tab at the User Profile page will not be displayed for users with the Backups permission group disabled.

Improvement

CORE-16899Now you can perform graceful shutdown for a VS built from a load balancer.

Improvement

CORE-16986Now the Log in as feature may also be used if the Global Whitelist is not configured.

Improvement

CORE-15163

CORE-15164

CORE-14831

CORE-16938

CORE-16939

Updated the following UI components to match the new layout design: labels, action buttons, and group form components, such as input labels, radio buttons, sliders, tabs, and others.

Improvement

CORE-14994Now you can assign service add-ons or recipes to your virtual server using Service Addons or Recipes sub-tabs, which became available in the Add-ons step.

Improvement

CORE-17045Added a rake task to convert the Control Panel DB tables fields of TIME, TIMESTAMP or DATETIME type during upgrade as required after database update to MariaDB v.10.4.

vCenter & vCloud


Feature

CORE-16394Implemented the Infrastructure mode for vCenter in Beta VS Creation wizard to enhance security and reduce time of vCenter VS deployment.

Improvement

CORE-17447Added support the newer vCloud API version 34.

Improvement

CORE-16401Now you can set more virtual memory or CPU resources for vCD resource pools than is physically available in the system.

Improvement

CORE-13057Now you can edit the values of all the VS resources available in the vApp creation wizard.

Improvement

CORE-16382Now you can convert Edge Gateways to Advanced Edge Gateways to successfully use NSX regardless of your vCloud version.

Improvement

CORE-15621Now in case of a network connectivity issue with NSX Edge, the warning message is displayed at the top of the screen and it includes the failure reason.

Improvement

CORE-15640Now you can manually import multiple vCenter VSs to OnApp at once.

Improvement

CORE-15814Now you can add, delete, and increase size of vCenter or OVA disks without the VS reboot.

Improvement

CORE-16330Improved IP address validation process to avoid errors when working with NSX NAT rules.

Improvement

CORE-16359Added confirmation pop-up window after clicking vApp power off/on buttons.

Improvement

CORE-16395Now you can set limits and calculate price for vCPUs for vCloud organizations.

Improvement

CORE-16400Now the resource pool CPU and RAM usage are more frequently updated and synced with vCloud to ensure more efficient resource management.

Improvement

CORE-16404Added a notification to update your out-of-sync vCloud credentials, if the vCD password was changed on vCloud side.

Improvement

CORE-16550Now you can skip verification of self-signed certificates with tls enabled but still have secure notifications delivery.

Improvement

CORE-16730As a vCloud user you can now assign SSH keys to your vCloud VSs from the VS Tools menu.

Improvement

CORE-16734Now you can add to a VS secondary disks larger than 2TB with limited support.

Improvement

CORE-11769Now you can only select files of the corresponding format when uploading OVAs or OVFs from your file system to vCD Catalog.

Improvement

CORE-16015Improved resyncing process so that the hostname of the controller is not overwritten when you resync NSX manager after importing to OnApp.

Improvement

CORE-15935Removed the redundant last_seen_event parameter from the NSX Manager API output.

Improvement

CORE-11622Now only enabled data stores are available for selection at the Resources step of the vCenter VS Creation wizard.

Improvement

CORE-16205Now you can view sub-allocated IP pools for your Edge Gateway at the Edge Gateway Details page.

Improvement

CORE-9398Added the search field to the Resource Pools page.

Improvement

CORE-16380Now you can enable the Reboot Virtual Server option while adding a disk to a Linux-based OVA and vCenter VS.

Improvement

CORE-16390Added validation of the hostname length (15 characters maximum) for Windows VS's on vCenter, Xen, and KVM compute resources.

Improvement

CORE-16886Improved the password reset procedure on Windows-based VSs running on vCenter or static compute resources.

Improvement

CORE-16243Improved logging for vCenter by adding logs for configuration transactions that run on Windows- and Linux-based vCenter VSs.

Improvement

CORE-16867Added the ability to log what is going on during the transaction running for vCenter VS.

Improvement

CORE-16791Changed the mode levels of the vcloud_rest logs: the INFO level is used for production, while DEBUG is used for staging and development.

Installer

Feature

INSTALLER-525Introduced new RPM packages for onappstoretests and test-suite.

Improvement

INSTALLER-522Built MariaDB version 10.1.38 binaries to grep mysqldump.

Improvement

INSTALLER-454Disabled the 0023-RHEL-7-v2v-Disable-the-virt-v2v-in-place-option.patch patch as required for Xen to KVM migration of Windows-based VSs.

Improvement

INSTALLER-473Switched onapp-vnc-proxy.service to systemd service unit for RHEL/CentOS 7 compute resources.

Improvement

INSTALLER-474Switched onapp-ssh-agent service to systemd service unit for RHEL/CentOS 7 compute resources.

Improvement

INSTALLER-475Switched OnApp engine service to systemd service unit for RHEL/CentOS 7 compute resources.

Improvement

INSTALLER-479Added timeout value for InnoDB transaction waiting for a raw lock, and set the value to 50 seconds by default.

Improvement

INSTALLER-488Added the libguestfs-winsupport, virtio-win, and virt-v2v utilities to CentOS 7 backup servers on static compute resource required for Xen to KVM migration on Windows.

Improvement

INSTALLER-490Updated the version of MariaDB to 10.4 for Control Panels on CentOS 7 compute resources. 

Improvement

INSTALLER-491Improved the databases migration to upgrade the Control Panels on CentOS 7 compute resources to the updated version of MariaDB. 

Improvement

INSTALLER-493Now you can migrate database of Control Panel running on CentOS 6 compute resources from MySQL stock v.5.1 to MariaDB v.10.4

Improvement

INSTALLER-500Provided ability to migrate database migration utility to MariaDB 10.4.

Improvement

INSTALLER-502Updated the python version to 3.8.1 for compute resources and controllers based on CentOS 7 Xen, CentOS 7 KVM, and CentOS 6 KVM.

Improvement

INSTALLER-508Added support of GRUB2 Boot Loader Specification feature on CentOS 6 and CentOS 7 KVM compute resources.

Improvement

INSTALLER-510Added the HttpOnly and Secure flags to Apache HTTPS response header.

Improvement

INSTALLER-511

Removed EULA from the Control Panel installer.

Improvement

INSTALLER-515

Configured usable SSL and TLS protocol versions and Cipher Suite available for negotiation in SSL handshake.

Improvement

INSTALLER-520

Improved Integrated Storage on static compute resources startup by installing iperf.

Improvement

INSTALLER-521

Improved the onapp-cp-config service: provided ability to read VMware guest info and, based on this information, configure networking for a VS: IP addresses, mask, gateway, nameservers, and FQDN.


CloudBoot

Feature

CLOUDBOOT-630Updated the python version to 3.8.1 for Integrated Storage and storageAPI on CentOS 7 Xen, CentOS 7 KVM, and CentOS 6 KVM.

Improvement

CLOUDBOOT-587Added the following components for CentOS 7 KVM ramdisk required for Xen to KVM migration of Windows guests:
  • libguestfs-winsupport
  • virtio-win
  • Virt-v2v
  • unzip
  • OVMF

Improvement

CLOUDBOOT-593

Updated the following components for CentOS 7 Xen ramdisk:

  • A kernel version to 4.9.215-36.el7.x86_64 
  • A UFS filesystem driver sources version based on a kernel version 4.9.215-36.el7.x86_64 compelled with super-ufs_fs_write.patch patch
  • A wireguard sources version to 0.0.20190702 based on a kernel version 4.9.215-36.el7.x86_64 

Improvement

CLOUDBOOT-594

Updated the following components for CentOS 6 Xen ramdisk:

  • A kernel version to 4.9.215-36.el6.x86_64 
  • A UFS filesystem driver sources version based on a kernel version 4.9.215-36.el6.x86_64 compelled with super-ufs_fs_write.patch patch
  • A wireguard sources version to 0.0.20190702 based on a kernel version 4.9.215-36.el6.x86_64 

Improvement

CLOUDBOOT-617

Updated the following components for CentOS v.7.8.2003 KVM ramdisk:

  • A libvirt version to 4.5.0-33.el7
  • A qemu-kvm-ev version to 2.12.0-44.1.el7_8.1

Improvement

CLOUDBOOT-618Updated the Xen version for CentOS 7 Xen ramdisk to 4.10.4.42.g24d62e1262-1.el7 to address the following issues: XSA-318/CVE-2020-11742, XSA-316/CVE-2020-11743, XSA-314/CVE-2020-11739, XSA-313/CVE-2020-11740, and CVE-2020-11741.

Improvement

CLOUDBOOT-619

Updated the following components for CentOS 6 KVM ramdisk:

  • A kernel version to 2.6.32-754.29.1.el6.x86_64 to address the CVE-2019-17666RedHat 1485759 and 1775226 issues
  • A qemu-kvm version to 0.12.1.2-2.506.el6_10.7  compiled with --enable-io-throttling to addres RedHat bz#1791680 and bz#1798966 issues

Improvement

CLOUDBOOT-620

Updated the following components for CentOS 7 KVM ramdisk:

  • A CentOS version to 7.8.2003
  • A kernel version to 3.10.0-1127.el7.x86_64 to address the CVE-2019-14901 issue
  • An XFS filesystem driver sources version to 3.10.0-327.36.3.el7.x86_64 based on a kernel version 3.10.0-1127.el7.x86_64 compiled with the following patches:
    • xfs-make-xfs_bmbt_to_iomap-available-outside-of-xfs_.patch
    • iomap-Switch-from-blkno-to-disk-offset.patch
    • dax-give-DAX-clearing-code-correct-bdev.patch
    • xfs_posix_acl_valid.patch
  • A UFS filesystem driver sources version based on a kernel version 3.10.0-1127.el7.x86_64 compelled with R/W support patch
  • A wireguard kernel module version to 1.0.20200426
  • A wireguard-tools version to 1.0.20200319

Improvement

CLOUDBOOT-627

Updated the following components for CentOS 7 KVM ramdisk:

  • A CentOS version to 7.8.2003
  • A wireguard kernel module version to 1.0.20200426
  • A wireguard-tools version to 1.0.20200319

Improvement

CLOUDBOOT-632

Updated the following components for CentOS 7 KVM ramdisk:

  • CentOS version to 7.8.2003
  • kernel version to 3.10.0-1127.10.1.el7.x86_64 to address the CVE-2020-10711 issue
  • An XFS filesystem driver sources version to 3.10.0-327.36.3.el7.x86_64 based on a kernel version 3.10.0-1127.10.1.el7.x86_64 compiled with the following patches:
    • xfs-make-xfs_bmbt_to_iomap-available-outside-of-xfs_.patch
    • iomap-Switch-from-blkno-to-disk-offset.patch
    • dax-give-DAX-clearing-code-correct-bdev.patch
  • UFS filesystem driver sources version based on a kernel version 3.10.0-1127.10.1.el7.x86_64 compelled with R/W support patch
  • A libvirt version to 4.5.0-33.el7_8.1 to address the rhbz#1816035 issue

Improvement

CLOUDBOOT-638Updated the kernel version for CentOS 6 KVM ramdisk to 2.6.32-754.30.2.el6.x86_64 to address the CVE-2017-12192, CVE-2020-10711, and the CVE-2020-0543 issue.

Improvement

CLOUDBOOT-640

Updated the following components for CentOS 7 Xen ramdisk:

  • kernel version to 4.9.221-37.el7.x86_64 to address the XSA-316/CVE-2020-11743 issue
  • UFS filesystem driver sources version based on a kernel version 4.9.221-37.el7.x86_64 compelled with the super-ufs_fs_write.patch patch
  • A xen version to 4.10.4.36.g6cb1cb9c63-1.el7 to address the XSA-320/CVE-2020-0543 issue
  • wireguard kernel module version to 1.0.20200426.1 based on a kernel version 4.9.221-37.el7.x86_64

Improvement

CLOUDBOOT-646Added support of GRUB2 Boot Loader Specification feature on CentOS 6 and CentOS 7 KVM compute resources.

Improvement

CLOUDBOOT-653Updated OnApp Storage with the onappstore-6.3-8096-master.x86_64.rpm ramdisk images for CloudBoot 6.3 Stable.

Improvement

CLOUDBOOT-654Updated the kernel version for CentOS 6 KVM ramdisk to 2.6.32-754.31.1.el6.x86_64 to address the CVE-2017-12192, CVE-2020-10711, and the CVE-2020-0543 issues.

Improvement

CLOUDBOOT-655

Updated the following components for CentOS 7 Xen ramdisk:

  • kernel version to 4.9.230-37.el7.x86_64
  • UFS filesystem driver sources version based on a kernel version 4.9.230-37.el7.x86_64 compelled with the super-ufs_fs_write.patch patch
  • A Xen version to 4.10.4.75.g93be943e7d-1.el7 to address the XSA-317, XSA-319, XSA-321, XSA-327, and the XSA-328 issues
  • wireguard kernel module version to 1.0.20200729 based on a kernel version 4.9.230-37.el7.x86_64

Improvement

CLOUDBOOT-656

Updated the following components for CentOS 7 KVM ramdisk:

  • CentOS version to 7.8.2003
  • kernel version to 3.10.0-1127.18.2.el7.x86_64 to address the CVE-2019-19527, CVE-2020-10757, CVE-2020-12653, CVE-2020-12654, and the CVE-2020-10713 issues
  • An XFS filesystem driver sources version to 3.10.0-327.36.3.el7.x86_64 based on a kernel version 3.10.0-1127.18.2.el7.x86_64 compiled with the following patches:
    • xfs-make-xfs_bmbt_to_iomap-available-outside-of-xfs_.patch
    • iomap-Switch-from-blkno-to-disk-offset.patch
    • dax-give-DAX-clearing-code-correct-bdev.patch
  • UFS filesystem driver sources version based on a kernel version 3.10.0-1127.18.2.el7.x86_64 compelled with R/W support patch
  • wireguard kernel module version to 1.0.20200729 based on a kernel version 3.10.0-1127.18.2.el7

Integrated Storage

Improvement

STORAGE-2164

Improved SAN networks setup management and provided the ability to configure networks manually to make them compatible with OnApp Integrated Storage.

Improvement

STORAGE-2134Improving virtualization detection algoritm for backup servers with Intgerated Storage.

Improvement

STORAGE-2186Added possibility to edit SAN Controller updateconfig command on all compute resources in a single compute zone.

Improvement

STORAGE-2187Improved the node selection algorithm for disk creation and now the best nodes are selected for vDisk redundancy after the score calculation.

Improvement

STORAGE-2227Reduced Integrated Storage installation size and build time by removing the thttpd service and binary from the Integrated Storage rpm.

Improvement

STORAGE-2228Added bios names support for network devices for static compute resources with Integrated Storage.

Improvement

STORAGE-2235Added bios names support for network devices for static backup servers with Integrated Storage.

Improvement

STORAGE-2084Improved the API and command line output for the Enforce redundancy request by providing more details and indicating cause of the issue.  

Improvement

STORAGE-2197Updated the python version to 3.8.1 for compute resources and controllers based on CentOS 7 Xen, CentOS 7 KVM, and CentOS 6 KVM.


Fixes

TypeKeyRelease NotesAffected Versions

CORE-1480

If you created a template from a VS disk backup and did not add it to a template store, it was charged incorrectly. 

3.1 - 6.2

CORE-4816You could not create a VS without the See all templates permission enabled.3.0 - 6.3 Edge 1

CORE-7165Users with a default set of permissions and enabled See list of all compute zones permission could not see any compute zones. 4.3 - 6.2

CORE-8708

At the Compute Zone Failover Details page, the failover section was cropped and the Tools button was displayed incorrectly.

5.4

CORE-9057

The Clear button in the Advanced Options section at the Global Search page overlapped the selected options in the box. 

5.4 - 6.1

CORE-9282

The non-public networks were displayed in the dropdown list while creating an application server at the Add New Application Server page.

6.0 Patch 8

CORE-11434The CopyOVA option for not displayed at the VS Properties page for a vCenter OVA VS.5.7 - 6.3 Edge 1

CORE-12448The 500 Internal Server Error appeared on the Dashboard if you typed "users" in the search box and clicked the search button. 5.10 - 6.2

CORE-12557The network interface number was displayed incorrectly on the Resources step of the VS Creation wizard.5.10 - 6.2

CORE-12657The Cores per Socket label at the Adjust Resource Allocation page was not displayed correctly.6.0 - 6.2

CORE-12714The redundant Port Speed column was displayed at the Network Interfaces page for vCloud VSs.6.0

CORE-12724If you tried to create a VS via API with port speed that exceeded the limit set in your bucket, the error message that appeared was misleading.6.0 - 6.3 Edge 1

CORE-12805Users without the Update Yubikey permission could still use the Manage YubiKeys button of other users at the User Details page.6.0

CORE-12821The Purge all button at the Purge page was named incorrectly as it purged content only for a specified site.5.5 - 6.3 Edge 1

CORE-12858The redundant search box was displayed at the Users with Config Problems page. 6.0 - 6.2

CORE-13323The irrelevant API URL field label was displayed in the Add New Compute Resource form instead of the IP Address/Hostname label.6.0 Patch 2 - 6.3 Edge 1

CORE-13325The irrelevant IP Address field label was displayed at the vCloud compute resource Details page instead of the API URL label.6.0 Patch 2 - 6.3 Edge 1

CORE-13478If you tried to import a vCenter VS to OnApp but did not specify the VS name and clicked Submit, import failed though no error message appeared.6.1 - 6.3 Edge 1

CORE-13526If you tried to add a VS disk to a vCenter VS using invalid service credentials, in spite of the error shown in the OnApp interface, the disk was successfully added in vSphere.6.0 - 6.3 Edge 1

CORE-13567Icons for vCenter CentOS 6 templates were missing in the VS Creation wizard. 6.0 - 6.2

CORE-13591It was impossible to delete a CloudBoot compute although the transaction was displayed as executed successfully at the Logs menu.4.0 - 6.0

CORE-13629When you tried to add step to a recipe and tried to select some value from the On Failure dropdown menu of the Add step to recipe form, the scrollbar dissapeared from the menu.6.1 Edge 1 - 6.2

CORE-13980Sometimes, if you deleted five or more vCenter VSs, the transactions displayed as failed even though the VSs were deleted.6.0 Patch 4 - 6.2

CORE-14168When you cliked the Cancel button at the Import vCenter Virtual Server page, the page refreshed instead of returning to the previous page.6.0 - 6.3 Edge 1

CORE-14192If you tried to create a vCenter VS, specifying only a network cluster at the Resources step of the VS Creation wizard, the transaction failed.6.0 Patch 6 - 6.3 Edge 1

CORE-14168When you cliked the Cancel button at the Import vCenter Virtual Server page, the page refreshed instead of returning to the previous page.6.0 - 6.3 Edge 1

CORE-14369If you have created a VS with an encrypted password and cloned this VS, the password for the cloned VS was shown incorrectly in the Overview tab.6.1 Edge 1

CORE-14408If you set password longer than 14 symbols during creation of a vCenter Windows-based VS, the VS creation failed.6.0 - 6.3 Edge 1

CORE-14427The virtual servers created in vCenter contained unlimited port speed regardless of the speed value set by the user.6.0 Patch 6- 6.3 Edge 1

CORE-14520If your password was expired, after entering the password, you have seen Password expired page without the ability to get back on the Login screen.6.0 - 6.3 Edge 1

CORE-14524Sometimes, if you ran several backups on a compute resource, the transactions failed. 6.0 Patch 6 - 6.2

CORE-14575If you tried to boot some KVM VS from ISO with a long name, the label of the ISO was cropped in the dropdown of the Boot from ISO popup window.6.1 Edge 1 - 6.3 Edge 1

CORE-14588The label of a server with more than 23 symbols name has been truncated with three dots, although there was enough space to display it completely.6.0 Patch 6 - 6.3 Edge 1

CORE-14612When you started building two Windows-based vCenter VSs and removed some other vCenter VSs from your Control Panel, one of the building transactions failed.6.1 Edge 1 - 6.3 Edge 1

CORE-14614Rarely, when you tried to create a Windows-based vCenter VS, the transaction failed. 6.0 Patch 7 - 6.3 Edge 1

CORE-14767When you created a VS with the long FQDN, it was cropped at the VS Overview page.6.1 Edge 2

CORE-14785After you selected the number of items to filter records at the Schedule Log page, you could not switch between the pages using the pagination buttons.6.0 - 6.1

CORE-14786When clicking, the pagination button borders were missing at the Virtual Servers and Users pages.6.1 Edge 2 - 6.2 Edge 2

CORE-14816The Operating System Type label was aligned incorrectly at the Compute Resource Details page.6.1 Edge 2 - 6.2 Edge 2

CORE-14852It was possible to assign a disk to an OVA and ISO virtual servers, even though the VS rebuild after assigning disk still failed. 6.0 - 6.1 

CORE-14865If you tried to clone a virtual server, you might see a message in the pop-up filed that you have filled correct VS password and password confirmation, even if VS root/admin password and password confirmation were incorrect.6.1 - 6.3 Edge 1

CORE-14866You might see an inaccurate message in the Add IP Address pop-up window trying to add an IP address to a vCenter VS.6.0 Patch 7 - 6.3 Edge 1

CORE-14867When you tried to add IP to Windows VS and filled in the initial root password with a valid password, you might see an inaccurate message in Add IP Address pop-up window.6.1 - 6.3 Edge 1

CORE-14899At the VS properties page, the highcharts indicating the usage of memory and CPU(s) did not disappear after taking the mouse cursor away.6.1 Edge 2

CORE-14903When you tried to edit limits for your Instance Package in the Access Control section of your bucket, the buttons in the appearing popup were displayed incorrectly.6.1 Edge 2 - 6.2 Edge 2

CORE-14906Some UI frames were distorted when you tried to zoom out the VS Overview page.6.1 Edge 2

CORE-14915Migration to from VMware to KVM failed for vCenter Linux-based VSs with three or more disks.6.1 Edge 2 - 6.2

CORE-14930If creation of an OVA vCenter VS failed, there was no option to rebuild this VS in the Tools menu at the VS Details page.6.1 Edge 2 - 6.2

CORE-14932The 500 Internal Server Error appeared at the Service Add-on Store page if you tried to create an empty service add-on.6.0 Patch 8 - 6.1 Edge 2

CORE-15043The redundant Notifications navigation bar item was displayed in breadcrumbs at the Events page and did not respond to clicking. 6.1 - 6.2

CORE-15160After you rebooted a load balancer of a cluster type, some of the firewall rules on the associated compute resource disappeared untilyou rebooted a VS node. 6.0 - 6.3 Edge 2

CORE-15184The 500 Internal Server Error appeared at the Access Controls page if you tried to edit a non-existent CDN bandwidth limit. 6.0 - 6.2

CORE-15284At the Acceleration reporting page, the measurement unit in the acceleration reporting chart on the Y-axis was not represented.6.1 - 6.2 Edge 1

CORE-15290Sometimes, vCenter VS creation could fail if it was based on the OVA template with the NVRAM file.6.0 Patch 8 - 6.3 Edge 1

CORE-15292If you set the end date sooner than the start day at the Acceleration Reportig page, the error message was misleading.6.0 Patch 8 - 6.3 Edge 1
CORE-15320The option Rebuild Virtual Server was available for vCenter VSs in Tools menu at the VS Properties page even if the initial root password and service credentials were not set.6.0 Patch 8 - 6.3 Edge 1
CORE-15395Instead of Update Firewall Rule, there was a wrong section header at the Update rule page.6.0 Patch 8 - 6.2 Edge 1

CORE-15414After hovering over the Instance Package VSs infobox at the Edit Compute Zone page the mouse cursor was displayed as a pointer.6.0 Patch 8 - 6.2 Edge 1

CORE-15419When you tried to suspend a CDN resource at the CDN Resource Details page, the transaction was successful but resulted in incorrect message in the infobox section.6.1 - 6.2

CORE-15420When you tried to create an Edge/Storage server, the Cancel button was only pertly clickable at the Cloud Locations step of the VS creation wizard.6.1 - 6.2 Edge 1

CORE-15423The pagination config at the Virtual Servers page was automatically applied to Compute Resources page.6.0 Patch 8

CORE-15428When you tried to indicate the certificates you have and their expiration date at add a zone to Federation step, the tooltips on Prev and Next buttons in datetime pickers did not hide after a click and a mouseout event.6.1 - 6.3 Edge 1

CORE-15440Converting imported OVA archive into template failed if the OVA file had several disks of non VMDK format.6.0 Patch 8 - 6.1

CORE-15442If you had insufficient resources to create a VS from a default template in the VS Creation wizard, it was still possible to proceed to the final step with the default template selected.6.1 - 6.2

CORE-15488If you had two or more vCenter compute resources, data stores from one compute resource were displayed for another compute resource at the Data Stores for Compute Resource page.6.1 - 6.3 Edge 1

CORE-15458The Remove and Modify buttons were not aligned to the center in the Assign IP Address popup window at the Network Details page.6.2 Edge 1

CORE-15526The 500 Internal Server Error appeared if you did not select any template at the Templates step of the VS Creation wizard and clicked Next.6.0 Patch 8 - 6.3 Edge 1

CORE-15584If you opened any of NSX pop-up windows and a notification appears, it was not visible because of dark background.6.2

CORE-15588After you configured the value of start day at the Usage Statistics page, it was impossible to edit.6.2 Edge 1

CORE-15606If there were >800 VSs on vCenter side and you tried to import a VS to OnApp, the Import Virtual Server page loaded about 3 minutes.6.0 - 6.3 Edge 1

CORE-15608The Shut down VS button at the Virtual Servers page did not respond to clicking.6.1 - 6.2

CORE-15617The password validation didn't work properly in the Set Password pop-up window as you tried to set root password for a vCenter VS.6.0 Patch 8 - 6.3 Edge 1

CORE-15622When you tried to import to OnApp a great number of vCenter VSs simultaneously, the transaction failed with the system error.6.1 Patch 1

CORE-15675After you applied both Hide Successful Market Notifications and any status filter in the Logs section at the Dashboard page, the Logs menu display was distorted.6.1 Patch 1 - 6.2 Edge 1

CORE-15681When you set the value of end date less than the start date value at the Backups page, the view of the page was distorted.6.1 Patch 1 - 6.2 Edge 1

CORE-15690The breadcrumbs was missing at the Usage Trends page.6.1 Patch 1 - 6.2 Edge 1

CORE-15705When you deployed a VS from Windows template with a service add-on assigned, the templates and VSs were displayed in one list at the Service Add-ons Applied to Virtual Servers page.6.2 Edge 2

CORE-15706Long labels of system service add-ons and VSs associated with them were displayed truncated at the SPLA Report and System Service Add-ons Report pages.6.2 Edge 1

CORE-15729Instance Package label was not displayed in the breadcrumb area at the Instance Package Details page.6.0 - 6.2 Edge 1

CORE-15782When user was trying to edit pricing for the Template Group in the bucket, the corresponding popup for editing exceeded the size of the Bucket page area.6.0 Patch 9

CORE-15795After you added federated compute resource group to the cloud with CloudBoot compute resources at the Buyer side, CloudBoot compute resource was updated on the Seller side instead.6.1

CORE-15808There was no confirmation box for rebooting the VS after ticking Virtual VPU hot add or Memory hot add checkboxes at the Edit Virtual Server page.6.0 Patch 7

CORE-15865If you tried to create a template with no lable at the Template Store page, the template was not created though no error message appeared.6.0 Patch 8 - 6.3 Edge 1

CORE-15918When you zoomed in or out any page with tables using the Google Chrome browser, the table borders disappeared.6.2 - 6.3 Edge 1

CORE-15924The Disable customization after run slider at the Confirmation step of the vApp deploy wizard did not initiate the Disable Guest Customization transaction after vApp deployment.6.1 Patch 1 - 6.3 Edge 1

CORE-15925Both virtual servers in Powered on and Powered off status were displayed in the same color at the Virtual Servers page.6.2 Edge 1

CORE-15938When you set the value of end date less than the start date value at the Backups page, it was impossible to edit these values without refreshing the page.6.2 Edge 1 - 6.2 Edge 2

CORE-15940Once you accessed the Activity Log or Failed Actions tabs at the Sysadmin Tools page, the breadcrumbs disappeared and you could not return to the main page.6.2 Edge 1 - 6.2 Edge 2

CORE-15997As you hovered over the ? sign at the Role Details page in Firefox browser, the tooltip didn't appear.6.1 - 6.3 Edge 1

CORE-16014OnApp admin with Any action on last access log permission enabled couldn't view the last access log of other users.6.1 - 6.2

CORE-16028The VS hot migrate, VS hot full migrate, and VS failover recipe events were displayed for vCenter and vCloud VSs at the Recipes page though irrelevant.6.1 - 6.3 Edge 1

CORE-16036It was possible to remove via API NSX Load Balancer Application rule, Application Profile, or Pool that was in use.6.2

CORE-16046As you hovered over the label of an OVA-based VS at the VS Details page, the label text disappeared.

6.2

CORE-16067When you enabled rate limits for an edge gateway, both incoming and outgoing rate limits were set to invalid 0.00 value.6.1

CORE-16080Sometimes, if you edited prices at the Rate Card tab, the 500 Internal Server Error appeared.6.2

CORE-16111When you tried to add VS via API and set template backup_server_id parameter to null, the location_group_id parameter was set incorrectly.6.0 Patch 8

CORE-16122When hovering over the password field at the VS Details page, the password label was blinking.6.2 Edge 2

CORE-16142When you entered some invalid information during an Organization Network creation, all the inserted data was reset and you had to fill it in again.6.1

CORE-16162The 500 Internal Server Error appeared when you tried to create a vCenter VS with instance package.6.2 Edge 1 - 6.2 Edge 2

CORE-16179When editing service add-ons, it was possible to change the type of service add-on from User type to System type and vice versa.

6.2

CORE-16190It was impossible to reboot or shutdown Storage or Edge servers from the Edge Accelerators menu although you could do it via API.6.2

CORE-16197The redundant Restore Infoboxes button was displayed at the Edit user page.6.0 Patch 8 - 6.2 Edge 2

CORE-16209When you tried to filter firewall or NAT rules for NSX edge gateway and then disable filter, the Save button was disabled instead.6.2

CORE-16218After you deployed a vCenter VS from Windows or OVA template and tried to edit its time zone, the ResizeVirtualServer transaction was triggered.6.0 Patch 8 - 6.2

CORE-16219After you upgraded to OnApp 6.1 and tried to create a federated VS, the transaction failed with NoMethod Error.6.1

CORE-16221When you tried to edit NSX edge gateway in one tab and switch to another tab, your changes were lost and you did not receive any warning about that.6.2 Edge 2

CORE-16225If you hovered over a recipe at the Recipes step of the VS Creation wizard, the Uncaught Type Error appeared in web console.6.2 - 6.3 Edge 1

CORE-16226When you tried to create a new ISO via API and set the allowed_hot_migrate parameter to true, the ISO was created with this parameter set to false.6.2 Edge 2

CORE-16229If you manually typed an IPv6 into the filtering field, you did not get a particular IP from the pool without scrolling and searching it in the pool down menu.6.0 Patch 8 - 6.3 Edge 1

CORE-16232It was possible to select an end date that was less than the start date for IP usage at the IP Report page.6.2 Edge 2

CORE-16233When you tried to deploy a vCloud vApp, Disable guest customization label was cropped at the Confirmation step of the creation wizard6.2

CORE-16255During adding new NSX Edge resources to the Access Control section in a bucket not only edge gateways but also isolated networks were available for selection.6.2

CORE-16259If OnApp admin created White List for a user, the admin could not log in as this user if one's IP was not on the user's White List.4.3 - 6.2

CORE-16260It was possible to start a recipe execution on a vCenter VS from the Assigned Recipes page without service credentials set.6.0 - 6.3 Edge 1

CORE-16261An option to enable autoscaling for a VS was available at the Autoscaling page before the VS was built even though the transaction failed.6.0 - 6.3 Edge 1

CORE-16265The irrelevant Delete button was displayed at the Network Interfaces tab at the Edge Accelerator Details page.6.0 Patch 8 - 6.2 Edge 2 

CORE-16266When you tried to create a VS with several network interfaces, the footer overlapped information about one of the network interfaces at the Confirmation step of the creation wizard.6.2 Edge 2 

CORE-16267When you tried to create a vCenter VS, incorrect template image was displayed at the Confirmation step of the VS creation wizard.6.2 Edge 2 

CORE-16273A non-advanced Edge Gateway page was available before the Create Edge Gateway transaction finished.

6.2

CORE-16277It was possible to create NSX routed network without any edge gateway, but the transaction failed with an error.6.2 Edge 2 

CORE-16282When you tried to edit notifications from the Compute Zones page, the 500 Internal Server Error appeared.6.1 - 6.2 Edge 2 

CORE-16283After you configured an end time for a new notification in Federation compute zone at the Compute Zones page, the dates in the datepicker were disabled.6.2 Edge 2

CORE-16284If you set Now as a start date for the period filter and then changed the start date at the Usage Trends page, the VS Details page with distorted layout appeared below the graphs.6.2 - 6.3 Edge 1

CORE-16285If you selected a vCenter template on the Templates step of the VS Creation wizard, chose a data store at the Resources step, and then edited the RAM value, the Data Store dropbox became empty.6.2

CORE-16292When you wanted to create a VS, the icons for the vCenter Windows templates were not displayed at the Templates step of the VS creation wizard.6.2 Edge 2

CORE-16293After upgrade to 6.1, the CPU limit you set in a resource pool was ignored during vApp deployment at the vApps page.6.1 - 6.2

CORE-16297If you enabled normal backup for a VS, and then removed a previously set backup scheudule, the Take Backup transaction failed. 6.0 - 6.3 Edge 2

CORE-16308Breadcrumbs at the Application Errors and IP Report pages were not displayed correctly.6.2

CORE-16309When you tried to compose a vApp from an existing vApp, the transaction failed with a system error and the created vApp was blank.6.2

CORE-16310After you created a vApp with two data stores and one vCloud VS that you tried to edit disk for, you could see all data stores even those not allowed by bucket. When you selected that datastore, the error appeared.6.1 Edge 2 - 6.2

CORE-16311When you tried to add compute zone to Federation, the Private checkbox and Description fields shifted.6.1 - 6.2 Edge 2

CORE-16318Down arrows in the dropboxes were aligned incorrectly at the Firewall Rules page.6.2 Edge 2

CORE-16322After you moved a VS between two compute zones with different price configuration, the price for the VS was not updated at the VS Overview page as expected.6.1 - 6.2

CORE-16327When you clicked the Power off button for a mixed vApp at the vApps page, the powered on VSs of this vApp were not powered off.6.2

CORE-16331System error appeared at the Logs page after you created a VS and then deleted its primary and swap disk.6.0 Patch 8 - 6.2 Edge 2

CORE-16332Notification item counter was displayed incorrectly in Chrome and Safari browsers.6.2

CORE-16333When you unassigned an IP address from a vCenter Windows-based VS, the VS hostname changed to a random value.6.2

CORE-16335After you subscribed to a compute zone in Federation, installed a template for the VS creation and tried to update it, the transaction failed.6.1 - 6.2

CORE-16337After you subscribed to a compute zone in Federation, the statistics for buyer's VSs was not gathered and displayed at the Dashboard.6.2

CORE-16338After you edited FQDN value for a Windows-based VS, it was impossible to start the VS.6.0 - 6.2

CORE-16339The 500 Internal Server Error appeared in logs as you tried to take backup of all disks via API request.6.2

CORE-16341When you tried to migrate a VS with swap disk enabled from Xen to KVM compute resource, the transaction failed.6.2

CORE-16343

When you tried to create a CloudBoot compute resource and selected static IP address from the CloudBoot IP pool, the transaction failed due to the kernel panic error.

6.1 - 6.2
CORE-16346

If you hot migrated a Windows-based VS, the migration price was not calculated as the corresponding transaction failed.

6.2 - 6.3 Edge1

CORE-16356If the VS and Accelerator owners were different, and you tried to acceelerate the VS at the Edge Accelerator Dashboard page, the transaction failed.6.2

CORE-16373After you increased a disk size for a vCenter VS and saved changes, the VS was restarted.6.2

CORE-16374When you tried to add a disk to a vCenter VS, both available and unavailable data stores were displayed in the Data Store dropbox at the Add New Disk page.6.2

CORE-16375Sometimes, if you tried to remove a disk from a powered-off Linux-based vCenter VS, the transaction failed.6.0 Patch 9 - 6.3 Edge 1

CORE-16381You received redundant %{msg} item in notification message displayed at the VS Overview page after powering on the VS.6.2 Patch 1

CORE-16392Notification panels were located incorrectly at the Virtual Server Details page.6.2 Edge 2

CORE-16396VS statistics on the CPU usage was displayed in cores instead of percentages at the Dashboard page.6.2

CORE-16403After you updated the power status of the VS and closed the corresponding notification message, it appeared again at the very next page that you accessed.6.2

CORE-16421If a user had the entire Buckets permission set disabled, it was impossible to reset user password and edit user details.6.2 - 6.3 Edge 1

CORE-16424When you tried to create a new vApp, the labels were cropped in the Password Reset section at the Guest Customization step of the creation wizard.6.2

CORE-16430When you tried to import vCenter without NSX manager into Control Panel, the transaction failed6.2

CORE-16435When you tried to edit the Color field at the Edit Theme page, you couldn't select the color as color picker was overlapped by other fields on the page.6.2

CORE-16442Measurement unit for the Failover timeout field was missing at the Edit Compute Zone page.6.2 - 6.2 Edge 2

CORE-16445When the popups for limits configuration exceeded the size of the page in the Rate Card section of your bucket, the labels on the bottom of the page were cropped.6.2 Edge 2

CORE-16456When you tried to remove zombie logical volumes after removing disks, the transaction failed but was marked as complete at the Logs page.6.0 - 6.2

CORE-16472Disable Auto Suspending option was not available when you tried to enable it for an already existing account at the User Profile page.6.0 - 6.3 Edge 1

CORE-16463The 500 Internal Server Error appeared at Location Group Details page on attempt to attach Backup Server Zone to Location Group.6.2

CORE-16495See any vCenter Templates permission was missing in the default configuration of vCenter User role.6.2

CORE-16499During migration of a vCenter VS disk it was possible to select mismatching data center and so the transaction failed.6.0 Patch 7 - 6.2

CORE-16506If S.M.A.R.T drive health diagnostics failed, the Storage Health Check reports also failed to be generated and sent.6.2

CORE-16524After you imported Windows-based vCenter VS to OnApp and rebuilt the network, the default gateway value was overriden to 0.0.0.0.6.2

CORE-16528After you imported a VS from vCenter and set service credentials for the VS at the VS Details page, there was no confirmation message about successfully set service credentials.6.0 Patch 9 - 6.3 Edge 1 

CORE-16536

If you set wrong credentials for a vCenter Linux-based VS at the VS details page, and then tried to resize a VS disk, the transaction failed. 6.2.

6.2

CORE-16537Users who had vCenter VSs without service credentials could edit the disk settings at Settings > Disks menu.6.2 Edge2

CORE-16545After you created a user role with Any action on buckets and networks permisson enabled and limited access to networks defined by bucket in restriction set, the restriction was not applied at the Networks page.6.2

CORE-16546In case of having two vCenter compute resource clusters with the same identifiers you could select the wrong cluster at the Compute Resources step of the VS creation wizard.6.2

CORE-16551After you set up notifications for the Hourly storage health report event at the Subscriptions page, you did not receive any message on the Deliveries page. 6.1 - 6.2

CORE-16557The redundant Cancel button was displayed in the Boot from ISO pop-up window if there were no ISOs available for a VS.6.0 - 6.2

CORE-16569The Hypervisor column was empty when you tried to view the details of the vDisk from the Integrated Storage datastore at the Storage Node Details page.6.2 Patch 1

CORE-16570When you tried to view the details of the vDisk from the Integrated Storage datastore at the Storage Node Details page, some table labels were overlapped with the error message.6.2 Patch 1

CORE-16574If you set bigger than available data store size at the Add New Disk or Edit Disk page, the maximum upload size value in the error pop-up window is wrong.6.0 Patch 9 - 6.3 Edge 1

CORE-16589When you tried to log in to OnApp 6.1 under the admin account protected with Yubikey, you received the following error: "Service is temporarily unavailable and Invalid Yubikey."6.1 - 6.2

CORE-16591The option use as gateway was available for the virtual routers under the Default Firewall Rules section at the Firewall Rules page.6.2 Patch 1

CORE-16595If you unassigned a data store from a vCenter compute resource and a data store zone, and then performed the vcenter:clean rake task, the data store was still assigned to the data store zone.6.0 Patch 9 - 6.3 Edge 1

CORE-16596If you unassigned a network from a vCenter compute resource and a network zone, and then performed the vcenter:clean rake task, the network was still assigned to the network zone.6.0 Patch 9 - 6.3 Edge 1

CORE-16599If you did not specify the role label while creating a new role and clicked Save, the error hint indicated the Search field instead of the Label field.6.2 Patch 1 - 6.3 Edge 1

CORE-16601If you set RAM to the value that was not a multiple of four during vApp recomposing, the transaction failed.5.5 - 6.2

CORE-16602It was impossible to hot migrate a vCenter VS disk if the target data store was moved from the initial data store zone.6.2

CORE-16603When you tried to import or resync a vCenter VS created from CHR OVA template, the transaction failed with the following error System Error ('undefined method `domainName' for nil:NilClass').6.2

CORE-16609If you tried to log in to your account using YubiKey and the credentials were invalid, the login failed but there was no error notification about invalid YubiKey credentials.6.2 Patch 1 - 6.3 Edge 1

CORE-16613After you migrated a virtual router, the VR's network interface on the target comute resource did not respond.6.1 - 6.2

CORE-16615If you submitted an invalid Edit CDN Resource API request, the 500 Internal Server Error appeared in the output instead of 400 Bad Request error.6.0 - 6.2

CORE-16617If you sorted nodes using the By compute resource filter while editing 4s2r or 2r2s IS data store and saved the edits at the Edit Data Store page, the data store was not updated.6.0 - 6.2

CORE-16635The irrelevant Networks field was displayed at the Confirmation step of the smart server Creation wizard.6.0 Patch 9 - 6.2

CORE-16643When you tried to create a new user and used the “<” or “>” symbols when setting a password, the error message appeared in the user creation wizard.6.0 - 6.2

CORE-16645The tooltip that appeared as you hovered over the Tools button at the VS Details page did not disappear after the page autorefresh.6.3 Edge 1

CORE-16646If you set two for cores and vcpu values for a VS, and then unlocked editing XML config for a VS at the Edit XML Config page and clicked the Save button, the Irrelevant numbers of CPU sockets error appeared.6.0 - 6.3 Edge 1

CORE-16647If you tried to hot full migrate a VS without networks via the Migration wizard, the transaction failed with a system error.6.2

CORE-16651After you migrated a VS with disks, the IP addresses remained identical on source and target compute resources.6.2

CORE-16662If you tried to suspend a vCloud user at the Users page, the transaction failed with the system error.6.2

CORE-16672If you set the default rate for network interface in the info_hub.local.yml file, the changes weren't applied at the Resource step in the VS Creation wizard.6.0 Patch 8 - 6.3 Edge 1

CORE-16675When you tried to create a new CloudBoot compute resource and there were no disks attached to a particular compute resource, the Devices step of the creation wizard was empty.6.2 Patch 1

CORE-16682As you tried to add a new user, the Roles field was overlapped at the Roles& Groups step of the User Creation form.6.3 Edge 1

CORE-16686If you started vCenter daemon and then shut down a vCenter VS, the vCenter compute resource status was still displayed as Online at the Compute Resource Details page.6.2 Patch 1

CORE-16692When you performed full migration or hot full migration of a VS between compute zones without changing networks, the network join remained the same at the Network Interfaces page.6.2

CORE-16693When you tried to migrate your Linux-based VS from Xen to KVM compute resource, the VS network was lost.6.2 Patch 1
CORE-16707

The 500 Internal Server Error appears at the DNS page if connection to a CDN server is disabled.

6.0 - 6.2

CORE-16724If there was a backup server with no free space in your Control Panel, and you tried to convert an OVA template to KVM or vCenter at the All OVSs page, the error message that appeared was misleading.6.2 Patch 1 - 6.3 Edge 1

CORE-16733It was impossible to hot migrate a VS created from the Linux template between two compute resources.6.2 Patch 2 - 6.3 Edge 1

CORE-16739If you had 2019 Windows license and selected 2016 or later Guest OS version for a Windows-based vCenter VS on the vCenter side, it was not possible to use 2019 Windows license on OnApp side at the Software Licenses page.6.0 - 6.3 Edge 1

CORE-16753In case of 400 or 500 code errors in the interface, the Server error text appeared instead of the corresponding error code page.6.2 - 6.3 Edge 1

CORE-16757If you inserted incorrect credentials for your vCenter Windows-based VS and tried to reset administrator password via SSH, the VS was locked and transaction stucked.6.2 - 6.3 Edge 1

CORE-16760After you unassigned IP addresses to a Windows-based vCenter VS and then performed network rebuild, the IP addreses were still assigned to the VS.6.3 Edge 1

CORE-16762If you created a VS without selecting a specific data store in the VS creation wizard, all VS disks were created in the data store with the smallest size and available space.6.0 Patch 9

CORE-16766After the content balance check failed for an IS compute zone with local read enabled, and you clicked the Rebalance button to rebalance disks at the Content Balance Check page, the transaction stuck in an endless loop.6.2

CORE-16767The OnAppTmp folder was not removed for vCenter Windows-based VSs after such transactions as ResetRootPassword, BuildDisk, or ResizeDisk.6.0 Patch 9 - 6.3 Edge 1

CORE-16770It was impossible to create a disk with Require format option enabled for Windows-based VSs built from vCenter template.6.0 Patch 9 - 6.3 Edge 1

CORE-16784When you selected vCenter or vCloud type in the compute resource creation wizard, the irrelevant error message appeared about changing Integrated Storage settings.6.2 - 6.3 Edge 1

CORE-16787If a user with See all templates permission disabled has only child group templates added to one’s bucket without the parent template group, these templates are not displayed at the Templates step of VS Creation wizard.6.2 - 6.3 Edge 1

CORE-16790If you disabled the Show Compute resources on Virtual Server creation permission, the Primary data store dropbox at the Resources step of the VS Creation wizard still contained data stores added to a restricted compute zone.6.0 - 6.3 Edge 1

CORE-16792When a transaction failed on VS which was not built or it was built and locked, and you scheduled the next transaction on this VS, the Failed instead of Pending status was displayed at the VS Details page.6.2 - 6.3 Edge 1

CORE-16794The All and Degraded buttons at the Data Store Details page were not aligned properly. 6.3 Edge 1

CORE-16795In Chrome browser, if you selected Translate to option, Google translate dis not work and OnApp pages were displayed without text.6.2 - 6.3 Edge 1

CORE-16797When you tried to set the same OVA label to the virtualization in the Convert to Virtualization pop-up window, the redundant error notification appeared in the background.6.2 - 6.3 Edge 1

CORE-16798After hot full migration, invalid backups were displayed as available at the Backups page but restoring files from those backups failed.6.2 Patch 2 - 6.3 Edge 1

CORE-16802When you tried to delete a disk at vCenter VS Disks page with Force Reboot option enabled and Power off shutdown type selected, the VS did not power off on the vCenter side.6.3 Edge 1

CORE-16807If your user had the Remove/update/view own IP nets permissions enabled, it was possible to remove, update, and view all IP nets in the cloud, but not only those that belonged to the user.6.2 - 6.3 Edge 1

CORE-16808If your user had the Remove/update/view own IP ranges permissions enabled, it was possible to remove, update, and view all IP ranges in the cloud, but not only those that belonged to the user.6.2 - 6.3 Edge 1

CORE-16810You could not view own IP nets and IP ranges at the Networks page with the See all own networks permission enabled.6.2 - 6.3 Edge 1

CORE-16827If the Show Compute resources on Virtual Server creation permission was disabled for a user, all networks were available for selection at the Resources step of the VS Creation wizard.6.0 - 6.3 Edge 1

CORE-16828The Add new own Network, Delete own Network, and Update own Networks permissions could be enabled though irrelevant, and the See own networks permission did not allow a user to view any networks, including one’s own.6.2 - 6.3 Edge 1

CORE-16829The redundant scrollbar appeared in the Convert to Virtualization pop-up window as you tried to convert an OVA template to virtualization on Windows OS.6.3 Edge 1

CORE-16830As you clicked the CPUs button at the Virtual Servers page to sort the VSs by CPU cores number, the VSs were not sorted.6.3 Edge 1

CORE-16839You could not start a VS built from a vApp with CPU unlimited and PAYG resource pool type. 6.3 Edge 1

CORE-16840An option to decrease size of vCloud and vCenter disks was available at the Edit Disk page, even though irrelevant and the transaction failed.6.0 - 6.3 Edge 1

CORE-16843VPN was not enabled on VS's DRaaS Dashboard in case of enabling VPN via cloud settings and restart replication.6.3 Edge 1

CORE-16844If you tried to delete a VS backup at the Backups for Virtual Server page, the transaction failed with a system error. 6.0 - 6.3 Edge 1

CORE-16846The 500 Internal Server Error appeared at the Edit Recipe page after you changed the sequence of recipes steps and clicked Save. 6.2 - 6.3 Edge 1

CORE-16847It was impossible to cold migrate a Windows-based VS if it had extended CPU flags enabled.6.0 - 6.2 Patch 2

CORE-16850The Size column label at the Data Store Details page was not aligned properly. 6.3 Edge 1

CORE-16859The measurement unit for CPU sockets at the Edit VS page was not displayed.6.3 Edge 1 - 6.3 Edge 2

CORE-16861After you enabled or disabled the Boot from CD option for a smart server built from ISO, the was no notification about enabling or disabling the option. 6.3 Edge 1

CORE-16863The 500 Internal Server Error appeared as you double clicked the IP Ranges tab at the CDN Resources page.6.2 - 6.3 Edge 1

CORE-16866The scrollbar in the Create Locale pop-up window was distorted.6.3 Edge 1

CORE-16868As you tried to trigger a custom event at the Event Types page, the Cancel and Trigger buttons in the Trigger Message pop-up window were not aligned properly.6.3 Edge 1

CORE-16869You could not access a virtual router via console without the Any action on virtual routers permission enabled.6.2 - 6.3 Edge 1

CORE-16870You could not manage recipe and service add-ons of a virtual router without the Any action on virtual routers permission enabled.6.2 - 6.3 Edge 1

CORE-16871You could not boot a virtual router from ISO without the Any action on virtual routers permission enabled.6.2 - 6.3 Edge 1

CORE-16872You could not assign an IP net to a virtual router if the Max Port Speed for the corresponding network zone was less than the global max speed specified in bucket.6.2 - 6.3 Edge 1

CORE-16874If you uploaded an ISO via URL method, it was not displayed at the Templates step of the smart server creation form.6.3 Edge 1

CORE-16888

Sometimes, after upgrading to 6.2, the 500 Internal Server Error may appear at the CDN usage statistics and CDN Resources pages.6.2 Patch 2

CORE-16889You could not migrate a load balancer without the Any action on load balancer permission enabled.6.0 - 6.3 Edge 1

CORE-16893You could not migrate a load balancer without the Any action on load balancer permission enabled.6.2 - 6.3 Edge 1

CORE-16905If you set an IP address as a label for a virtual server, the search was not working properly. 6.0 Patch 9

CORE-16909It was possible to allocate more than available Primary and Swap disks size at the Resources step of the VS Creation wizard for a Linux-based VS, but the VS creation failed.6.2 - 6.3 Edge 1

CORE-16917When you disconnected or connected a network from/to edge gateway on vCloud side, the changes were not applied on OnApp side.6.2 - 6.3 Edge 1

CORE-16930You could not start or stop a vApp using the Power buttons at the vApps page with the Any action on vApp permission disabled.6.3 Edge 1

CORE-16951As you opened the Assigned Recipes page, its shrunk version was displayed for a few seconds instead of the regular page view.6.0 - 6.3 Edge 1

CORE-16959The Available recipes and Recipes events tables were not aligned properly at the Assigned Recipes page.6.3 Edge 1

CORE-16960If you hot migrated a Linux-based VS, the billing recalculations transaction failed. 6.3 Edge 1

CORE-16962Redundant tooltops appeared at the vCenter VS Properties page as you hovered over the place above the OS icon. 6.2 Patch 2 - 6.3 Edge 2

CORE-16989If the libvirt command failed during Xen to KVM migration, rollback didn't revert the database changes.6.2 - 6.3 Edge 1

CORE-16906When your first transaction from the chain failed to start, the transaction logs might have canceled status and then, changed to pending status.6.2 - 6.3 Edge 1

CORE-16975You could not set SSH Key for a smart server.6.3 Edge 1

CORE-16979If you enabled automated backup at the Confirmation step of VS Creation wizard, the auto-backup ran and failed before the VS was built.6.0 Patch 10 - 6.3 Edge 1

CORE-16990If before Xen to KVM migration you did not set the limits for disk size at least 1 GB higher per each disk except swap  in destination data store zone, the migration failed.6.2 - 6.3 Edge 1

CORE-16991Log percentage and output was missing for Xen to KVM or disk migration transactions. 6.2 Patch 2- 6.3 Edge 1

CORE-17000If you tried to install a load balancer on a VS on a KVM compute resource and with a Zabbix server set up, the transaction failed.6.3 Edge 1

CORE-17004If you tried to rebuild network for a load balancer after assigning a sedcondary IP address, the transaction failed.6.2 Patch 4

CORE-17014A redundant tooltip appeared in the Reset Virtual Server Password as you hovered over the Set Password button. 6.3 Edge 2

CORE-17040If you selected a Pro or Dev tier that was not available while adding a compute zone to Federation, the Next button was inactive and there was no notification about the inavailability of the selected tier.6.3 Edge 1

CORE-17042If you set any value for create_snapshot_timeout parameter in the on_app.yml file, and then performed any vCloud-related actions limited by time (compose vApp, start vApp, etc.), the timeout value was not applied.6.2 - 6.3 Edge 1

CORE-17043If you changed NIC or IP mode for a VS or vApp on vCloud side, the old NICs were not removed on OnApp side.6.2 - 6.3 Edge 1

CORE-17049You could not select the last CloudBoot compute resource on the list at the Add New CloudBoot Compute Resource page.6.3 Edge 1

CORE-17057If you tried to import two or more templates with the same label from different data centers or vCenter compute resources to OnApp, only one template was imported.6.2 - 6.3 Edge 1

CORE-17058If you tried to create a new Load Balancer with a label typed in Cyrillic, you saw the 500 Internal Server Error at the Add Balancer page.6.2 Patch 4

CORE-17069If you tried to restore a a VS from a Veeam recovery point at the Recovery Points page, the transaction failed.5.10 - 6.3 Edge 1

CORE-17085The permission label was just Recovery point instead of Any action on recovery points6.2 Patch 3

CORE-17125If you tride to migrate a VS from Xen to KVM with full or disabled data store, the transaction failed with a system error.6.2 Patch 4 - 6.3 Edge 1

CORE-17133The count of the service add-ons was not displayed at the Assign Service Add-Ons page.6.3 Edge 2

CORE-17138If you have more than one vCenter, you might see the networks from one vCenter shown as available for another vCenter.

6.2 Patch 4 - 6.3 Edge 1

CORE-17167If before Xen to KVM migration you did not set the limits for disk size at least 1 GB higher per each disk except swap in source data store zone, the migration failed.

6.3 Edge 2

CORE-17188The size of the pop-up window Add new Data Store zone resources decreased after clicking Submit at the page MS Basket Clone of Default Bucket Access Control.6.3 Edge 2

CORE-17191If you assigned more than two IP addresses to a VS, the label in the IP Addresses column was not aligned properly at the Virtual Servers page. 6.3 Edge 2  

CORE-17259It was impossible to clone a virtual server build from an instance package.6.2 Patch 4 - 6.3 

CORE-17235If you set the end date that preceded the start date in the statistics filter at the Acceleration Reporting page, the error message that appeared was duplicated. 6.3 Edge 2

CORE-17238If you tried to start up a vCenter VS built in infrastructure mode and from a template with no VMware tools installed, the transaction failed. 6.3 Edge 2

CORE-17239The redundant Rebuild Network button was displayed at the IP Addresses for this VS page for vCenter VSs built in infrastructure mode. 6.3 Edge 2

CORE-17240It was not possible to clone a vCenter VS built in infrastracture mode. 6.3 Edge 2

CORE-17280Although it was not allowed to edit and view other users' profiles with only the Add SSH Keys for Own Virtual Servers and Set SSH Keys permissions enabled, it was possible to see or set SSH keys for any user in the cloud at the SSH Keys page.6.0 - 6.3 Edge 2

CORE-17319It was impossible to hot attach a new disk to VS when TRIM was enabled.6.2 Patch 4

CORE-17387It was impossible to set the CDN bandwidth limit in the bucket at the Access Controls page.6.2- 6.3

WIZ-123It was impossible to run the recipes for a vCloud virtual server created from Windows and Linux templates.6.2- 6.3

STORAGE-1802Rarely, if Integrated Storage disks were corrupted, the Unicode strings in the storageAPI.py were parsed incorrectly4.2 - 6.2

STORAGE-1833If a filesystem operation failed, it retried only one time instead of three.4.1 - 6.2

STORAGE-1913The formatandconfigure transation failed when you tried to format disk with live LVM or device mapped devices. 4.1 - 6.2

STORAGE-2154After you stopped or started a SAN controller via SSH, the ISD config was generated twice. If a filesystem operation failed, it retried only one time instead of three.6.1 Edge 1 - 6.2

STORAGE-2216You could not repair vDisks for datastores with 4 stripes and 2 copies successfully.6.0 Patch 7

STORAGE-1890Sometimes, the rmmod tool for the Integrated Storage controller was not working properly and could not remove a module from the Linux kernel.4.1 - 6.3 Edge 1

STORAGE-2009The force option to delete a data store with nodes containing VDisks was not available.3.5 - 6.3 Edge 1

STORAGE-2142If the cache drive crashed, you could not start or migrate a VS.6.0 Patch 7 - 6.3 Edge 1

STORAGE-2234If a filesystem operation failed, it retried only one time instead of three.6.3 Edge 1

STORAGE-2246If you tried to delete an already deleted vDisk via API call, the request failed, but there were redundant retry attempts in logs.6.0 Patch 9

INSTALLER-462SSH connection was lost on CentOS 7.7 KVM static compute resources and backup servers with Integrated Storage after running the systemctl isolate onapp-storage.target command.6.0 Patch 10 - 6.2

INSTALLER-489If you used the NSX functionality, the size of production log could exceed 3GB per month.6.2

INSTALLER-497If you updated libvirt and KVM versions from 1.5.x to EV on CentOS7 KVM compute resources with powered on VSs, the VSs were powered off after the update.

6.0 Patch 8 - 6.2

CLOUDBOOT-605Updated the Xen version for static and CloudBoot CentOS 7 compute resources to 4.10.4.42.g24d62e1262-1.el7 to address the XSA-313/CVE-2020-11740 and CVE-2020-11741 issues.6.0 - 6.2

CLOUDBOOT-606Updated the Xen version for CentOS 7 compute resources with Arm-based CPU to 4.10.4.42.g24d62e1262-1.el7 to address the XSA-314/CVE-2020-11739 issue.6.0 - 6.2

CLOUDBOOT-607Updated the Xen version for static and CloudBoot CentOS 7 compute resources to 4.10.4.42.g24d62e1262-1.el7 to address the XSA-316/CVE-2020-11743 issue.6.0 - 6.2

CLOUDBOOT-609Updated the Xen version for static and CloudBoot CentOS 7 compute resources to 4.10.4.42.g24d62e1262-1.el7 to address the XSA-318/CVE-2020-11742 issue.6.0 - 6.2

CLOUDBOOT-613If VNC WebSocket and VNC Display port were not available after updating OnApp software with WebSocket implementation, the Cannot recv data: Connection reset by peer error appeared in logs until the VS reboot.6.0 Patch 8 -  6.2

CLOUDBOOT-641
CLOUDBOOT-642
CLOUDBOOT-643
CLOUDBOOT-644
CLOUDBOOT-645
Updated the Xen version for CentOS 7 compute resources to 44.10.4.75.g93be943e7d-1.el7 to address the XSA-319/CVE-2020-15563,  XSA-317/CVE-2020-15566, XSA-321/CVE-2020-15565, XSA-327/CVE-2020-15564, and the XSA-328/CVE-2020-15567 issues. 6.0 - 6.2