Search Engine: Elastic

Article ID: 131553, created on Oct 3, 2017, last review on Oct 3, 2017

  • Applies to:
  • Operations Automation 7.0
  • Operations Automation 7.1
  • Operations Automation 7.2
  • Operations Automation 6.0

Symptoms

Second NG Cluster is being deployed.

The same storage device with different mount point is supposed to be used with the new cluster.

When adding new cluster in OA, the NFS mount point is being attached to the first cluster, instead of new one.

Cause

Storage node is registered in OA and is linked to the webcluster upon cluster creation.

When new cluster uses the same IP address, OA uses node's IP address entered, finds that the node is already registered and simply add new mount point to it.

The issue is acknowledged as POA-113260.

Resolution

Set up name resolution on MN and Web Server Nodes and use storage device's hostname to register the cluster.

0871c0b47b3b86ae3b1af4c2942cd0ce caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 1941880841f714e458ae4dc3d9f3062d 31987597efff5a3a9ce779cc203bbe5e 8c199f0ee4305da1a577740620df4a51 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF