none
moved headnode to a different domain RRS feed

  • Question

  • We had our blades and the headnode in different domains, we were getting some strange issues - so we moved the headnode into the same domain as the blades. Now when I set nodes to an offline state or delete or reassign a node template I get these errors. 

    could not contact the node <headnode name> to perform the change. Authentication failed, the server has rejected the client credentials

    could not contact the node <headnode name > The management service was unable to connect to the node using any of the IP address resolved for the node

    does anyone have any ideas?

    Monday, May 2, 2016 4:31 PM

All replies

  • The headnode entry in the cluster manager has the old domain as in the network properties for the node... is there any way to change that? Besides a reinstall of the headnode. 

    Thanks. 

    Monday, May 2, 2016 5:22 PM
  • Hi,

        It is not supported to move the headnode to a different domain.


    Qiufang Shi

    Tuesday, May 3, 2016 7:47 AM