none
Unable to provision new compute nodes RRS feed

  • Question

  • Hello, I have connected compute nodes to my HPC cluster. I applied the compute node template and when I try to bring them online, the status remains as 'provisioning'. I am able to <g class="gr_ gr_176 gr-alert gr_spell gr_inline_cards gr_disable_anim_appear ContextualSpelling ins-del <g class="gr_ gr_14 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="14" id="14">multiReplace</g>" data-gr-id="176" id="176">rdp</g> into each of these nodes and they are connected to my domain.

    WIN-IDLT2GCSV25 Provisioning Transitional ComputeNode Template ComputeNodes

    Upon examining the provisioning log, I found the following issues:

     

    Time Message
    8/15/2017 11:21:54 PM Checking the configuration of node numerica\WIN-IDLT2GCSV25
    Time Message
    8/15/2017 11:22:15 PM Could not contact node 'WIN-IDLT2GCSV25' to perform <g class="gr_ gr_49 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="49" id="49">change</g>. Connection Failed. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 172.31.10.4:6730
    Time Message
    8/15/2017 11:22:15 PM Could not contact node 'WIN-IDLT2GCSV25' to perform <g class="gr_ gr_78 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="78" id="78">change</g>. The management service was unable to connect to the node using any of the IP addresses resolved for the node.
    Time Message
    8/15/2017 11:22:15 PM Could not contact node 'WIN-IDLT2GCSV25' to perform <g class="gr_ gr_97 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="97" id="97">change</g>. The management service was unable to connect to the node using any of the IP addresses resolved for the node.
    Time Message
    8/15/2017 11:23:36 PM Failed to execute the change on the target node

    Can someone please help resolve these issues?


    • Edited by KMLN Tuesday, August 15, 2017 10:26 PM Formatting
    Tuesday, August 15, 2017 10:25 PM

Answers

  • Turned out that the compute nodes were not part of the same security group and therefore were not able to communicate. They all worked fine after correcting the error.
    • Marked as answer by KMLN Thursday, August 17, 2017 10:49 AM
    Thursday, August 17, 2017 10:49 AM