Whirr
  1. Whirr
  2. WHIRR-590

ssh port timeout fails the whole cluster

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.7.1
    • Fix Version/s: 0.7.2
    • Component/s: None
    • Labels:
      None

      Description

      If the ssh port does not open before the jclouds.compute.timeout.port-open timeout, the whole cluster fails to launch rather than starting a replacement for the failed node and continuing provisioning. You can simulate this by setting your jclouds.compute.timeout.port-open to something very small, such as:

      jclouds.compute.timeout.port-open=5

      I believe that the failure happens because the node winds up both the successfulNodes and the lostNodes reported by the RunNodesException. I filed a bug for this in jclouds: https://code.google.com/p/jclouds/issues/detail?id=923

      1. WHIRR-590.patch
        2 kB
        Doug Daniels

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Doug Daniels
            Reporter:
            Doug Daniels
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development