"Unknown node" error while trying to migrate cluster resource

  • 7009682
  • 02-Nov-2011
  • 26-Apr-2012


Novell Cluster Services 1.8.8
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3
Novell Business Continuity Clustering 1.2.2
Cluster resource is enabled for BCC.


Trying to migrate a cluster resource through iManager to the remote cluster and the resource never comes online.  
The "/var/log/messages" file shows the following error:  kernel: Unknown node: =173.


You can manually online the resource with the "cluster online<resource name>" command once the resource is marked primary on the destination cluster.

You may workaround the problem by using the command line interface to migrate the resource and specifying the remote cluster node which to online the resource.
Example:  CLUSTER MIGRATE <source cluster>/<resource name>  <destination cluster>/<node name>

Fix has been checked in and will be released in next OES 2 SP3 maintenance update. 

Additional Information

A change was made in the clustering code "novell-cluster-services" (released in OES2 SP3 August Maintenance patch release) which affects a BCC cluster resource migration.

When BCC sends the command to NCS to migrate a resource, it passes the Resource Name and an NCS:Revision number but does not specify a node to online the resource.  It relies on the "preferred nodes list stored for each cluster resource.  The error"Unknown node: =173" references the NCS:Revision number on the cluster resource so this number will be unique for each resource which it's attempting to migrate.