{"action":"created","issue":{"url":"https://api.github.com/repos/projectatomic/adb-atomic-developer-bundle/issues/147","labels_url":"https://api.github.com/repos/projectatomic/adb-atomic-developer-bundle/issues/147/labels{/name}","comments_url":"https://api.github.com/repos/projectatomic/adb-atomic-developer-bundle/issues/147/comments","events_url":"https://api.github.com/repos/projectatomic/adb-atomic-developer-bundle/issues/147/events","html_url":"https://github.com/projectatomic/adb-atomic-developer-bundle/issues/147","id":122023513,"number":147,"title":"Time out during vagrant up but it still starts","user":{"login":"mmalina","id":2291011,"avatar_url":"https://avatars.githubusercontent.com/u/2291011?v=3","gravatar_id":"","url":"https://api.github.com/users/mmalina","html_url":"https://github.com/mmalina","followers_url":"https://api.github.com/users/mmalina/followers","following_url":"https://api.github.com/users/mmalina/following{/other_user}","gists_url":"https://api.github.com/users/mmalina/gists{/gist_id}","starred_url":"https://api.github.com/users/mmalina/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmalina/subscriptions","organizations_url":"https://api.github.com/users/mmalina/orgs","repos_url":"https://api.github.com/users/mmalina/repos","events_url":"https://api.github.com/users/mmalina/events{/privacy}","received_events_url":"https://api.github.com/users/mmalina/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2015-12-14T11:21:24Z","updated_at":"2015-12-14T13:37:44Z","closed_at":null,"body":"Even with the fix from #128 I still get a time out during vagrant up, but this is probably something else.\r\nI have seen this before even in instances where that other issue didn't happen. I'm on OS X and am using the build from December 11 through https://github.com/redhat-developer-tooling/openshift-vagrant .\r\nSee here:\r\n```\r\n$ vagrant up\r\nBringing machine 'default' up with 'virtualbox' provider...\r\n==> default: Clearing any previously set forwarded ports...\r\n==> default: Clearing any previously set network interfaces...\r\n==> default: Preparing network interfaces based on configuration...\r\n    default: Adapter 1: nat\r\n    default: Adapter 2: hostonly\r\n==> default: Forwarding ports...\r\n    default: 22 => 2222 (adapter 1)\r\n==> default: Running 'pre-boot' VM customizations...\r\n==> default: Booting VM...\r\n==> default: Waiting for machine to boot. This may take a few minutes...\r\n    default: SSH address: 127.0.0.1:2222\r\n    default: SSH username: vagrant\r\n    default: SSH auth method: private key\r\n    default: Warning: Connection timeout. Retrying...\r\n    default: Warning: Remote connection disconnect. Retrying...\r\n==> default: Machine booted and ready!\r\n==> default: Checking for guest additions in VM...\r\n    default: No guest additions were detected on the base box for this VM! Guest\r\n    default: additions are required for forwarded ports, shared folders, host only\r\n    default: networking, and more. If SSH fails on this machine, please install\r\n    default: the guest additions and repackage the box to continue.\r\n    default: \r\n    default: This is not an error message; everything may continue to work properly,\r\n    default: in which case you may ignore this message.\r\n==> default: Configuring and enabling network interfaces...\r\n==> default: Registering box with vagrant-registration...\r\n==> default: Rsyncing folder: /Users/rasp/git/openshift-vagrant/cdk-v2/ => /vagrant\r\n==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`\r\n==> default: flag to force provisioning. Provisioners marked to run always will still run.\r\n```"},"comment":{"url":"https://api.github.com/repos/projectatomic/adb-atomic-developer-bundle/issues/comments/164440426","html_url":"https://github.com/projectatomic/adb-atomic-developer-bundle/issues/147#issuecomment-164440426","issue_url":"https://api.github.com/repos/projectatomic/adb-atomic-developer-bundle/issues/147","id":164440426,"user":{"login":"mmalina","id":2291011,"avatar_url":"https://avatars.githubusercontent.com/u/2291011?v=3","gravatar_id":"","url":"https://api.github.com/users/mmalina","html_url":"https://github.com/mmalina","followers_url":"https://api.github.com/users/mmalina/followers","following_url":"https://api.github.com/users/mmalina/following{/other_user}","gists_url":"https://api.github.com/users/mmalina/gists{/gist_id}","starred_url":"https://api.github.com/users/mmalina/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mmalina/subscriptions","organizations_url":"https://api.github.com/users/mmalina/orgs","repos_url":"https://api.github.com/users/mmalina/repos","events_url":"https://api.github.com/users/mmalina/events{/privacy}","received_events_url":"https://api.github.com/users/mmalina/received_events","type":"User","site_admin":false},"created_at":"2015-12-14T13:37:44Z","updated_at":"2015-12-14T13:37:44Z","body":"@hferentschik the problem is that there is a warning every single time. A warning should warn a user of something going slightly wrong. Perhaps something that the user has done wrong. At least that's my opinion. So what I'm asking here is to fix it so that either a more benevolent time out is given or some other mechanism is employed so that a warning is not displayed every time (for me and @rhopp).\r\n\r\nBut of course it's up to you all to decide if you accept this as a bug or not :)"}}