[Bug 202323] 10.2-RELEASE Announcement vagrant instructions don't work

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202323

            Bug ID: 202323
           Summary: 10.2-RELEASE Announcement vagrant instructions don't
                    work
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Some People
          Priority: ---
         Component: Website
          Assignee: freebsd-doc at FreeBSD.org
          Reporter: chip at 2bithacker.net

In the 10.2-RELEASE Announcement page, it says:

* Hashicorp/Atlas® Vagrant™:
  Instances can be deployed using the vagrant utility:
      % vagrant init freebsd/FreeBSD-10.2-RELEASE
      % vagrant up

However, when running these command, the following happens:

> vagrant init freebsd/FreeBSD-10.2-RELEASE
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.
> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 => 2222 (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Connection timeout. Retrying...
The configured shell (config.ssh.shell) is invalid and unable
to properly execute commands. The most common cause for this is
using a shell that is unavailable on the system. Please verify
you're using the full path to the shell and that the shell is
executable by the SSH user.

I think the instructions may be missing a few steps.

-- 
You are receiving this mail because:
You are the assignee for the bug.