Subordinate UVMS remains stuck in status 'Unregister pending...'
search cancel

Subordinate UVMS remains stuck in status 'Unregister pending...'

book

Article ID: 268283

calendar_today

Updated On:

Products

CA Automic Dollar Universe

Issue/Introduction

When a user tries to unregister/delete a subordinate UVMS from a Master UVMS, and the subordinates host is not reachable (either down or network issue) at this time, the Subordinate UVMS will remain permanently in a status 'Attente de désenregistrement'/Pending unregistering' .

This status is irreversibly blocking and will never change, even when the subordinate is reachable again.

Additional commands like the following are unable to change anything :

unidlt node -node UVMS_SUBORDINATE_NAME -type SUBMS

unidlt node -node UVMS_SUBORDINATE_NAME -type SUBMS -offline

unidlt LINK -type SUBMS -node UVMS_SUBORDINATE_NAME

In this situation it is impossible to remove the UVMS Subordinate from the Master configuration. 

 

Environment

UVMS 7.00.11 or 6.10.111 or inferior in Advanced Architecture.

Cause

DU_AS-7349

Resolution

Resolution:

Update to a fix version listed below or a newer version if available.

Fix version(s): 
Component: Univiewer Management Server (UVMS)
Dollar Universe 7.00.21 - Available
Dollar Universe 6.10.121 - Available

Workaround:

Running the 'uniderby' tool on the UVMS Master to update architecture_role of the impacted Subordinate UVMS.

The READONLY must has been set to OFF in the uniderby script beforehand

The name of the subordinate UVMS should be passed in the parameter name.

1. Stop the UVMS master
2. Backup the uvms database folder <uvms_folder>/data/data/uvmsdb
3. Modify the file /uvms_folder/app/bin/uniderby. Change the line:
    echo READONLY ON; >> %SQLFILE%
    to:
    echo READONLY OFF; >> %SQLFILE%
4. Launch the command uniderby to update the architecture role of the impacted Subordinate on the Master UVMS database:

uniderby -q "update uni_uv_nodes set architecture_role='SUBORDINATE' where name='UVMS_SUBORDINATE_NAME'"


5. Start the UVMS master

Remark: 

If the subordinate UVMS does not share his nodes, to avoid any problem with unregistering it from the master UVMS, the simplest and most secure way to achieve this will be an SQL statement submitted via the 'uniderby' instruction.
In the procedure described above in the Workaround section, replace step 4 with the following line:

uniderby -q "update uni_uv_nodes set architecture_role='SUBORDINATE',share_nodes=1 where name='UVMS_SUBORDINATE_NAME'"

Additional Information

Public Description: Algo change to avoid node status change when node is not reachable via 'unidlt NODE' command.
'unidlt LINK' command takes care of proper node deletion when node is not reachable.