Uploaded image for project: 'Bigtop'
  1. Bigtop
  2. BIGTOP-1732

remove has_ssh in Docker provisioner

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.8.0
    • Fix Version/s: 1.0.0
    • Component/s: deployment, vm
    • Labels:
      None

      Description

      Set has_ssh = true in Vagrantfile can cause following error if running on non-Linux hosts:

      ==> bigtop1: Waiting for machine to boot. This may take a few minutes...
      Vagrant::Errors::VMBootTimeout: Timed out while waiting for the machine to boot. This means that
      Vagrant was unable to communicate with the guest machine within
      the configured ("config.vm.boot_timeout" value) time period.
      
      If you look above, you should be able to see the error(s) that
      Vagrant had when attempting to connect to the machine. These errors
      are usually good hints as to what may be wrong.
      
      If you're using a custom box, make sure that networking is properly
      working and you're able to connect to the machine. It is a common
      problem that networking isn't setup properly in these boxes.
      Verify that authentication configurations are also setup properly,
      as well.
      
      If the box appears to be booting properly, you may want to increase
      the timeout ("config.vm.boot_timeout") value.
      

      According to conclusion reached in BIGTOP-1643's comments, this JIRA is going to remove has_ssh setting.

        Attachments

        1. BIGTOP-1732.patch
          1 kB
          Evans Ye
        2. BIGTOP-1732.patch
          1 kB
          Evans Ye

          Activity

            People

            • Assignee:
              evans_ye Evans Ye
              Reporter:
              evans_ye Evans Ye
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: