B Issues with the Oracle Database Appliance DCS (odacli) Stack

The following are known issues deploying, updating, and managing Oracle Database Appliance DCS stack:

• When deploying the appliance without databases, the default password changes
  When deploying the appliance without creating a database, the default password changes.
• DCS-10001: Fail to run GI configtools
  When deploying the appliance with VLAN, the GI configtools fail to run.
• DCS-10001:Internal error encountered: Fail to discover disk groups
  Disk groups are not discovered when deploying an appliance with 19 SSD disks.
• DCS-10045:Validation error encountered: Error retrieving the cpucores
  When deploying the appliance, DCS-10045 error appears. There is an error retrieving the CPU cores of the second node.
• Deployment might fail with status code 400: Unable to process JSON
  In some cases, the deployment in the Web Console fails with status code 400: Unable to process JSON.
• The output for the installed and available versions is not accurate
  The output is not always accurate for the commands odacli describe-component and odacli describe-latestpatch
• Unable to create a test alert with internal Oracle ASR
  Unable to create a test alert for Oracle Auto Service Request (ASR) that is configured with SNMP version 3.
• The command irestore-database fails if the directories are not created
  Unable to restore a database that is using Oracle Automatic Storage Management Cluster File System (Oracle ACFS) storage unless another Oracle ACFS database is in the system.
• Error DCS-10001: Unable to restore an SE database
  When using the command odacli irestore-database with an existing Standard Edition database home, the command fails with the error DCS-10001:Internal error encountered: enable block change tracking.
• The command odaadmcli expand fails due to a segmentation fault
  The command odaadmcli expand fails to run and due to a segmentation fault.