These Release Notes (updated at 9:42 PM on 4/29/2021) are for everRun Release 7.8.0.0. See the following sections:
The following features are new in everRun Release 7.8.0.0:
Security Improvements:
For information, see New in everRun Release 7.7.0.0.
ZTC-3664: After performing a kit upgrade on a system running Release 7.4.3.2 to a later release, any guest volumes that leave less than 500 MB of space available on the logical disk will fail to mirror after performing a node replacement.
ZTC-3618: Provide a warning that appears when creating or importing a UEFI VM that a snapshot of it cannot be created. (Warning now exists.)
ZTC-3175: The Nessus scan identifies deprecated SSL protocols on port 5560. (The deprecated protocols have been removed.)
ZTC-3171: SSH Cipher settings do not pass all security scans. (Settings have been modified to increase security and to pass these scans.)
ZTC-3017, ZTC-2257: Users with special characters in passwords fail to join Active Directory (AD). (AD usernames and passwords that contain special characters such as “$”, “!”, “&” and “<” are now supported when logging into AD.
ZTC-2773: The lvmetad daemon has a known memory leak and has been deprecated. (The daemon has been configured to no longer run.)
ZTC-2427: A single processor in a dual socket motherboard does not have license support. (License support has been added.)
ZTC-2395, ZTC-2396: The Qualys scan fails QID 37839 and QID 38738. (SSH settings have been modified to be more secure and pass this scan.)
ZTC-2256: The mcelog package is not installed by default. (mcelog is now installed by default.)
ZTC-2206: The Qualys scan fails QID 13162. (The session cookie now includes the secure attribute, which allows this scan to pass.)
ZTC-2138: E-alert email does not show correct value for snapshot variable.
ZTC-1298: Windows guests experience performance issues due to lack of a hypervclock setting. (Windows 2016 and Windows 2019 guests performance issues have been addressed by adding the hypervclock setting to the configuration.)
ZTC-962: The Stratus-supplied SSL certificate has an expiration date of 2026. (A new certificate has been provided that expires 10 years from the date of release (for example, 2030). You must accept the new certificate; see During Upgrade, Refresh Browser and Accept New Certificate.)
ZTC-461: Unable to login to Active Directory after a primary node failover.
ZTC-458: Guests configured with boot priority order may fail to start.
ZTC-454: Root, swap, or diagdata may display as broken after a fresh install or node recover/replace.
ZTC-453: Generate an alert when guest startup fails.
For information, see Bug Fixes in everRun Release 7.7.0.0.
For a list of the CVE fixes, see Fixed CVEs.
Upgrade to everRun Release 7.8.0.0 following the upgrade path for the release that is running on your system, as listed in the table below.
| Release | Upgrade Path |
|---|---|
|
Releases 7.7.0.0, 7.6.1.0, 7.6.0.0, 7.5.1.1, 7.4.3.2 |
Upgrade directly to Release 7.8.0.0 following instructions in Upgrading everRun Software Using an Upgrade Kit. |
|
Releases 7.5.1.0, 7.5.0.5, 7.4.3.0, 7.4.2.0, 7.4.1.0, 7.4.0.0, 7.3.4.0 |
Upgrade to Release 7.6.1.0 first, and then upgrade to Release 7.8.0.0. For information on upgrading to Release 7.6.1.0, see the everRun Release 7.6.1.0 Release Notes and Help. |
|
Releases 7.3.2.0 and earlier |
Upgrade to Release 7.3.4.0 first, then to Release 7.6.1.0, and finally to Release 7.8.0.0. To upgrade to Release 7.3.4.0, see the everRun Release 7.3.4.0 Release Notes and Help. |
During an upgrade to Release 7.8.0.0, the browser may display the upgrade as stalled after the first node has been upgraded and become the new primary node. This incorrect browser display can occur if the browser has a new certificate from Stratus that needs to be accepted. You should refresh the browser and, if prompted, accept the new certificate. After you have accepted the new certificate, the browser displays the correct status of the upgrade.
For a list of the guest operating systems tested with the current release, see Tested Guest Operating Systems.
everRun 7.8.0.0 or higher features enhanced support for 512e storage, including:
In order to take advantage of this enhanced 512e support, see the following before installing or upgrading an everRun system:
To make 512e storage available when you are newly installing a system with everRun 7.8.0.0 or higher:
To make 512e storage available when you are upgrading an existing everRun system to 7.8.0.0 or higher:
For Windows-based guest operating systems only, download and update the VirtIO drivers as described in Updating the VirtIO Drivers (Windows-based VMs). At a minimum, you must update the storage drivers to support 512e volumes.
For more information about configuring or using 512e storage, see the following notes:
Windows Server 2008 and Windows Vista guest operating systems lack the required VirtIO drivers to benefit from 512e disk drives.
Windows Server 2008 R2 and Windows 7 guest operating systems require Service Pack updates and additional configuration changes to benefit from 512e disk drives. For full information, see Microsoft KB Article 2510009 at the following location:
Follow the instructions under Windows 7 and Windows 2008 R2. Also, as described under Known Compatibility Issues, resolve compatibility with fsutil.exe by adding the EnableQueryAccessAlignment property to the system registry.
The following AVCLI commands have been updated, or are new, to support 512e and 4K storage:
In everRun Release 7.8 or higher, the storage-group-info command is deprecated in favor of the new storage-group-info-v2 command, which displays more detailed information about the 512n, 512e and 4K disk types. If you have scripts that use the output of the original command, consider updating the scripts to take advantage of the new v2 command output.
After a Windows 2008 SP2 (32-bit) VM is created, the installation of the VirtIO serial driver fails. In this situation, you must install the driver manually. To do so, download the VirtIO ISO file from the Downloads page at https://www.stratus.com/services-support/downloads/?tab=everrun. Continue by following instructions in Updating the VirtIO Drivers (Windows-based VMs), though selecting the serial driver (vioser). Note that this problem does not occur with the 64-bit version of Windows 2008 SP2.
Guest volumes that are 2TB or greater in size and that become fragmented over time may significantly reduce guest performance. When volumes of this size are created, Stratus recommends that qcow2 be selected as the disk image format. The format qcow2, instead of raw, reduces performance slightly, but prevents the significant performance reduction seen with raw guest volumes of this size. For information on creating guest volumes, see Creating a Volume in a Virtual Machine.
Before migrating a PM or VM using a bootable P2V client (virt-p2v) ISO file, check if any removable media (for example, floppy disks, DVD drives, or external USB disks) are attached to the source image. If removable media are attached to the source image when you attempt to migrate a PM or VM, the error message Conversion failed appears. So, deselect the media in the virt-p2v window before starting the migration. To do so, access the virt-p2v window with the sections Target properties and Fixed hard disks, and then beneath Fixed hard disks, uncheck the box in the Convert column next to the removable media. See Migrating a Physical Machine or Virtual Machine to a System, particularly the section To migrate a PM or VM to the ztC Edge system, for more information on using virt-p2v.
When a system running everRun Release 7.4.3.x has a VM running Windows Server 2016 with an open console session, and you upgrade the system to Release 7.8.0.0, the console session displays Guest has not initialized the display (yet) and cannot open correctly. To correct the problem, shutdown and then restart the VM, and re-open the console session.
When you import a VM using the Import/Restore Virtual Machine wizard, the maximum length of the path to the VM, including the VM name, is 4096 characters for the import options Import from remote/network Windows Share(CIFS/SMB) and Import from remote/network NFS.
If you begin to import an OVA file and then the node is placed into maintenance mode or loses power, the OVA import fails, and any future attempt to import an OVA file fails. For information on a work-around for this problem, see KB-10035.
Importing a Linux VMware OVA file changes the network interface and networks-scripts file. After you import the file, you need to manually configure the network information using the following procedure:
On the Virtual Machines page, select the VM.
Click Console in the bottom panel to open the VM login page (for additional information, see Opening a Virtual Machine Console Session).
Login into the VM.
Open a command prompt window.
Issue the ifconfig command. In the command output, check if ip address is assigned to the virtual network interface eth0.
If ip address is not assigned to eth0, list the contents of the /etc/sysconfig/network-scripts directory.
Note the value of ifcfg-xxxx (though not ifcfg-lo).
Rename ifcfg-xxxx to be ifcfg-eth0.
Edit the ifcfg-eth0 file, changing the values of DEVICE and ONBOOT, as follows:
Save the file.
Issue the following command to restart network services:
Verify the IP assignment by issuing the command ifconfig. In the command output, confirm that ip address is assigned to eth0.
When you select Import from USB in the Import/Restore Virtual Machine wizard to import an OVA file, you can enter a file name or partial file name in the Search Files box. The box lists OVA files that have names matching the name entered in the box, and that reside in various directories:
For complete information on importing an OVA file, see Importing an OVF or OVA File.
You cannot import a VM running RHEL 8.1 (with BIOS boot firmware) from a VMware ESXi 6.7.0 server to a everRun system.
You can recover or replace a PM from a temporary Preboot Execution Environment (PXE) server on the primary PM. After the procedure is complete, the Size Available, Size, and Size Used columns of a Storage Group display zero in all three columns, with the following selections in the PXE procedures:
This is a display problem. The actual size in the system is accurate. To correct the display, re-assign the disk to the storage group.
On the Virtual Machines page of the everRun Availability Console, you can open a VM console session to display the console of the guest operating system running in the VM. When you open a console session to access a guest VM with a UEFI boot type, the console session has a maximum resolution of 800x600. For a higher resolution, connect to the VM using a Remote Desktop Connection.
After a system is upgraded from Release 7.6.1.0 (or earlier) to Release 7.8.0.0 using an upgrade kit, support for vmgenid on VMs running Windows Server 2019, Windows Server 2016, or Windows Server 2012 is not present until after the VMs are restarted. Therefore, you must restart such VMs to enable vmgenid support after the upgrade. If you are upgrading from Release 7.7.0.0, you do not need to restart such VMs if they had previously been restarted on the system running Release 7.7.0.0.
When you are using Microsoft Edge as the browser for the everRun Availability Console you cannot create a VCD: the process will fail. Instead, use another compatible browser (see Compatible Internet Browsers).
When importing a VMware VM, you must shutdown the VM using operating system shutdown commands in addition to powering it off from the VMware console. If you shutdown the VM using only the VMware console, the import will fail.
The mapping of the Japanese keyboards 106 and 109 may be incorrect when using IE10, IE11, or Firefox to access the everRun Availability Console. Use Chrome or remote connection software (VNC or RDP), instead.
A Windows 2016 VM with the maximum supported number of vCPUs and the maximum amount of memory will not reboot cleanly. To avoid the problem, reboot the VM using the Shutdown button (on the *Virtual Machines* page, in the bottom pane for the VM), and then restart the VM using the Start button. To avoid the problem, reduce the number of vCPUs or the amount of memory assigned to the VM.
If you are connected to the everRun Availability Console using an https URL in a Microsoft Internet Explorer or Mozilla® FireFox® browser, and you click Console after selecting a running VM from the Virtual Machines page, the message VNC: Unable to connect, retrying in n seconds may appear. To enable the VNC connection, click the https link to the VNC console page in the upper right-hand corner of the masthead, and continue with the appropriate procedure below (procedure in your browser may differ, depending on the version of your browser):
In Internet Explorer, the Security Alert wizard appears:
In FireFox, the Your connection is not secure window appears:
Click Confirm Security Exception.
The VNC console appears.
When you remove a snapshot on an everRun system, the system must coalesce the snapshot by merging it with the next oldest snapshot. While the system is coalescing snapshots:
A user cannot start the VM associated with the snapshot(s) if the VM is currently stopped. The Start button is temporarily unavailable on the Virtual Machines page of the everRun Availability Console. So, if you need to delete a snapshot, do so while its associated VM is running, or allow the associated VM (if stopped) to remain stopped.
A user must not shutdown a VM associated with the coalescing snapshot(s). You must not shut down the associated VM from the guest operating system because doing so causes data corruption. You cannot shut down the VM using the everRun Availability Console because the console prevents you from doing so.
Avoid removing snapshots if you have an immediate need to perform any of these operations. After you remove a snapshot, wait at least 10-15 minutes before attempting any of these operations, or retry the operation if needed. You may need to wait much longer depending on the size of your volumes, the amount of VM activity, and the number of snapshots you remove.
For information about how to monitor coalescing operations that are underway, see KB-4272.
The system cannot create application-consistent snapshots of VMs running Windows 2008 (32 bit) and Windows 2003 (32 bit). The system can create only crash-consistent snapshots of VMs running these operating systems.
When you change the IP address or netmask settings of a node as described in Configuring IP Settings, both the old and new settings are in effect until you reboot the node. Having both settings active may cause routing or connection issues.
Beginning in Release 7.6.0.0, Help is available in German, Japanese, Chinese, and Portuguese
The Stratus Customer Service Portal provides a searchable Knowledge Base with technical articles about all Stratus products, including everRun. In some cases, the Release Notes directly reference these Knowledge Base articles (for example, KB-nnnn). You can access the Customer Service Portal and the Knowledge Base articles by using your existing service portal credentials, or by creating a new user account, as follows.
To access the Knowledge Base
Log on to the Stratus Customer Service Portal at https://support.stratus.com.
If needed, create a new account as follows:
Enter your company email address and contact info, and click Register.
Your company email address must include a domain name (for example, stratus.com) for a company that is a registered customer of Stratus.
If you need assistance creating an account, contact your authorized Stratus service representative.
In the Keyword Search box, enter keywords associated with the information you need, and then click Search.
To search for an article by its KB-nnnn number, click Advanced Search. Next to Search by ID, type the article ID number (nnnn) and click Display.
If you have a technical question about everRun systems, you can find the latest technical information and online documentation at the Downloads page at https://www.stratus.com/services-support/downloads/?tab=everrun. You can also search the Knowledge Base in the Stratus Customer Service Portal at https://support.stratus.com.
If you cannot resolve your questions with these online resources, and the system is covered by a service agreement, contact your authorized Stratus service representative. For information, see the everRun Support page at https://www.stratus.com/services-support/customer-support/?tab=everrun.
Product Support and Downloads