6.2 Stable Release Notes

23 December 2019

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

Before You Upgrade 

  • You can update to OnApp 6.2 Stable from OnApp 6.1, 6.2 Edge 1 or from 6.2 Edge 2.
  • In this release, vCloud Director v9.1 support comes to its end of life and will be unavailable to use in the next releases.

Highlights

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


Migration from Xen to KVM

OnApp introduces the possibility to migrate virtual servers from Xen to KVM compute resource. Since KVM virtualization type is becoming more and more popular, OnApp gives you an option to easily move to it. The most time-consuming operations are performed with the virtual server being online, so the required downtime period is as short as possible. 

System Service Add-ons

With the introduced functionality of system service add-ons, you can offer your customers additional services on top of your current IaaS Virtual Server offering. Now you have an ability either to add obligatory services to a virtual server, or assign a system service add-on to a template or OVA. 

NSX Integration

With NSX-v integration used for vCloud edge gateways or vCenter edges, you get flexible network configuration managed in OnApp interface. Apart from that, NSX-v provides network isolation as well as the ability to build edge gateway services on the top. With the help of NSX, you can configure the following services for each edge or edge gateway: Firewall, Load balancer, NAT rules, and VPN.

SPLA Reporting

According to the new Microsoft requirement, service providers with Windows-based VSs will need to report their usage to Microsoft by sending an SPLA Report monthly. To make it easier for our customers, OnApp is implementing a possibility to generate an SPLA (Services Provider License Agreement) report for Windows-based VSs. 

Resync vCenter VS

Resync vCenter VS option allows you to synchronize the changes you applied to a vCenter virtual server on the vCenter side after you already imported the VS to OnApp. In just one button click you can update the changes on the OnApp side to match, and all the latest configurations will smoothly even out.

Instance Packages Support in Federation

Starting from OnApp 6.2 Edge 1, you have a possibility to create a virtual server based on instance package. It is a preconfigured CPU/RAM/Disk/Bandwidth package, which facilitates and accelerates the virtual server creation greatly. You now can select this option at the Resources step in the VS creation wizard. 



Features & Improvements


TypeKeyRelease Notes
OnApp Cloud

Feature

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

Feature

CORE-14457Introduced the new type of system service add-ons, which are obligatory for end users and impossible to remove.

Feature

CORE-14954With SPLA report you can avoid Microsoft compliance gaps in licenses usage tied to services you provide on Windows-based VSs.

Feature

CORE-15355Now you can select Network Appliance as operating system when converting OVA into KVM-based template.

Feature

CORE-15491Now you can manage advanced configuration for OVA VSs based on Network Appliance operating system.

Improvement

CORE-9631Now you can create a federated VS from an instance package.

Improvement

CORE-14338Now you can select as many compute zones as you need to set the same limits for all resources in the newly created bucket.

Improvement

CORE-10263Now you can unassign multiple IP addresses from a user in one click instead of selecting them one by one.

Improvement

CORE-13073Now you can edit port speed for a network interface of a federated VS not only via API but also via the OnApp interface.

Improvement

CORE-15144During migration from Xen to KVM, you can immediately view the updated price per hour for a VS changed due to the increase of the primary disks' size.

Improvement

CORE-15113

You can enable a new setting to use Super Admin permissions and restrict a user to create roles, assign other users to roles and log in to CP as users with permissions exceeding her or his own permissions.

Improvement

CORE-15191Now you can not only edit the CORS header status at the Edit CDN Resource page but also see the current CORS header status at the Advanced CDN Resource Details page.

Improvement

CORE-15140Updated a minimum value that you can set for Dom0 memory to 3648 MB on CloudBoot compute resources based on Xen and CentOS 7.

Improvement

CORE-12028Now you can see not only the Template name but also the compute zone type it belongs to in the Properties dropbox at the Template Store page as you add a template to a template group.

Improvement

CORE-14318

CORE-14631

Now you can configure the auto-backups re-run period in the info_hub.yaml configuration file, which is now by default set to 3 hours instead of 1 day.

Improvement

CORE-14460Now the Available Recipes and Recipes Events columns at the Recipes page are fixed as you scroll them and drag-n-drop items between them. 

Improvement

CORE-9514Improved the process of deleting backups of federated VSs: a notification about the completion of a transaction is not sent from Seller to Buyer until the previous notification is sent.

Improvement

CORE-14492Added support of Zabbix server deployment for CentOS7.

Improvement

CORE-15642Now system service add-on assigned to a VS associated with a vApp is not lost after this vApp is converted to a template.

Improvement

CORE-15692Now you can create a VS from an OVA template with no backup server if you set NULL value for the backup server ID in the template’s database after it is uploaded.

Improvement

CORE-15737Accelerators are renamed into Edge Accelerators to achieve better consistency of OnApp terms.

Improvement

CORE-15907Now when enabling DRaaS for a VS, an additional 1GB disk is created on the shadow VS to store replication metadata and resume replication after a crash.

Improvement

CORE-14493Reduced the response time for the available templates load on the Templates step in the VS creation wizard. 
Improvement
CORE-14713Updated the virsh capabilities data to enforce using all necessary Windows 2016/10 CPU features by default.

Improvement

CORE-14282Now not only admins but also end users can see the resource usage graphs on their Dashboards.

Improvement

CORE-14796Updated the tabs to match the new UI layout design.

Improvement

CORE-14799Updated the calendar to match the new UI layout design.
Improvement
CORE-14893Implemented an improved version of the federation price calculator with increased maximum values and ratios for the VS resources.

Improvement

CORE-15083Now price and limits for RAM are calculated per GB per hour instead of MB per hour.

Improvement

CORE-14977Now, after you reboot a VS with manually mounted disk assigned and TRIM enabled, the path to the disk is updated automatically, so TRIM doesn’t require additional editing.

Improvement

CORE-15130With the improved Usage Statistics page speed, you can generate billing statistics fast regardless of the number of resources on the page.

Improvement

CORE-15193Added the search field to the Networks and Network Zones pages.

Improvement

CORE-15194

Added the search field to the Data Stores and Data Store Zones pages.

Improvement

CORE-15238Now you can check the price per last hour including discount in the Billing Details section at the User Profile page. 

Improvement

CORE-15286Updated the default layout design to achieve consistency with the new UI.

Improvement

CORE-15298With the new loading indicator, you are now notified that content is loading on the Templates step in the VS creation wizard.

Improvement

CORE-15496Now you can set up and reconfigure a Zabbix server via API.

Improvement

CORE-15501Now you are notified of incorrect data input in the New IP Net form when adding IP nets to the network and can fix it right away.

Improvement

CORE-15504Improved handling of transactions execution delays.

Improvement

CORE-15505Autoscaling events are now scheduled for a VS only if there are no transactions running to avoid redundant scheduling.

Improvement

CORE-15547Improved handling error output with special symbols while processing recipe on a VS with custom localization.

Improvement

CORE-15579Now you can take VS backups and resize the VS without reboot at the same time.

Improvement

CORE-15581Improved DRaaS error handling if connection between source and shadow VSs is lost.

Improvement

CORE-15718Removed the irrelevant KVM CentOS6 compute resources from "Xen to Kvm Migrate" migration wizard.

Improvement

CORE-15664The Control Panel server now uses a new version of an image (7.7) for Recovery Mode.

Improvement

CORE-14797Updated accordions to match the new UI layout design.

Improvement

CORE-15168Updated note boxes to match the new UI layout design.

Improvement

CORE-15169Updated toggles to match the new UI layout design.

Improvement

CORE-15483Updated custom themes settings to match the new UI layout design.

Improvement

CORE-16041Now the IO limits are updated after hot migration of VS disk.

Improvement

CORE-16134Implemented the IP Usage Report for Federation: now you can view when the IP addresses assigned or unassigned to a particular buyer.

vCloud & vCenter

Feature

CORE-15275With NSX integration you can now configure Advanced Edge services within the OnApp interface.

Feature

CORE-15011

Introduced the new type of system service add-ons for vCloud, which are obligatory for end users and impossible to remove.

Feature

CORE-15263With a new vCenter User role, you receive additional permissions to create a vCenter VS as a user.

Improvement

CORE-15239Now you can check the resources' discounted price per hour and per month in the top right corner of the Billing Details section at the User Group Details page.

Improvement

CORE-15270Now you get an alert notification in case vCloud statistics gathering transaction fails.

Improvement

CORE-15192Improved the vCloud statistics by providing more details in log output, and added a notification in case of statistics collecting failure. 

Improvement

CORE-15128Now you can move created but not yet imported VSs between the Resource Pools on the vCenter side and they are recognized on the OnApp side by the auto-import rules.

Improvement

CORE-14337Now vCenter templates are also imported as you add a vCenter compute resource to OnApp.

Improvement

CORE-14923Now, if you import a vCenter VS to OnApp, and then make any changes to the VS on the vCenter side, you can resync the VS to update the changes on the OnApp side to match.

Improvement

CORE-16031Added the possibility to assign recipes and system service add-ons to the templates imported from vCenter.




CloudBoot

Feature

CLOUDBOOT-481Added the Expect utility for all CloudBoot compute resources.

Improvement

CLOUDBOOT-492Added Socat command for all compute resources to enable bidirectional data relay between the data channels.

Improvement

CLOUDBOOT-496Added WireGuard kernel module and utility for CentOS7 Xen, KVM and CentOS6 Xen compute resources.

Improvement

CLOUDBOOT-501Updated OnApp Storage with the onappstore-6.2-7769-master.x86_64.rpm ramdisk images for CloudBoot 6.2 Edge 1.

Improvement

CLOUDBOOT-508Updated the following components for CentOS 7 KVM ramdisk:
  • A CentOS version to 7.7.1908
  • A kernel version to 3.10.0-1062.1.1.el7.x86_64
  • A libvirt version to 4.5.0-23.el7_7.1 to address the CVE-2019-10161, CVE-2019-10166, CVE-2019-10167, CVE-2019-10168, CVE-2019-10132, CVE-2018-12126, CVE-2018-12127, CVE-2019-11091, CVE-2018-12130, and the CVE-2019-3840 issues
  • An XFS filesystem driver sources version to 3.10.0-327.36.3.el7.x86_64 based on a kernel version 33.10.0-1062.1.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 
  • A UFS filesystem driver sources version based on a kernel version 3.10.0-1062.1.1.el7.x86_64 compelled with R/W support patch
  • A qemu-kvm-ev version to 2.12.0-33.1.el7 to address CVE-2018-17958, CVE-2018-17963, CVE-2019-6778, CVE-2019-9824, CVE-2018-20815, CVE-2018-12126, and the CVE-2019-6501 issues
  • A wireguard sources version to 0.0.20190702 based on a kernel version 3.10.0-1062.1.1.el7.x86_64 patched with wireguard-rhel.patch
  • Kernel modules with GCC version to 4.8.5-39.el7.x86_64

Improvement

CLOUDBOOT-509

Updated a CentOS version to 7.7.1908 for CentOS Xen ramdisk.

Improvement

CLOUDBOOT-532

Updated a qemu-kvm version to 0.12.1.2-2.506.el6_10.5 compiled with --enable-io-throttling for CentOS7 KVM ramdisk to address CVE-2018-11806, CVE-2018-10839, CVE-2018-17962, CVE-2019-6778, and the CVE-2019-12155 issues.

Improvement

CLOUDBOOT-533Updated a Xen version to 4.8.5.48.gc67210f60d-1.el6 for CentOS 6 Xen ramdisk to address the XSA-296/CVE-2019-18420, XSA-298/CVE-2019-18425, XSA-299/CVE-2019-18421, XSA-301/CVE-2019-18423, XSA-302/CVE-2019-18424, and the XSA-303/CVE-2019-18422 issues.

Improvement

CLOUDBOOT-534Updated a Xen version to 4.10.4-2.el7 for CentOS 7 Xen ramdisk to address the XSA-296/CVE-2019-18420, XSA-298/CVE-2019-18425, XSA-299/CVE-2019-18421, XSA-301/CVE-2019-18423, XSA-302/CVE-2019-18424, and the XSA-303/CVE-2019-18422 issues.

Improvement

CLOUDBOOT-542Updated the following components for CentOS 7 KVM ramdisk:
  • A CentOS version to 7.7.1908
  • A kernel version to 3.10.0-1062.4.2.el7.x86_64 to address the CVE-2018-20856, CVE-2019-3846, CVE-2019-0155, CVE-2019-0154, CVE-2019-11135, CVE-2018-12207, CVE-2019-14835, CVE-2019-9506, and the CVE-2019-10126 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-1062.4.2.el7.x86_64 and 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 
  • A UFS filesystem driver sources version based on a kernel version 3.10.0-1062.4.2.el7.x86_64 compelled with R/W support patch
  • a qemu-kvm version to 2.12.0-33.1.el7_7.4

Improvement

CLOUDBOOT-543Updated a kernel version to 2.6.32-754.24.3.el6.x86_64 for CentOS 7 KVM ramdisk to address the CVE-2018-12207, CVE-2019-11135, CVE-2019-0154, and the CVE-2019-0155 issues.

Improvement

CLOUDBOOT-545Updated the following components for CentOS 7 KVM ramdisk:
  • A CentOS version to 7.7.1908
  • A kernel version to 3.10.0-1062.4.3.el7.x86_64 to address the CVE-2019-0155 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-1062.4.3.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 
  • A UFS filesystem driver sources version based on a kernel version 3.10.0-1062.4.3.el7.x86_64 compelled with R/W support patch

Improvement

CLOUDBOOT-553

Updated the following components for CentOS 6 Xen ramdisk:

  • A kernel version to 4.9.199-35.el6.x86_64
  • A UFS file-system driver sources version based on the kernel version 4.9.199-35.el6.x86_64 sources and patched with super-ufs_fs_write.patch
  • WireGuard kernel module(s) version 0.0.20190702 built against kernel version 4.9.199-35.el6.x86_64
  • Xen version to 4.8.5.75.g4c666a7e15-1.el6 to address the XSA-304/CVE-2018-12207, XSA-305/CVE-2019-11135 issues

Improvement

CLOUDBOOT-552

Updated the following components for CentOS7 Xen ramdisk:

  • A kernel version to 4.9.199-35.el7.x86_64
  • UFS file-system driver source version based on the kernel 4.9.199-35.el7.x86_64 sources and patched with super-ufs_fs_write.patch
  • WireGuard kernel module(s) version 0.0.20190702 built against kernel version 4.9.199-35.el7.x86_64
  • Xen version to 4.10.4.26.gfde09cb80c-1.el7 to address the XSA-304/CVE-2018-12207, XSA-305/CVE-2019-11135 issues

Improvement

CLOUDBOOT-564Updated the OnApp Storage with the onappstore-6.2-8630-master.x86_64.rpm ramdisk images for CloudBoot 6.2.

Improvement

CLOUDBOOT-565Updated a Xen version to  4.8.5.77.gec6c25e467-1.el6 for CentOS 6 Xen ramdisk to address the XSA-306/CVE-2019-19579 issue.

Improvement

CLOUDBOOT-566Updated a Xen version to 4.10.4.28.ge4899550ff-1.el7 for CentOS 7 Xen ramdisk to address the XSA-306/CVE-2019-19579 issue.


Improvement

CLOUDBOOT-567Updated a libvirt version to 4.5.0-23.el7_7.3 for CentOS 7 KVM ramdisk.

Integrated Storage

Improvement

STORAGE-1322Improved security of DraaS functionality to exclude mitten attacks.

Improvement

STORAGE-1856Improved the reliability of epochs by implementing an additional check during the repair.

Improvement

STORAGE-2150Now you can see the NIC details for compute resources with Integrated Storage via API.

Improvement

STORAGE-2156Now the names of bridge and bond devices for the SAN network can be configured from the console.

Improvement

STORAGE-2175Implemented refactoring of an existing codebase for storage port generation and improved mechanism of detecting already taken ports.

Installer

Improvement

INSTALLER-451Added the Expect utility for all Static compute resources.

Improvement

INSTALLER-457Updated Control Panel script to allow smooth transition to OnApp 6.2 Edge 1 version.

Improvement

INSTALLER-458Updated the script to enable Zabbix installation for CentOS7 compute resources.

Improvement

INSTALLER-461Implemented the -y command-line option for KVM compute resources installer to prevent unwanted packages from installing.

Improvement

INSTALLER-472Added OnApp Licensing service configuration file to systemd software suite.


Fixes


TypeKeyRelease NotesAffected Versions

CORE-4560If you created a template from a VS's backup file, which did not start with the OS name, the OS icon for a template wasn't displayed correctly.4.0-6.1

CORE-5607The See all roles permission was enabled by default though irrelevant for vCloud vApp User,  vApp Author,  Catalog Author, Console Access Only, and Defer to Identity Provider roles.4.1-6.2 Edge 2

CORE-9155

You couldn't create a template group from My Template Groups menu if there was a template group with the same label already. 

5.0-6.1

CORE-10300After you enabled CPU topology and then switched from KVM to Xen compute zone at the Resources step of the VS creation wizard, you could still configure CPU sockets and threads that are not applicable to Xen.6.1

CORE-11236For the federated buyers’ VSs, the allocated IPsv6 addresses were not displayed in the UI at the IP Addresses page.

5.4-6.1

CORE-11741It was possible to see and create Admin notes for a vCloud VS in OnApp Cloud with not only vCloud Admin role but also any other vCloud one. 5.6-6.1

CORE-12369You could create a VS based on Orchestration Model with Allocation Pool or PAYG VDC model type with vCPU speed other than set during the Orchestration Model creation.5.5-6.2 Edge 2

CORE-12425The White List tab was not displayed at the User Profile page if the Read all white user IPs permission was disabled.5.5-6.1

CORE-12859It was possible to delete a VS disk with the Destroy any disk permission disabled, if the Manage OnApp Storage permission was enabled. 5.10-6.1

CORE-12942You could create a backup resource zone selecting a federated location group that might lead to issues with unsubscribing from a federated zone.6.0-6.1

CORE-12975The Edit FQDN button was available even though not supported for the federated VSs in the Tools menu at the VS Details page.6.0-6.1

CORE-13035After buyers subscribed to a federated zone, they could not set prices for the templates received from Federation as the sample bucket for template group was not created.6.0-6.1

CORE-13131You could not convert an OVA file to VS template at the All OVAs page, if the filename included spaces. 5.0-6.1

CORE-13170If Control Panel retrieved incorrect or empty data about networks from the server, the Next button became inactive at the Resources step in the VS creation wizard.6.0-6.1

CORE-13345When you tried to run rake vcloud:resync task, the transaction failed.6.1 Edge 1-6.2 Edge 1

CORE-13449A CentOS icon was displayed instead a CoreOS one at the final step in the Create Container Server wizard.6.1 Edge 1-6.1

CORE-13469As you clicked any of the compute resource types on the first step in CloudBoot wizard, the selected line didn’t become highlighted.6.0-6.1

CORE-13548Migration of the virtual servers failed if you used too many characters for the network interface name of the target compute resource. Now the number of characters is determined and limited to 15.6.0.0-98-6.1

CORE-13554The 500 Internal Server Error appeared at the Add New Disk page if you tried to add a VS disk to a federated VS.6.1 Edge 1-6.1

CORE-13655If the number of the compute zone failover iterations exceeded 10, you couldn`t view them all in one page using the All Items option.6.1 Edge 1-6.1

CORE-13704Server error appeared at the Federate Compute zones page if you tried to hide an infobox in the Scores and Benchmarks pop-up window. 6.0.0-98-6.1

CORE-13728When you tried to create a normal VS backup with the Update own disk permission disabled, it was not created, and a Disk not found notification appeared.5.5-6.1 

CORE-13752After you deleted access control you could still see it in the bucket but when you tried to edit it, the transaction failed.6.1 Edge 1-6.1

CORE-14111It was possible to rebuild an OVA VS via API,  though it is prohibited in the User Interface. 6.0-6.1

CORE-14131When you tried to start up a federated Windows-based VS, the transaction failed.6.0.0-152-6.1

CORE-14153After you logged is under the User role and tried to create a VS, the CPU Cores and CPU priority sliders were not responding at the Resources step in the VS creation wizard. 6.1 Edge 1-6.1

CORE-14210The dark theme was not applied to the dropboxes in the Search section.  6.1 Edge 1-6.1

CORE-14211The dark theme was applied incorrectly at the VS Properties page. 6.1 Edge 1-6.2 Edge 2

CORE-14219If you created a vCenter VS based on OVA template with multiple disks assigned, only primary disk was displayed at the Resources step in the VS creation wizard.6.0-6.1

CORE-14236The dark theme was applied incorrectly at the Create Instance Package page. 6.1 Edge 1-6.1

CORE-14237The dark theme was applied incorrectly at the Snapshots and Create New Snapshot pages.6.1 Edge 1-6.1

CORE-14256

You could exceed the maximum supported value of a disk size during adding a new disk to a Windows VS. 

5.5-6.1

CORE-14290

The timezone value was American Samoa for all newly-created Windows-based vCenter VSs, even if in VS creation wizard or at the VS Details page there was another timezone value specified. 

6.0-6.2 Edge 2

CORE-14332The value of the actual free compute resource memory was displayed incorrectly in the Memorty Chart at the Dashboard.5.5-6.1

CORE-14345The Manage Device option for IS static compute resources was missing in the Tools section at the Compute Resource Details page if CloudBoot was disabled for the cloud. 6.1 Edge 1-6.1

CORE-14398The Windows Licensing Type section on the Templates step of the VS creation wizard disappeared after you hovered over the sidebar menu. 6.1 Edge 1-6.1

CORE-14404After you deleted some cloud locations from your license, they were still displayed in the OnApp interface.6.1 Edge 1 - 6.1
CORE-14407Timezone was set to UTC+1 by default instead of the user’s local timezone for a Windows-based VS at the Properties step in vCenter VS creation wizard.6.0-6.2 Edge 2

CORE-14420You could not take incremental backups for more than one drive of a Linux-based VS.4.0-6.1

CORE-14472If you tried to decrease the CPU cores number for a KVM CentOS7 VS with the allow resize without reboot option enabled, the VS was still rebooted after the resize. 6.0.0-159-6.1

CORE-14475After you clicked the Run recipe on VS(s) option in the Actions button dropbox at the Recipes page,  the appeared Run on selected button was not aligned properly. 6.1 Edge 1-6.1

CORE-14482When you tried to delete an SDN Manager with nodes attached, the error message in the notification box was incorrect.6.1 Edge 2-6.1

CORE-14517When you tried to generate the VS hourly statistics through API call, the Outstanding amount was set to incorrect value at the User Details page.6.1

CORE-14572When you tried to migrate a VS with >=2 NICs from vCenter to KVM, the networks were not grouped properly at the Networks step of the Migration wizard.6.0.0-159-6.1

CORE-14577It was possible to assign only one disk to a VS created from a vCenter template.6.1 Edge 2-6.1

CORE-14586The default Swap disk size was not agreed with the value in the template and was set to zero at the last step of the VS creation wizard. 6.1 Edge 2-6.1

CORE-14603After you selected Apply to All Buckets option during the bucket editing, the currencies in all buckets were changed to the one used in the freshly edited bucket.6.0.0-196-6.1

CORE-14657After you changed an owner for a VS with backup schedules, the schedules were not reassigned to the new VS's owner, and the latter was not able to manage them. 6.0-6.1

CORE-14659After you changed the rabbitmq pid file’s path or restarted the RabbitMQ service for the VSs running on CentOS7, RabbitMQ status was displayed as N/A.6.1 Edge 1-6.1

CORE-14687After you deleted the last uploaded OVA file and restarted MySQL and OnApp services for a vCenter VS via SSH, and then tried to migrate it to KVM, sometimes the migration stopped at the Building state and was not scheduled. 6.0.0-196-6.1

CORE-14691The Baremetal server creation wizard included the irrelevant Storage step.6.1 Edge 1-6.1

CORE-14700After you logged out of the system, you could still see the OnApp dashboard and navigate between the sidebar menu tabs. 6.0.0-196-6.1

CORE-14721If you suspended a vApp with a VS assigned, the Console button at the VS Overview Details page was still displayed. 6.0.0-196-6.1

CORE-14722When you zoomed out the map to view edge servers at the CDN resources page, the edge server pins shifted and were displayed incorrectly.5.5-6.1

CORE-14763It was possible to initiate startup of a VS based on OVA template with higher minimum disk size than the minimum disk size of an Instance Package selected, even though the deployment failed. 6.0.0-196-6.2 Edge 2

CORE-14779After you deleted the CDN bandwidth limit in the Limits for CDN Bandwidth section at the Access Control page, the Usage Limit value at the CDN Resources page wasn't updated. 6.1 Edge 2-6.1

CORE-14803After you disabled the Show Network Zones on Virtual Server creation permission and tried to select IP address for a network interface in the new VS creation wizard, the 404 error appeared.6.1 Edge 2-6.1

CORE-14807The 500 Internal Server Error appeared at the Disks page when you tried to edit a degraded VS disk assigned to IS CloudBoot or static compute resource. 6.1

CORE-14811If you copied and then renamed an Orchestration model, the old name was still displayed as you were adding the Orchestration model to a bucket at the Access Control tab of the required bucket. 6.0-6.1

CORE-14822When you tried to import vCD organizations in multiple vCloud director mode to OnApp, the 500 Internal Server Error appeared.6.1 Edge 2-6.1

CORE-14827When you tried to add a new location group for a Federated Zone, the location group was created but you received the notifications about the incorrect configuration.6.0.0-196-6.1

CORE-14834The 500 Internal Server Error appeared in the log output when you tried to check the SDN Manager's connection status via API. 6.0-6.1

CORE-14837The boot VS transaction failed after editing the XML configuration file at the Edit XML Config page, and the <target dev="vda" bus=""/> bus attribute was empty for the primary disk of a Windows-based VS6.1 Edge 2-6.1

CORE-14843The Submit button on the Add IP Address pop-up window did not respond when you tried to assign an IP address to a NIC of a vCenter CentOS-based VS.6.0.0-196-6.1

CORE-14844If you pasted >201 symbols in the Initial root password encryption key field in the Add IP Address pop-up window, the page became unresponsive. 6.0.0-196-6.1

CORE-14845When you migrated a VS from vCenter to KVM with enabled disks to one data store, default datastore ID was passed instead of the selected one.6.0.0-196-6.1

CORE-14849If you disabled DR for a VS or reestablished replication, the StopReplication transaction failed with a fatal error. 6.1 Edge 1-6.1

CORE-14850Shadow VSs were connecting via SSH through the default 22 port, which sometimes could lead to security issues with firewall. 6.1 Edge 2-6.1

CORE-14854After you assigned an SDN network to a user, the Assign to user option became irrelevant but was still displayed in the Actions dropbox at the Networks page.6.1

CORE-14856If you tried to hot full migrate without storage and networks a VS with SDN between two KVM CentOS 7 compute resources, the transaction failed with a fatal error. 6.1-6.2 Edge 2

CORE-14872After you updated your cloud to OnApp  6.1 Edge 1 or 6.1 Edge 2 and generated statistics for the cloud, the output was duplicated in graphs on the Dashboard.6.1 Edge 2-6.1

CORE-14877The Undefined method 'key?' for false:FalseClass error notification appeared if you indicated an incorrect ODL password and clicked the Check connection button at the Edit SDN Manager page. 6.1

CORE-14878If you took a normal backup of a federated VS at the Backups page on the Buyer's side, the backup was not displayed at the Virtual Server's Backups page. 6.0-6.1 

CORE-14879When you accessed the details of failed actions from the federated VS Details page, the layout was distorted. 6.1 Edge 2-6.2 Edge 2

CORE-14880The color of the notification text background at the Notification Details page changed as you hovered over it. 6.1 Edge 2-6.1

CORE-14887It was typed Accesses instead of Addresses in the Edit Routed Network Pricing pop-up window at the vCD Pricing Rate Card page. 6.1 Edge 2-6.1

CORE-14888

Due to incorrect ssh parameters settings, you could contstantly see the corresponding warning messages in the /onapp/interface/log/onapp.err file. 

6.0-6.1 

CORE-14890After you imported a vCenter VS to OnApp and set a root password, the text in the Set Password pop-up window became Set password for virtual machine instead of Set current password for virtual machine6.0.0-196-6.2 Edge 1

CORE-14891When the vCloud VS was in suspended status, it was still possible to edit guest customization but the transaction failed.6.0.0-196-6.2 Edge 2

CORE-14896When you tried to create Windows-based VS with KMS licensing type enabled, the VS was successfully created but not activated and Windows activation popups were contantly displayed on the screen. 6.0-6.1

CORE-14902When you tried to create an OVA-based VS on CentOS 7 KVM compute resources, the transaction failed with the system error.6.0.0-196-6.1

CORE-14904Labels in the Add Event pop-up window at the New Subscription page were missing. 6.1 Edge 2-6.2 Edge 2

CORE-14911You couldn't assign an IP address to an Accelerator, Container server, Storage server, or Edge server at the Assign IP Address page as the corresponding popup did not load.6.0-6.1

CORE-14916If you selected Windows 2012 template and CloudBoot compute resource with the old type of provisioning during the baremetal server creation, the transaction failed with the system error.6.1

CORE-14919If you tried to run a recipe on a Linux-based vCenter VS without any IP addresses assigned, the transaction failed with a system error. 6.1-6.2 Edge 2

CORE-14945When you tried to allocate an IP address to a federated VS at the Assign IP Address page, it was allocated to a local VS instead of a federated one. 6.1

CORE-14963Irrelevant "initial_root_password" parameter was available in the output of Get VS Details API request for an application server.6.1 Edge 2-6.1

CORE-14970When you tried to schedule autobackups for a Windows VS at the VS Overview page, the popup window provided the hyperlink to proceed to the configuration, but the link was not highlighted. 6.1 Edge 2-6.1

CORE-14988You could not restore a recovery point for a Windows-based VS, if it required SSH access and had a recovery mode enabled.6.0.0-196-6.1

CORE-14990When you tried to add a new IP address to the VS at Virtual Servers menu, IPv6 filter was not working.6.0-6.1 

CORE-15020If you tried to create a load balancer of an autoscaling type with the Free RAM option enabled in Autoscale Out/In Parameters sections, the transaction failed.6.1 Edge 2-6.1

CORE-15035If you tried to restore a VS from recovery point, and the VS wasn't in the recovery mode, the transaction failed.6.1.0-240-6.1

CORE-15042When you tried to run a VBS or PowerShell script type recipe assigned to a VS, the transaction failed. 6.1 Edge 2-6.1

CORE-15062When you used an API request to enable/disable notifications, the API call failed with an error. 6.1 Edge 2-6.1

CORE-15066If you selected the option to display more than 10 items per page at the Integrated Storage Disks page, it wasn't applied. 6.1 Edge 2-6.1

CORE-15068If you added empty fields for custom recipe variables at the Recipes step of the VS creation wizard, the error notification appeared at the Confirmation step and the VS wasn't created. 6.1.0-240-6.1

CORE-15071After you deleted a user with assigned vApp via vCD, the vApp was not reassigned to you and the 500 Internal Error appeared at the vApp Details page in OnApp Cloud.6.0.0-80-6.1

CORE-15072The 500 Internal Server error appeared at the Snapshots page if you tried to delete or add note to a snapshot.6.2 Edge 1-6.2 Edge 2

CORE-15077When you tried to decrease a vDisk's size of an Integrated Storage data store, the actual size of the disk and the one indicated in the logs were different.6.0.0-196

CORE-15086If you logged in to your Control Panel via Firefox browser, the SSH keys at the SSH-Keys for Virtual Servers page were not displayed properly. 6.1

CORE-15087If you saved your Control Panel password to the browser auto-fill form data, and then tried to create a VS from ISO via the VS creation wizard, the doesn't match confirmation error appeared on the Properties step. 6.0.0-196-6.1

CORE-15088Some elements at the EC2 Instance Details page were inconsistent with the general page layout. 6.1

CORE-15089After you hid the sidebar menu with a custom logo set, the custom logo changed back to the OnApp default one. 6.1 Edge 2-6.1

CORE-15090After you performed a manual backup of an IS CloudBood VS, the arrow icon at the Backups page next to the backup in question was not aligned properly. 6.1

CORE-15091The Start Smart Server slider label on the Rebuild Smart Server pop-up window was cropped. 6.0.0-196-6.1

CORE-15092

The layout of the Backups and Price column labels at the User Profile page was distorted. 6.1 Edge 2-6.1

CORE-15096You could not see the Activity Log section on the Dashboard with the Show cloud dashboard permission disabled. 6.1 Edge 1-6.1

CORE-15098If you tried to set the network interface port speed limit to Unlimited for an Application server in the Application Server creation wizard, it was set to 10 Mbps instead. 6.1

CORE-15100After you navigated to >=130 page at the Locale page, the pagination at the Missing Translations tab disappeared. 6.1 Edge 2-6.1

CORE-15107After you enabled/disabled disk autobackups, the message in the confirmation notification was not decoded properly.6.0.0-62-6.1

CORE-15111When you tried to hot full migrate a CentOS7-based VS on KVM compute resource, the transaction failed with a system error. 6.1 Edge 2-6.1

CORE-15112When you tried to full migrate a VS from CloudBoot to static compute resource, the transaction failed with a fatal error. 6.1

CORE-15115If you sorted VSs by labels at the Virtual Servers page, the order changed back to the default identifier-sorted one as you navigated to another page. 6.0.0-196-6.1

CORE-15117A load balancer created on a Xen compute resource and the heartbeat service did not start up after the load balancer's creation. 6.0.0-196-6.1

CORE-15120A load balancer stopped working after a node reboot at the Load Balancer Details page. 6.0.0-196-6.1

CORE-15121If a label for a service add-ons included the word "label", the field for the service add-on label was left blank at the Assign Service Add-ons page. 6.1 Edge 1-6.1

CORE-15122When you added a service add-on with no recipes to a vCloud VS, the transaction failed.6.1 Edge 1-6.1

CORE-15123When you migrated a VS with an encrypted password from vCenter to KVM, the VS's password was updated to a random value.6.0.0-159-6.1

CORE-15124It was possible to add more than one NIC to the same network at the New Network Interface page. 6.0-6.1

CORE-15125It was not possible to create a vCenter VS with those data stores or networks assigned that were moved from their initial zones. 6.1

CORE-15126CPU Usage was displayed in GHz instead of GBs in vCloud Storage graph in the Statistics section on the Dashboard. 6.1

CORE-15129There was an option to detach a vCenter compute resource from a compute zone, even though it is implemented by default. 6.0.0-196-6.1

CORE-15131After you added recipe actions to the service add-on and tried to run recipe on a destination vCloud VS, the transaction failed with a fatal error.6.1 Edge 2-6.1

CORE-15132When you set a root password for a VS imported from vCenter, the data you indicated in the Password confirmation field in the Set Password pop-up window was ignored. 6.0.0-196-6.1

CORE-15133When you tried to set root password for a newly-imported vCenter VS, the label Leave Blank For Auto-generate was displayed in the password field.6.0.0-196-6.1

CORE-15135After you used the same SAML authentication to log in to several Control Panel accounts simultaneously, the 500 Internal Server Error appeared as you tried to log out from one of the accounts.6.0.0-196-6.1

CORE-15136The CloudBoot backup server NICs assigned to SAN at the Edit Hardware Devices page in OnApp 6.0 got unassigned after the upgrade to OnApp 6.1.6.1

CORE-15137If you tried to run a Performance Benchmark test for an IS datastore at the Data Store Details page, the transaction failed with a fatal error.6.1

CORE-15138The label of epoch mechanism slider included the word beta at the Edit Data Store page after moving epochs from beta mode. 6.1 Edge 1-6.1

CORE-15139When you tried to create partition on disks for a VS running on CentOS 6 compute resource, the VS performance was slowed down.6.0-6.1

CORE-15146If you tried to delete an Org network and create a new one connected to the same Edge Gateway simultaneously, both transactions failed. 6.0.0-196-6.1

CORE-15148If you scheduled deletion of >=2 routed Org Networks, only the first transaction was successful, and the second one failed with a fatal error. 6.0.0-80-6.1

CORE-15149

When you migrated a VS to another compute resource and exceeded its resources capacity, the transaction failed.

6.1 Edge 2 - 6.1

CORE-15158The 500 Internal Server Error appeared at the second step of the VS creation wizard if you didn't choose any template at the first step. 6.0-6.1

CORE-15161When you tried to create an Org Network with routed network type for a vCloud VS, the transaction failed with a fatal error. 6.0.0-6.2-6.1

CORE-15197

After you uploaded custom logo and favicon during editing a new theme in Look and Feel Settings menu, the corresponding fields shifted in the OnApp interface. 

6.1

CORE-15202The nameservers' labels  were formatted incorrectly in the infobox at the DNS setup page.6.1

CORE-15206Headers and footers were displayed incorrectly in the interface after you applied a theme with customized header and footer.6.1 Edge 2-6.1

CORE-15219After you configured the dates at the CDN Cache Statistics Report page, the calendar did not disappear when you tried to configure other parameters. 6.0.0-196-6.2 Edge 1

CORE-15220The 500 Internal Server Error appeared on the IP addresses tab at the Networking page on the Seller side if you tried to detach an IP address from a federated VS.6.0.0-238-6.1

CORE-15221You could not assign an IP address to a VS at the Assign IP Address page without the All actions on virtual server's IP addresses permission enabled. 6.1

CORE-15234Clicking the Suspend button at the CDN Resource Details page caused the relevant information in the infobox to disappear.6.1

CORE-15236You could not import a vCenter VS with >168GB of RAM to OnApp at the Import Virtual Server page. 6.1

CORE-15237If you tried to increase the size of a primary disk of vCenter Windows-based or OVAs-based VSs by 1GB or more, the transaction failed with a fatal error. 6.0.0-196-6.1

CORE-15244The Network Configuration section at the Resources step of the VS Creation wizard was temporarily auto-filled as you hovered over the sidebar menu. 6.2 Edge 1

CORE-15245The modified Windows icon was not centered at the VS details page for Windows-based VSs. 6.1.0-240-6.2 Edge 2

CORE-15260After you rebooted an Integrated Storage Static compute resource, the UpdateComputeResourceCpuConfiguration transaction failed. 6.1.0-240

CORE-15261If you tried to create a smart server on CentOS7 CloudBoot compute resource, the transaction failed. 6.1.0-240-6.2 Edge 1

CORE-15283The 500 Internal Server Error appeared after you deleted an accelerated VS from the Virtual Servers menu, if the inviCDN ID was missing on the Aflexi side or CDN service was not available. 6.1

CORE-15289When you tried to rebuild network for the VS built from the Windows template that did not support VirtIO virtualization, the transaction failed. 6.1 Edge 2-6.1

CORE-15303If Aflexi server stopped responding for any reason or CDN SyncRunner did not work properly, the CdnSynchronizationSupervisor: CDN service is temporarily unavailable alert was not displayed.6.2 Edge 1

CORE-15313The word "was" was duplicated in the notification box that appeared after you enabled WAF rules for an HTTP CDN Resource at the Web Application Firewall page. 6.1

CORE-15314If you cancelled a zombie transaction at the Logs page, it was displayed as failed instead of cancelled. 6.1

CORE-15340It was possible to delete a User Group associated with a vCD organization. 6.1

CORE-15341If you created a vCloud organization with automatic creation of a User Group associated with it, it was still possible to delete this User Group. 6.1 Edge 2-6.1

CORE-15342After you imported to OnApp a vCenter VS with 2 clusters connected to one DvSwitch, the networks and datastores of the imported VS were duplicated at the Network Zone Details and Data Store Zones Details pages respectively. 6.0.0-238-6.1

CORE-15343Sometimes, after import of two vCenter VSs to OnApp, deleting the last one and shutting down another caused increased CPU load and the transaction stuck.6.1

CORE-15345You could not increase RAM and CPUs for the vCenter VS even when you had enough resources in your Resource Pool due to incorrect calculation of free RAM for the VS.6.1

CORE-15346When you tried to access a CDN resource disconnected from API server at the CDN Resources page, the 500 Internal Server error appeared instead of an error notification.6.1

CORE-15350When you created a bucket and tried to add both access control and rate card sections to it at the same time, the transaction failed 6.1

CORE-15370After you imported some vCenter VSs to OnApp, some data related to the vCenter data store capacity was missing or not updated at the OnApp side.6.0.0-196-6.1

CORE-15371After you imported all of your vCenter VSs to OnApp, the RAM usage value displayed at the Compute Resource Details page was incorrect. 6.0.0-238-6.1

CORE-15388The Billing Details section labels at the User Profile page were not aligned properly. 6.2 Edge 1

CORE-15393When you tried to take a backup of a Windows-based VS running on a Cloudboot compute resource, the transaction failed with a fatal error. 6.0.0-238-6.1.0-240

CORE-15394If you tried to create an OVA-based vCenter VS in VS creation wizard, the transaction failed. 6.0.0-238-6.1

CORE-15418The 500 Internal Server Error appeared at the Hardware Info page after you added a custom field at the Custom fields page. 6.1-6.2 Edge 2

CORE-15429Help tooltip icon was missing at the Certificates step of Add Zone to federation wizard. 6.1-6.2 Edge 1

CORE-15433When you tried to add a compute zone with a newly-generated certificate to federation at the Compute Zones page, the transaction failed. 6.0.0-238-6.1

CORE-15436It was not possible to disable logo and favicon for a theme at the Edit Theme page. 6.0.0-238-6.1

CORE-15453The 500 Internal Server Error appeared when you tried to suspend a federated compute zone at the Compute Zones page. 6.2 Edge 1-6.1

CORE-15459When you cancelled the failover process transaction at the Compute Zone Failover page, the 500 Internal Server Error appeared.6.1 Edge 1-6.1

CORE-15471

It was not possible to rebuid and then boot the VS with the TRIM option enabled.

6.1.0-240-6.1

CORE-15475When you created a VS with the remote console password containing the "<", ">", or "&" symbols, you couldn't access the VNC console.6.1

CORE-15477

During editing CDN bandwidth limit in the bucket you received misleading warning message about the possibiity to set it to 0.

6.0-6.1

CORE-15485When you tried to create a federated VS, the transaction failed. 6.2 Edge 1

CORE-15486The Back to top button wasn't displayed correctly in the VS Creation wizard.6.2 Edge 1-6.2 Edge 2

CORE-15490When you tried to resize or build disks for Windows-based vCenter VS, the transaction failed.6.0.0-238 - 6.2 Edge 1

CORE-15498The 500 Internal Server Error appeared at the Custom Recipe Variables page if you tried to add a custom recipe variable to a template. 6.0.0-238-6.2 Edge 2

CORE-15495When you tried to assign an IP address to a vCenter VS, you were redirected to the Dashboard page and an error message appeared.6.1

CORE-15514The layout at the Federation tab at the Application Configuration page was distorted.6.2 Edge 1

CORE-15517When you tried to launch the Content Balance Check for a VS, the transaction failed with a system error.6.2 Edge 1

CORE-15529When you tried to create a VS without selected Instance Package, the error message at the Resources step of the wizard stated that the Instance Package did not exist rather than it was not selected.6.2 Edge 1

CORE-15540

Switching between different compute zones in the VS creation wizard at the Resources step did not reset CPU resources to the default values.

6.2 Edge 1

CORE-15541You could select the irrelevant for R1Soft backup plugin Advanced option in the Actions dropbox at the Backup Resource page. 6.1.0-240

CORE-15542After you hovered over the sidebar menu or changed the size of the browser window at the Resources step of the VS creation wizard, the CPU Sockets section disappeared. 6.2 Edge 1

CORE-15559Compute resources with less than 4 GB of RAM required for accelerator creation were displayed in the Compute Resource dropbox at the Resources step of the Accelerator creation wizard. 6.0.0-238-6.2 Edge 1

CORE-15564If you tried to full migrate a VS with two VS disks assigned and the source disk was migrated before the second disk, the transaction failed. 6.0.0-238-6.2 Edge 2

CORE-15565The text in an infobox at the Look and Feel Settings page contained grammar mistakes. 6.1.0-240

CORE-15566When you clicked the labels of the Disks r/w columns to sort the results at the Usage Statistics page, the results were not displayed in the correct order. 6.1-6.2 Edge 1

CORE-15567If you applied a theme with footer, the footer was not displayed correctly at the Virtual Servers page. 6.2 Edge 1

CORE-15573After upgrade to OnApp 6.1, you could not use the newly created CloudBoot compute resources and edit the existing ones.6.1

CORE-15568The 500 Internal Server Error appeared as you clicked the Save button at the Add New Role page when you tried to add a new role with all the necessary permissions enabled. 6.1

CORE-15578If you tried to hot full migrate a Windows-based VS to another compute resource, and there was no bridge created on the destination compute resource, the transaction failed with a fatal error. 6.1 Edge 2-6.1

CORE-15580The label of the Cloud Locations dropbox was cropped and its elements were not aligned properly at the Federated Zones page.6.2 Edge 1

CORE-15582If the Cloud Score number contained >2 digits , the elements in the corresponding cell at the Federated Compute Zones page were not aligned properly. 6.2 Edge 1-6.2 Edge 2

CORE-15586

The Reset zoom button was referred to as Show all button in the infobox at the CPU Usage page.  

6.2 Edge 1-6.2 Edge 2

CORE-15591If you tried to restore a backup for an OVA Windows-based VS, the transaction failed with a system error. 6.1.0-240

CORE-15599Some of the options in the dropboxes at the Application Server Details and Virtual Server Details pages were not aligned properly. 6.1-6.2 Edge 2

CORE-15604 If the VS creation transaction failed, it was displayed as Building at the Activity Logs page. 6.2 Edge 1

CORE-15615It was possible to set higher than 100% CPU priority minimal or default limit for Compute Zone at the Access Control page. 6.0.0-196-6.2 Edge 1

CORE-15626The 500 Internal Server Error appeared if you tried to create a vApp or edge gateway based on shut down vCloud VS. 6.0.0-159-6.2 Edge 1

CORE-15627If a vCenter Windows-based VS had 3 disks assigned, you deleted one of the disks and then tried to assign a new one, the transaction failed with a system error.6.0.0-196-6.2 Edge 1

CORE-15633If you tried to clone a vCenter OVA template with three NICs assigned, the transaction failed with a system error. 6.2 Edge 1-6.2 Edge 2

CORE-15634After you created a Linux-based VS from a template imported from vCenter, and then tried to add an IP address to this VS at the Assign IP Address page, the transaction failed.6.0.0-196-6.2 Edge 1

CORE-15637When you tried to add a schedule backup for a disk at the Add a New Schedule page, the Start Time dropboxes were cropped. 6.2 Edge 1-6.2 Edge 2

CORE-15650Limits for compute zones in buckets were displayed in gigabits (Gb) instead of gigabytes (GB) in the Edit Default Compute Zone resource pop-up window.6.2 Edge 1

CORE-15661It was possible to create several network interfaces with the same label for one VS.6.0.0-138-6.2 Edge 1

CORE-15672When you imported vCloud organization to OnApp, it was not possible to associate it with a user group that already had associated organizations, and thus use multiple vCD mode.6.1-6.2 Edge 1

CORE-15691It wasn't possible to change month for statistics generating at the Usage Trends page. 6.2 Edge 1

CORE-15694

When you had a bucket with service add-on but no recipe groups, you could still assign any of recipes in the cloud to this service add-on.

6.1-6.2 Edge 2

CORE-15707

It was possible to proceed to the Properties step without selecting the template at the Templates step when creating a federated VS in the wizard. 

6.0.0-238-6.2 Edge 2

CORE-15714Child groups in service add-on store were not aligned properly.6.2 Edge 1

CORE-15715The alignment of elements in the Pricing for Template Store and Pricing for Service Add-on Groups pop-up windows at the Rate card page was incorrect. 6.1-6.2 Edge 2

CORE-15722Measurement units for Memory and Disk size value were missing at the System Service Add-ons Report page and in Pricing for Service Add-on Groups section at the Rate Card page.6.2 Edge 1-6.2 Edge 2

CORE-15742If you set ext4 parameter to false in the VS template's database, it was not possible to set file system for a VS disk during its editing or creation.6.1

CORE-15747When you created a VS based on a vCenter template with 2 NICs assigned, the built VS had 1 NIC and 1 redundant disk instead of just 2 NICs. 6.2 Edge 1

CORE-15749If you tried to create a VS from Windows vCenter template with MAK license in VS Creation wizard, the transaction failed with an error. 6.2 Edge 1-6.2 Edge 2

CORE-15750Icons of both Windows and Linux vCenter templates were not displayed at the Template store page.6.2 Edge 2

CORE-15752When you selected the Linux OS option in the search dropbox at the Template Details page and clicked the search icon, the 500 Internal Server Error appeared.6.2 Edge 1

CORE-15759There were more than 3 digits after decimal displayed in tooltips of the charts at the end user Dashboard6.2 Edge 1-6.2 Edge 2

CORE-15768If you tried to create a VS from a vCenter template with two NICs assigned in VS Creation wizard, the transaction failed. 6.2 Edge 1-6.2 Edge 2

CORE-15769The limits and prices with precision  >=9 were saved incorrectly at the Access Control and Buckets pages.6.1-6.2 Edge 2

CORE-15775If you tried to submit Pricing for template Store or Service Add-on with no values set, no error message appeared. 6.2 Edge 1-6.2 Edge 2

CORE-15796If you removed a VS record on the R1Soft side, and then removed the corresponding VS on OnApp side, the transaction failed with a fatal error.6.1

CORE-15823If you tried to import the non-supported in OnApp edges with distributed routers from vCenter, the error message was too long and not informative. 6.2 Edge 2

CORE-15829If you created a VS based on the IP address assigned to a user, it was not possible to connect to the VS via SSH.  6.2 Edge 1

CORE-15833The Default Firewall Rules section was absent for the federated VSs at the Firewall Rules page. 6.2 Edge 1

CORE-15834The 500 Internal Server error appeared at the Firewall Rules page as you clicked the Save button after editing a firewall rule for a federated VS.6.1

CORE-15842After you have made any changes at NSX L2 VPN page and wanted to cancel changes, the Discard button did not work.6.2 Edge 1

CORE-15844If any transactions of vCloud or vCenter NSX components failed, there was no notification about it. 6.2 Edge 1-6.2 Edge 2

CORE-15846The 500 Internal Server Error appeared when you tried to save the changes after editing auto-backup preset in the Edit Auto Backup Preset pop-up window. 6.1.0-240-6.2 Edge 1

CORE-15860The misleading message about the VS reboot appeared in the Add IP Address pop-up window as you were assigning an IP address to a VS. 6.1.0-240-6.2 Edge 1

CORE-15866Virtualization type of a template was displayed as an array instead of text on the Template step of the Create federated VS wizard. 6.0.-6.2 Edge 1

CORE-15868As you clicked the Actions button in the Pricing for Template Store section at the Rate Card page, the dropbox was overlapped by the table border.6.2 Edge 2

CORE-15878After you edited CloudBoot backup compute resource, the Integrated Storage configurations on the corresponding backup server were reset. 6.1

CORE-15889If you tried to create a VS based on OVA template with OS type set as Other, the can't be blank, is invalid error appeared at the Properties step of the VS Creation wizard. 6.2 Edge 1-6.2 Edge 1

CORE-15910

When you zoomed the Virtual Servers page at 100%, a redundant scrollbar appeared at the right of the breadcrumbs area.

6.2 Edge 1

CORE-15926 The information in the help tooltip for Local Endpoint field in the Add IPSec VPN site pop-up window was misleading.6.2 Edge 2

CORE-15932You could not set initial password for a vCenter template if it was less than 12 symbols long and password complexity was enabled for the cloud. 6.2 Edge 1-6.2 Edge 2

CORE-15937After you configured the dates at the CDN Report pages, the calendar did not disappear as you clicked outside the calendar's area. 6.0-6.2 Edge 2

CORE-15945The Purge button overlapped the table border at the CDN Top Files Report page. 6.2 Edge 2

CORE-15946

The x_86 Architecture option was available though irrelevant for OVA templates with >=4 GB of RAM in the Convert to Virtualization pop-up window.  

6.2 Edge 2

CORE-15954The 500 Internal Server Error appeared at the Disks page when you tried to edit a secondary disk.6.2 Edge 1

CORE-15956

When you tried to clean dangling device mappers at the Integrated Storage Health Check page for a backup server, the transaction failed.

6.1.0-240

CORE-15969The tabs at the SDN Managers page were labeled Opendaylight [KVM] and NSX [VCENTER / VCD] instead of KVM and vCenter/vCloud respectively.  6.2 Edge 2

CORE-15970The vCenter label was displayed as VCenter one at the vCenter Edges and vCenter Edge Details pages. 6.2 Edge 2

CORE-15971The rule name was missing on the Manage Rules pop-up window at the NSX Firewall Service page. 6.2 Edge 2

CORE-15976If you ran provisioning of baremetal server based on CentOS 7.7 template, the transaction failed with a fatal error. 6.1-6.2 Edge 2

CORE-15978You could not select a network in the vCloud Edge Gateway creation wizard if its identifier started with network-.6.2 Edge 2

CORE-15980The tick indicating enablement of a compute resource was not aligned properly at the Compute Resource Details page. 6.2 Edge 1-6.2 Edge 2

CORE-15991It was impossible to edit a comment to a firewall rule at the Firewall Rules page for a federated VS.6.2 Edge 1-6.2 Edge 2

CORE-15993After the cold migration of the VS between compute resources with local storage, the VS's disk was corrupted.6.0.0-238-6.2 Edge 2

CORE-15994If you selected several NSX firewall rules, and then deselected some of those, the removal button above the table got greyed out.6.2 Edge 2

CORE-15995The warning about unsaved changes did not appear if you applied any changes at the Firewall or NAT tab and navigated to another tab. 6.2 Edge 2

CORE-15998The Save and Discard buttons were misplaced in the Add Application Rule pop-up window at the Load Balancers page.6.2 Edge 2

CORE-15999The fields in the Add Site pop-up window at the IPSec VPN site page were not aligned properly.6.2 Edge 2

CORE-16002Running rake nsx:resync:id task started resync of all NSX managers in the cloud instead of a specific NSX manager. 6.2 Edge 2

CORE-16005The scrollbar in the Networks list section in the Manage Source/Destination Rules pop-up window moved up every time you clicked any of the items. 6.2 Edge 2

CORE-16006If you tried to run vCloud guest customization script in OnApp, the transaction failed with an error. 6.1-6.2 Edge 2

CORE-16008Guest customization was disabled for a vApp deployed from a vApp template with guest customization enabled.6.1-6.2 Edge 2

CORE-16009An icon representing Limits for NSX Edges was missing at the Default Bucket Access Control page.6.2 Edge 2

CORE-16011А bucket wasn’t displayed at the Buckets page if it was created by a user under the role with restrictions on buckets by user group.6.1.0-240-6.2 Edge 2

CORE-16013The Apply to all NSX Edge resources in the bucket option was missing for an Edge Gateway as you edited limits for NSX edges in the Edit Resource pop-up window.6.2 Edge 1-6.2 Edge 2

CORE-16020If you created an application profile with TCP traffic type via API, and then tried to change the traffic type and edit other parameters of the application profile via interface, the transaction failed.6.2 Edge 2

CORE-16021The Cookie Name and HTTP Redirect URL fields in the Edit application profile pop-up window were empty even if you set specific values during creation of the application profile.6.2 Edge 2

CORE-16022

If an alert about CDN sync runner incorrect running was displayed in the cloud, the Back to top button in VS Creation wizard overlapped the alert. 

6.2 Edge 1-6.2 Edge 2

CORE-16025The values for the Owner and Instance Package fields at the federated VS Details page with >35 symbols were cropped. 6.0.0-238-6.2 Edge 2

CORE-16026An option to set price for a vCenter template was not available at the corresponding Rate Cards page.6.2 Edge 2

CORE-16027It you tried to perform resize without reboot while VS backup transaction was running, the reboot was still performed. 6.0-6.2 Edge 2

CORE-16029The No Recipe Groups label was misplaced at the Assigned Recipes page. 6.1.0-240-6.2 Edge 2

CORE-16030The last added pool member was still displayed on the NSX Load Balancer Pools list after you deleted it.6.2 Edge 2

CORE-16037If a user performed any backups or restores for a backup resource, they were not displayed at the user's Activity Logs page. 6.0-6.1

CORE-16040The 500 Internal Server error appeared at the NSX firewall page if you tried to close an infobox in the Add Firewall Service pop-up window.6.2 Edge 2

CORE-16043The NIC 0 Connection dropbox at the Resources step of the Deploy vApp wizard was overlapped by the table border as you expanded it, so you could not select the necessary option. 6.2 Edge 2

CORE-16045Measurement units for service add-ons group value were missing in Add/Edit Pricing for Service Add-on Groups section at the Rate Card page.6.2 Edge 2

CORE-16051The NSX Managers page was displayed in spite of the NSX feature sets being disabled in license. 6.2 Edge 2

CORE-16060The Add User Note button at the VS Details page was not aligned properly if the Any action with admin note permission was disabled. 6.2 Edge 2

CORE-16073The 500 Internal Server Error appeared at the Edge Details page after you imported from vCenter an edge that contained sub interfaces and was connected to org networks. 6.2 Edge 2

CORE-16076If you tried to run a recipe on a vCloud VS, the transaction failed with a system error. 6.2 Edge 1-6.2 Edge 2

CORE-16078Federated locations were displayed at the Hardware Info page in spite of having no content.6.1-6.2 Edge 2

CORE-16083The 500 Internal Server Error appeared when you tried to create a vCloud resource pool.6.2 Edge 2

CORE-16087The disk size of a federated VS at the Resources step of VS creation wizard was different than the minimum value specified in a template.6.1-6.2 Edge 2

CORE-16089The data about disks and NICs of federated VS was not displayed at the Billing Statistics page. 6.0.0-238-6.2 Edge 2

CORE-16090If you tried to create a vCenter VS with a hostname set to "." in VS Creation wizard, the transaction failed with a fatal error. 6.2 Edge 2

CORE-16092The prices for network usage and disks were displayed incorrectly at the Billing Statistics page.6.1-6.2 Edge 2

CORE-16099The 500 Internal Server Error appeared at the Resources step in VS creation wizard if you tried to create a vCenter VS from an Instance Package.6.1 Edge 2-6.2 Edge 2

CORE-16103When you tried to create vApp via API, the transaction failed with a system error.5.9-6.2

CORE-16107If VSP feature set was enabled, there were some redundant non-federated components available in CP.6.2 Edge 2

CORE-16112If you tried to cold migrate a VS disk and the corresponding VS was booted, the transaction failed.6.0.0-238-6.2 Edge 2

CORE-16114The layout of the Hardware Info for the backup server page was distorted. 6.1-6.2 Edge 2

CORE-16116 There was an HTML code excerpt displayed in the right Log Info pane at the Log Item Output page for the federated VSs. 6.2 Edge 2

CORE-16123If you tried to create a vCenter VS based on Windows 2012r2, the transaction stuck. 6.1.0-240-6.2 Edge 2

CORE-16129

The Autoscaling option was available though irrelevant for federated VSs in the Overview dropbox at the VS Details page.

6.1-6.2 Edge 2

CORE-16131The Federation::Trader::VirtualMachine label was displayed instead of the federated VS's label in graph tooltips on the Dashboard.6.1-6.2 Edge 2

CORE-16132When setting SSH key failed, the error message that appeared at the SSH-keys page did not contain the cause of the error. 6.1-6.2 Edge 2

CORE-16135If you tried to start up a Windows-based vCloud VS with the Automatically log on as administrator option enabled, the transaction failed with a fatal error. 6.1-6.2 Edge 2

CORE-16136If you tried to edit routed Org networks of an Orchestration Model with specified DNS, the transaction failed with a fatal error. 6.1-6.2 Edge 2

CORE-16138The Tools button was still displayed though non-clickable for a user with Update any/own Edge Gateway permissions disabled. 6.1-6.2 Edge 2

CORE-16139Layout of the Unlock My Account page was distorted. 6.1-6.2 Edge 2

CORE-16144The 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-16146

If you enabled Guest Customization during vApp composing or deployment, at the Summary step the Disable guest customization slider was still enabled by default. 

6.1-6.2 Edge 2

CORE-16148

If you tried to run a recipe on a vCenter or vCloud VS, the transaction failed with a system error. 

6.1

CORE-16150If you tried to create a VS based on a vCenter template using an Instance Package in VS creation wizard, the transaction failed with a system error. 6.2 Edge 2

CORE-16156The Quick Tutorial button appeared on the Dashboard though it didn't work with the new UI.6.1-6.2 Edge 2

CORE-16166

When you created a vCenter VS from OVA Windows-based template, you couldn't set the host for this VS.

6.0-6.1

CORE-16168When you deleted an owner of a VS with backup resource assigned, the backup resource could not be enabled on the VS with a new owner.   6.0.0-238-6.2 Edge 2

CORE-16169The Enable slider at the NAT page was displayed incorrectly. 6.2 Edge 2

CORE-16171Іf you tried to create a vCenter VS based on a Windows template with SNP service, the transaction stuck.6.0.0-238-6.2 Edge 2

CORE-16173

When you tired to create a virtual server based on the OVA template of the Other type, the transaction failed.

6.2 Edge 2

CORE-16185When you tried to create ten vCenter VSs in a row, the creation of some VSs failed with InvalidState error.6.0.0-238-6.2 Edge 2

CORE-16192When you tried to migrate a VS disk, the disk on the source VS was destroyed during the migration. 6.1.0-240-6.2 Edge 2

CORE-16195Labels were missing in the Scores and Benchmarks pop-up window that appeared as you clicked the Cloud Score icon for a specific zone at the Federated Zones page. 6.1.0-240-6.2 Edge 2

CORE-16196If none of infoboxes in your CP was hidden, and you hovered over the Restore infoboxes button at the User profile page, the button was displayed as clickable. 6.1.0-240-6.2 Edge 2

CORE-16204The Peer Subnets field in the Add IPSec VPN site pop-up window was labeled as Peer Endpoint.  6.2 Edge 2

CORE-16207It was possible to select an Instance package at the resources step in vCenter VS Creation wizard, even if the disk size of the selected template exceeded the Instance package disk size limit.6.2 Edge 2

CORE-16241If autoscaling for RAM and CPU was enabled, estimated price per hour for memory was doubled on autoscaling event.6.0.0-238-6.2 Edge 2

CORE-16263For user groups assigned to vCloud organizations, limit for maximum IP addresses was shared among all user groups in one bucket instead of being applied to each user group separately.6.1-6.2

CORE-16269If you try to migrate a vCloud disk between two datastores, the transaction failed with a system error. 6.1-6.2 Edge 2

CORE-16280The Next button didn't respond to clicking at the Cloud Locations step of the VS creation wizard. 6.2 Edge 2

CORE-16281The 500 Internal Server Error appeared at the User Group Report page if you tried to access it after generating a recovery point for a vApp owned by a user assigned to the aforementioned user group. 6.0.0-238-6.2 Edge 2

CLOUDBOOT-507

Updated the bnx2.ko NetXtreme II driver’s version to 2.2.6 to allow to set MTU to more than 1500. 

6.0-6.1

CLOUDBOOT-512Updated a kernel version to 2.6.32-754.23.1.el6.x86_64 for CentOS 6 KVM ramdisk to address the CVE-2019-14835 issue.6.0.0-238-6.2 Edge 2

CLOUDBOOT-515Updated the following components for CentOS 7 KVM ramdisk:
  • A CentOS version to 7.7.1908
  • A kernel version to 3.10.0-1062.1.2.el7.x86_64 to address the CVE-2019-14835 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-1062.1.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 

CLOUDBOOT-518

Updated the following components for CentOS 7 default ramdisk:

  • A CentOS version to 7.7.1908
  • A kernel version to 3.10.0-1062.1.2.el7.x86_64 to address the CVE-2019-14835 issue
6.0.0-238-6.2 Edge 1

CLOUDBOOT-521When you tried to hot migrate VS after upgrade to OnApp 6.1, the VNC display's port number was not reported with SNMP statistics.6.1 Edge 1-6.2 Edge 1

CLOUDBOOT-523
CLOUDBOOT-525
CLOUDBOOT-526
CLOUDBOOT-527
CLOUDBOOT-528
CLOUDBOOT-529


Updated the Xen version for CentOS 6 to 4.8.5.48.gc67210f60d-1 and for CentOS 7 to 4.10.4-2.el7 to address the following XSA issues:  296, 298, 299, 301, 302, and 303.


5.0 -6.1

CLOUDBOOT-535


Updated the Xen version for CentOS 6 to 4.8.5.77.gec6c25e467-1.el6 and for CentOS 7 to 4.10.4.28.ge4899550ff-1.el7 to address the XSA-306 issue.

5.0 -6.1

CLOUDBOOT-536
CLOUDBOOT-537

Updated the Xen version for CentOS 6 to 4.8.5.75.g4c666a7e15-1.el6 and for CentOS 7 to 4.10.4.26.gfde09cb80c-1.el7 to address the XSA-304 and XSA-305 issues.

5.0 -6.1

STORAGE-2092When you tried to reboot a compute resource with a VS with DRaaS enabled, the transaction failed.5.5-6.2 Edge 2

STORAGE-2184If you wrote to vDisks with online snapshots on CloudBoot compute resources with Integrated Storage.6.2 Edge 2

STORAGE-2185

When you tried to perform Storage Health Check performed on static backup servers with enabled Integrated Storage, the CleanDanglingDeviceMapper transaction failed. 

6.1-6.2 Edge 2

STORAGE-2193When you tried to repair VDisks with epochs enabled, the transaction failed.6.2 Edge 2

INSTALLER-471You could not start HTTPD service after you updated your Control Panel from OnApp 6.0 to 6.1 with High Availability enabled.6.0.0-238-6.1.0-240

STORAGE-2167When you tried to take a VDisk snapshot on static or CloudBoot compute resources with Integrated Storage enabled, snaptime field of snapshot got value from size of disk in sectors instead of actual creation time.4.1-6.1