Known Issues for Roving Edge

Details

This issue only applies when you're trying to recover the serial console passphrase with Auto Unlock enabled.

To lock a device, you must reboot it. With Auto Unlock enabled, the device automatically unlocks upon reboot. To disable auto unlock, you must enter the passphrase which was lost. Therefore, if a device has Auto Unlock enabled, it isn't possible to recover a passphrase.

Workaround

1. If you need to recover the passphrase, upgrade the Roving Edge device software to version 2.18.8 or higher. See Roving Edge Device Software Version Management.

2. Before the device reboots and locks the screen, use the serial console to disable Auto Unlock as described in Managing Auto Unlock.

3. Recover the passphrase. See Recovering Your Roving Edge Infrastructure Device After Shredding the Master Key.

Note

Roving Edge software to versions are released to realms at different times. If version 2.18.8 or later isn't available in your region, contact Oracle.

Details

This issue applies to Edge Installer versions 1.6.21 and 1.6.23.

When you use the Edge Installer to Download and Install Software there's a small chance that excessive logs will fill up the disk space and cause the software download process to fail.

A factory reset doesn't free up the disk space.

Workaround

1. In the Edge Installer menu, select Advanced Operations, then select Check for Configuration Interface Software Updates.

2. After the update is finished, reboot the device.

   Note: Don't run Check for Configuration Interface Software Updates again. If you do, reboot the device again.

3. Restart the self-provisioning process as described in Self-Provision the Device.

Note

Roving Edge software to versions are released to realms at different times. If version 2.18.8 or later isn't available in your region, contact Oracle.

Details

In the 2.18.6 release, if you factory reset a device and choose to preserve objects, the reset might display a credential error.

Workaround

1. If possible, back up the device Object Storage data to your OCI Object Storage. See Roving Edge Infrastructure Data Synchronization.
2. Factory reset the device again, and don't select to preserve objects. See Resetting Devices.

Details

As of version 2.18, the following error might be displayed when you reboot or power cycle a device:

Version          : *** Unknown ***System Time UTC     : 2025-08-28 18:14:31
Boot Time                  : 2025-08-28 17:39:18
Device Serial Id           : Unexpected Error!
Unlock Status              : Unexpected Error!
Auto Unlock Status         : Unexpected Error!
Diag Mode                  : *** Unknown ***
Red API Services Status    : *** Unknown ***
Red HW Services Status     : *** Unknown ***
Press ENTER to return... 

Workaround

Reboot the device until the error is no longer displayed. See Rebooting a Device.

Details

The Proxy URL setting in the Roving Edge installer isn't working. If you set a proxy URL during self-provisioning, the Roving Edge installer must be reset to recover.

Depending on your situation, perform one of the following workarounds:

Avoid the issue: Prior to self-provisioning a Roving Edge device, follow these guidelines:

• Ensure that the device isn't behind an HTTP proxy server and has internet connectivity.

• When you self-provision the device, don't specify a proxy URL. See Configure Device Networking.

Workaround: If you started to self-provision a Roving Edge device and received an error similar to the following error:

OCI connectivity is OK!
..............................................................................................
Failed: Connect to OCI Failed. (MaxRetryError("OCIConnectionPool(host='<uniqueiID>.oraclecloud.com', port=<port-no>): 
Max retries exceeded with url: /<version>/roverNodes/ocid1.rovernode.oc1.<uniqueID> (Caused by NewConnectionError('<oci.base_client.OCIConnection object at <uniqueiID>>: 
Failed to establish a new connection: [Errno 101] Network is unreachable'))"), 'Request Endpoint: GET https://rover.<region>.oci.oraclecloud.com/<version>/roverNodes/ocid1.rovernode.oc1.<uniqueiID> 
See https://docs.oracle.com/en-us/iaas/Content/API/Concepts/sdk_troubleshooting.htm for help troubleshooting this error, or contact support and provide this full error message.')
Registration failed. Retry 6) Register Device to OCI, or contact Oracle Support.

Reset the device to factory defaults and repeat the self-provisioning process:

1. In the self-provisioning menu, enter CTRL-C until you're back to the main menu:

   Roving Edge Basic Configuration Interface - Roving Edge Classic (ver. 1.6.37)
   Number selects a menu item, Enter accepts the selection, Ctrl+Z refreshes the menu, Ctrl+C returns to main menu, Backspace deletes a character.
   
   1) Configure Networking
   2) Set Up OCI Connectivity
   3) Set Up Credentials
   4) Install Platform Image
   5) Advanced Operations

2. Enter 5 to select the Advanced Operations menu.

3. Enter 3 to select the Factory reset Configuration Interface.

4. Enter factoryreset, then enter the reset passphrase: Oracle_Rover_Reset_1!

   The device resets to factory defaults then reboots.

5. After the device reboots, ensure that the device isn't behind a HTTP proxy server and has internet connectivity.

6. Self provision the device, and don't specify a proxy URL. See Self-Provision the Device.

On Roving Edge devices running version 2.16.2, when a block volume is shared with more than one instance, the shared block volume might get stuck in an ATTACHING state, then change to a DETACHED state.

Details

Any shared block volume attached to an instance that was created before version 2.16.2 remains attached and isn't affected by this issue.

Any shared block volume attached to an instance that's created on version 2.16.2, will be stuck in an ATTACHING state and eventually reach a DETACHED state.

Workaround

We're working on a resolution.

An Oracle Linux 9 instance might take longer than 4 minutes to boot.

Workaround

1. In the instance, run the following command to check if the bootloader entry contains a netroot setting that's set to an iscsi target:

   grep "netroot=iscsi" /boot/loader/entries/*$(uname -r).conf

2. If the command returns any result, remove the netroot option from the bootloader entries using this command:

   sed -i 's/netroot=iscsi:[^ ]\+ / /' /boot/loader/entries/*.conf