[
https://issues.apache.org/jira/browse/BIGTOP-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Evans Ye updated BIGTOP-1732:
-----------------------------
Attachment: BIGTOP-1732.patch
> remove has_ssh in Docker provisioner
> ------------------------------------
>
> Key: BIGTOP-1732
> URL: https://issues.apache.org/jira/browse/BIGTOP-1732
> Project: Bigtop
> Issue Type: Bug
> Components: deployment, vm
> Affects Versions: 0.8.0
> Reporter: Evans Ye
> Assignee: Evans Ye
> Priority: Minor
> Attachments: BIGTOP-1732.patch
>
>
> Set {{has_ssh = true}} in Vagrantfile can cause following error if running on
> non-Linux hosts:
> {code}
> ==> 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.
> {code}
> According to conclusion reached in BIGTOP-1643's comments, this JIRA is going
> to remove {{has_ssh}} setting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
