2.1 Changes and Improvements in Release 1.0.2

Oracle Virtual Compute Appliance X3-2 Release 1.0.2 is a maintenance release. This section describes functional changes, improvements and bug fixes compared to the previous release.

Compute Node Provisioning

Release 1.0.2 is a mandatory update of the Release 1.0.1 software stack installed during manufacturing. It enables the provisioning of compute nodes once the appliance is installed and updated on-site. A number of enhancements and bug fixes add more robustness and better serviceability of the functionality offered in this release.

Bugs Fixed in Release 1.0.2

The following table lists bugs that have been fixed in Oracle Virtual Compute Appliance X3-2 Release 1.0.2.

Table 2.1 List of Fixed Bugs

Bug ID



Dashboard does not support simultaneous users

Multiple users can now log in to the Dashboard UI simultaneously without issues.


Appliance is connected to data center network but external connectivity fails

Both tagged and untagged VLAN traffic is supported for virtual machine networking. Next-level data center switches must be configured accordingly, as described in the section Configuring Data Center Switches for VLAN Traffic of the Oracle Virtual Compute Appliance X3-2 Administrator's Guide.

VLAN traffic is not supported for management node external networking.


DNS configuration cannot be modified due to field validation error

Field validation has been corrected. DNS entries can be removed from the user-configurable network settings in the Dashboard UI.


Inconsistent password change behavior in Dashboard

Password changes through the Dashboard UI are applied as designed in a reliable and consistent way.


Dashboard login screen reports no error for invalid credentials

Error messages are displayed when a user attempts to log in with an incorrect user name or password.


Network configuration update is not applied; Dashboard UI provides no feedback

User-configurable network settings are applied as designed in a reliable and consistent way. The Dashboard UI does not reload until the services affected by the configuration changes have restarted.


Applying the dummy network configuration from the Quick Start Poster breaks rack connectivity

IP addresses are verified before they are applied. Internally used subnets and reserved addresses are rejected.


Choosing Network in Network View causes Java exception

The exception – which had no adverse effects – no longer appears.


Virtual machines are assigned to compute nodes in initializing state

Oracle VM does not allow compute nodes to join the server pool before they are completely provisioned and ready to use. If a compute node fails after joining the server pool, Oracle VM is unaware of the failure. This is considered normal behavior and is not harmful to the physical or virtual environment. If the issue is not resolved automatically by Oracle VM and the virtual machine will not start, you can log into Oracle VM Manager and move or migrate the virtual machine to a correctly operating compute node.


Updating network configuration fails due to field validation error

Field validation has been corrected for all user-configurable network settings in the Dashboard UI.


Backup functionality unavailable in Dashboard

The Backup tab has been removed from the Dashboard UI. Built-in backup functionality is based on a cron job. For more information about backing up your data and recovering after a component failure, user error or full system failure, refer to the Oracle technical white paper entitled Oracle Virtual Compute Appliance Backup and Recovery Guide.


Restarting management node network service causes Oracle VM server pool to go offline

Manual intervention to restart networking on any node is only necessary in rare situations. This is documented in the section Oracle VM Server Pool Is Offline After Network Services Restart of the Oracle Virtual Compute Appliance X3-2 Administrator's Guide


Oracle Virtual Compute Appliance Dashboard unavailable when logged in to Oracle VM Manager

The order in which you log in to both user interfaces no longer affects their availability. Both may be used side by side.