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.

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

        Activity

        Hide
        evans_ye Evans Ye added a comment -

        Committed. Thanks for your review jay vyas.

        Show
        evans_ye Evans Ye added a comment - Committed. Thanks for your review jay vyas .
        Hide
        jayunit100 jay vyas added a comment -

        +1 ! thanks evans.

        Show
        jayunit100 jay vyas added a comment - +1 ! thanks evans.
        Hide
        evans_ye Evans Ye added a comment -

        Uploaded a new patch in accordance with jay vyas's suggestion

        Show
        evans_ye Evans Ye added a comment - Uploaded a new patch in accordance with jay vyas 's suggestion
        Hide
        evans_ye Evans Ye added a comment -

        Great idea jay, let me upload a new patch.

        Show
        evans_ye Evans Ye added a comment - Great idea jay, let me upload a new patch.
        Hide
        jayunit100 jay vyas added a comment -

        gotcha....
        can we do

        has_ssh=false # We have decided to pipe commands to docker instead of ssh, due to ssh hang issue in vagrant.
        

        so that its clear ? otherwise this will be forgotton and get reverted again

        Show
        jayunit100 jay vyas added a comment - gotcha.... can we do has_ssh=false # We have decided to pipe commands to docker instead of ssh, due to ssh hang issue in vagrant. so that its clear ? otherwise this will be forgotton and get reverted again
        Hide
        evans_ye Evans Ye added a comment -

        You're right. Vagrant detect has_ssh to determine whether provisioners such as shell or puppet to be executed or not. If has_ssh = false, non of provisioner will be executed. But because of Vagrant's issue Waiting for machine to boot' hangs infinitely with docker it seems #3951 we implemented BigTop Docker provisioner by piping commands in containers instead of leverage Vagrant provisioners.
        And it doesn't have to set has_ssh to true if we only need to ssh in.
        I've notice the has_ssh problem at the very beginning when developing BigTop Docker provisioner, hence we have has_ssh = false originally.
        Setting has_ssh to true has been added in BIGTOP-1643, this JIRA is just about to revoke the change.

        Show
        evans_ye Evans Ye added a comment - You're right. Vagrant detect has_ssh to determine whether provisioners such as shell or puppet to be executed or not. If has_ssh = false, non of provisioner will be executed. But because of Vagrant's issue Waiting for machine to boot' hangs infinitely with docker it seems #3951 we implemented BigTop Docker provisioner by piping commands in containers instead of leverage Vagrant provisioners. And it doesn't have to set has_ssh to true if we only need to ssh in. I've notice the has_ssh problem at the very beginning when developing BigTop Docker provisioner, hence we have has_ssh = false originally. Setting has_ssh to true has been added in BIGTOP-1643 , this JIRA is just about to revoke the change.
        Hide
        jayunit100 jay vyas added a comment - - edited

        Doesn't our vagrant provisioner inherently require vagrant to be able to SSH into the containers? I assume if you turn off has_ssh to equal false, *then* vagrant won't bother provisioning hadoop at all....

        Show
        jayunit100 jay vyas added a comment - - edited Doesn't our vagrant provisioner inherently require vagrant to be able to SSH into the containers? I assume if you turn off has_ssh to equal false , * then * vagrant won't bother provisioning hadoop at all....

          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:

              Development