Roving Edge Infrastructure 2.0.3

Roving Edge Infrastructure 2.0.3 contains the following product enhancements:

• Improved performance by increasing the health check interval of Roving Edge Infrastructure services.
• Increase import image workflow timeout for very large boot volume images.
• Update rpm and kernel versions to the latest version of the Roving Edge Infrastructure device operating system.
• Added support for special characters in the serial console password.
• Improved system update scripts.
• Allow adding of free form tags when creating block volumes.
• Add validation and connectivity checking when setting up the network and domain name server (DNS).
• Verify valid destination paths for all downloads before they occur and block downloads to invalid destinations.
• Provide a diagnostic tool to calculate and write the percent complete field to the database.
• Improved logging to include more detailed information.
• Pack DHCP, HTTP, and TFTP images in a single file.
• Removed shell scripts and migrate the functionality into Python.
• Support image export to bucket support in Blockstorage Controlplane (Ceph).
• Add negative tests to get the coverage up by over 10%.
• Support instance cloning on LVM.
• Modify existing GET and PUT APIs on the subnet in VCNDP to retrieve and configure default GW for a given subnet.
• Added display of existing subnets and their respective default GWs through the serial console.
• Refactor unlock node/passphrase change/encryption key workflow.
• Support creating an image from an existing instance.
• Upgraded Delete API
• Propagate DNS Configuration Across Cluster in Serial Console.
• Upgraded the Roving Edge Infrastructure device operating system to UEK6.

Roving Edge Infrastructure 2.0.3 fixes the following issues:

• Launching an instance launch workflow fails while attaching a remote boot volume.
• Health checks fail due to insufficient timeout length.
• Services restart while running compute workloads.
• Identity data-plane service fails even when the system passes health checks.
• Services do not start when running a factory reset from the serial console.
• The system upgrade download option reports false errors when the upgrade is actually successful.
• System upgrade node API structured log not escaping double quotes.
• Reduce retries and increase retry interval for remote boot volumes.
• If port1 for the node IP is used, the instances on that node will not be reachable by the IGW on that node.
• Hardcoded credentials in system upgrade node API
• The node not rebooting after an online upgrade.