Error Message :
When launching the command "unims -checkms" on the nodes with the "Connected with warning" status, an error with code 200 was returned.
The job runs of the nodes cannot be displayed, as the console launched an error saying that the access is denied
On the UVMS subordinate, this kind of errors appeared after having launched the unisync node command:
|ERROR| request-worker-9 | com.orsyp.central.nodestatus.extractor.ProductNodeStatusCache | createNodeStatus error, Node info is null
|ERROR| request-worker-9 | com.orsyp.central.jpa.UniObjectMolester | Cannot set id field on class:class com.orsyp.central.jpa.jpo.NodeInfoEntity
Patch level detected:Dollar Universe 6.7.01
Product Version: Dollar.Universe 6.7.01
Description :On a configuration with an UVMS Master and an UVMS subordinate, having the nodes declared on both the master and subordinate, it was impossible to access DUAS nodes after having launched unisync node on the Master and Subordinate UVMS.
The nodes appeared with status Connected with warning on the master uvms.
The job runs of the nodes cannot be displayed, as the console launched an error saying that the access is denied.
Root Cause: The problem was caused by the fact that the hostname of the UVMS Subordinate was not recognized on the nodes / DNS, therefore they could not connect to it and the UVMS could not push the security properly to the nodes.
In order to fix completely this kind of synchronization / security issues with the nodes registered on the UVMS:
1. Add on the DNS the hostname used to install the Subordinate / Master UVMS, so that the command nslookup "hostname_of_the_uvms" works fine.
If you can't, add manually the lines on the hosts file of the DUAS servers.
2. When this operation is performed, you should launch a Full Synchronization of the nodes -> via univiewer console , click on Update on the nodes, then click on Full Synchronization.
In case the button is greyed out, register the node again on the UVMS.
Fix Status: Released
Version: Dollar.Universe 6.7.01