OvmError: 'Unable to add server as an admin to the ZFS San Server.'

(Doc ID 2086677.1)

Last updated on FEBRUARY 09, 2016

Applies to:

Private Cloud Appliance - Version 2.0.1 to 2.0.5 [Release 2.0]
Information in this document applies to any platform.

Symptoms

During initial setup, some compute nodes are found in the "Unassigned Server" folder in Oracle VM Manager, and while trying to add them to the serverpool manually, the following error was returned:

 [part of the error message is shown below]

[ERROR (server_setup:626) Error while adding server
to SAN. ILOM MAC: 00:10:e0:65:30:f5. Marking node as dead.
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/ovca/server_setup.py", line 622, in
ovmm_add_server_to_san
    raise OvmError('Unable to add server as an admin to the ZFS San Server.')
OvmError: 'Unable to add server as an admin to the ZFS San Server.'
]

 

 When we check the status of that node, it is seen as Dead:

e.g:

[root@ovcamn05r1 ~]# pca-admin list compute-node

Compute_Node  IP_Address    Provisioning_Status  ILOM_MAC            Provisioning_State 
------------              ----------       -------------------          --------                   ------------------ 
ovcacn08r1    192.168.4.15  RUNNING              00:10:e0:65:2f:b7          running 
           
ovcacn14r1    192.168.4.8   DEAD                     00:10:e0:65:48:2f   dead   
           
ovcacn26r1    192.168.4.13  DEAD                    00:10:e0:65:30:f5   dead   
           
ovcacn13r1    192.168.4.14  RUNNING              00:10:e0:62:91:c3   running 
           
ovcacn10r1    192.168.4.10  RUNNING              00:10:e0:65:2f:cf   running 
           
ovcacn30r1    192.168.4.6   RUNNING              00:10:e0:40:cb:59   running 
           
ovcacn12r1    192.168.4.7   RUNNING              00:10:e0:65:31:31   running 
           
ovcacn11r1    192.168.4.16  RUNNING              00:10:e0:65:2f:c3   running 
           
ovcacn28r1    192.168.4.11  RUNNING              00:10:e0:62:31:81   running 
           
ovcacn29r1    192.168.4.9   DEAD                 00:10:e0:31:49:1d   dead   
           
ovcacn09r1    192.168.4.5   RUNNING              00:10:e0:65:2f:3f   running 
           
ovcacn07r1    192.168.4.12  RUNNING              00:10:e0:62:ca:09   running  

 

In this case, the compute nodes ovcacn14r1, ovcacn26r1,  and ovcacn29r1 faced this issue.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms