[Bug 245051] Vagrant image for 12.1 can't start shell

2020-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245051

Glen Barber  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|g...@freebsd.org

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 245051] Vagrant image for 12.1 can't start shell

2020-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245051

Glen Barber  changed:

   What|Removed |Added

 Status|Open|In Progress

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 245051] Vagrant image for 12.1 can't start shell

2020-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245051

--- Comment #4 from commit-h...@freebsd.org ---
A commit references this bug:

Author: gjb
Date: Thu May 28 18:57:56 UTC 2020
New revision: 361593
URL: https://svnweb.freebsd.org/changeset/base/361593

Log:
  Include the shells/bash port on Vagrant images, which prevents
  a shell issue during startup.

  Approved by:  re (kib, insta-MFC)
  PR:   245051
  Sponsored by: Rubicon Communications, LLC (netgate.com)

Changes:
_U  stable/12/
  stable/12/release/tools/vagrant.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 245051] Vagrant image for 12.1 can't start shell

2020-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245051

--- Comment #3 from commit-h...@freebsd.org ---
A commit references this bug:

Author: gjb
Date: Thu May 28 18:57:08 UTC 2020
New revision: 361592
URL: https://svnweb.freebsd.org/changeset/base/361592

Log:
  Include the shells/bash port on Vagrant images, which prevents
  a shell issue during startup.

  Approved by:  re (kib, insta-MFC)
  PR:   245051
  Sponsored by: Rubicon Communications, LLC (netgate.com)

Changes:
_U  stable/11/
  stable/11/release/tools/vagrant.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 245051] Vagrant image for 12.1 can't start shell

2020-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245051

--- Comment #2 from commit-h...@freebsd.org ---
A commit references this bug:

Author: gjb
Date: Thu May 28 18:48:31 UTC 2020
New revision: 361591
URL: https://svnweb.freebsd.org/changeset/base/361591

Log:
  Include the shells/bash port on Vagrant images, which prevents
  a shell issue during startup.

  PR:   245051
  MFC after:1 minute (if approved by re@)
  X-MFC-for:11.4-RC2
  Sponsored by: Rubicon Communications, LLC (netgate.com)

Changes:
  head/release/tools/vagrant.conf

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"


[Bug 245051] Vagrant image for 12.1 can't start shell

2020-05-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245051

John-Mark Gurney  changed:

   What|Removed |Added

 Status|New |Open
   Severity|Affects Only Me |Affects Some People
 CC||j...@freebsd.org

--- Comment #1 from John-Mark Gurney  ---
I have been able to reproduce this.  This affects the following versions of
FreeBSD 11.3-R, 11.x-STABLE, 12.1-R, 13.0-CURRENT and likely effects all images
produced.

I have sent an email to re@ about this, but have not received a reply about
this.  Here is the email:
There is an issue where vagrant defaults to using bash to see if a VM
is running.  We do not install bash by default, and so that results in
the following experience:
nmac,ttys006,~/f114b,505$vagrant init freebsd/FreeBSD-11.4-BETA2
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.
nmac,ttys006,~/f114b,506$vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'freebsd/FreeBSD-11.4-BETA2' could not be found. Attempting to
find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'freebsd/FreeBSD-11.4-BETA2'
default: URL: https://vagrantcloud.com/freebsd/FreeBSD-11.4-BETA2
==> default: Adding box 'freebsd/FreeBSD-11.4-BETA2' (v2020.05.15) for
provider: virtualbox
default: Downloading:
https://vagrantcloud.com/freebsd/boxes/FreeBSD-11.4-BETA2/versions/2020.05.15/providers/virtualbox.box
default: Download redirected to host:
vagrantcloud-files-production.s3.amazonaws.com
==> default: Successfully added box 'freebsd/FreeBSD-11.4-BETA2' (v2020.05.15)
for 'virtualbox'!
==> default: Importing base box 'freebsd/FreeBSD-11.4-BETA2'...
==> default: Generating MAC address for NAT networking...
==> default: Checking if box 'freebsd/FreeBSD-11.4-BETA2' version '2020.05.15'
is up to date...
==> default: Setting the name of the VM: f114b_default_1590096819756_45273
==> default: Fixed port collision for 22 => . Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2201 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2201
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. 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.

it also causes other things to happen.  I filed a bug w/ vagrant, and
they refused to fix it on their side of things (like doing the correct
posix way of using sh): https://github.com/hashicorp/vagrant/issues/11532

I have finally attempted the fix of providing a default Vagrantfile in
the box with a shell set of sh, and this fixed the error.  The file
contents were just:
Vagrant.configure("2") do |config|
config.ssh.shell = "/bin/sh"
end

and the only requirements was that the file be located in the same
directory:
nmac,ttys006,~/f114b,545$tar -tzf shellfix.box
Vagrantfile
box.ovf
metadata.json
vagrant.vmdk

Otherwise everything else was the same.

and with that fix applied:
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2201
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default:
default: Vagrant insecure key detected. Vagrant will automatically replace
default: this with a newly generated keypair for better security.
default:
default: Inserting

[Bug 245051] Vagrant image for 12.1 can't start shell

2020-03-25 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245051

Bug ID: 245051
   Summary: Vagrant image for 12.1 can't start shell
   Product: Base System
   Version: 12.1-STABLE
  Hardware: amd64
OS: Any
Status: New
  Severity: Affects Only Me
  Priority: ---
 Component: misc
  Assignee: b...@freebsd.org
  Reporter: ruslan.yakau...@gmail.com

By this doc https://www.freebsd.org/releases/12.1R/announce.html

$ vagrant init freebsd/FreeBSD-12.1-RELEASE
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'freebsd/FreeBSD-12.1-RELEASE' could not be found. Attempting
to find and install...
default: Box Provider: virtualbox
default: Box Version: >= 0
==> default: Loading metadata for box 'freebsd/FreeBSD-12.1-RELEASE'
default: URL: https://vagrantcloud.com/freebsd/FreeBSD-12.1-RELEASE
==> default: Adding box 'freebsd/FreeBSD-12.1-RELEASE' (v2019.11.01) for
provider: virtualbox
default: Downloading:
https://vagrantcloud.com/freebsd/boxes/FreeBSD-12.1-RELEASE/versions/2019.11.01/providers/virtualbox.box
default: Download redirected to host:
vagrantcloud-files-production.s3.amazonaws.com
==> default: Successfully added box 'freebsd/FreeBSD-12.1-RELEASE'
(v2019.11.01) for 'virtualbox'!
==> default: Importing base box 'freebsd/FreeBSD-12.1-RELEASE'...
==> default: Generating MAC address for NAT networking...
==> default: Checking if box 'freebsd/FreeBSD-12.1-RELEASE' version
'2019.11.01' is up to date...
==> default: Setting the name of the VM: vm_default_1585136809769_53470
Vagrant is currently configured to create VirtualBox synced folders with
the `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrant  
guest is not trusted, you may want to disable this option. For more 
information on this option, please refer to the VirtualBox manual:  

  https://www.virtualbox.org/manual/ch04.html#sharedfolders 

This option can be disabled globally with an environment variable:  

  VAGRANT_DISABLE_VBOXSYMLINKCREATE=1   

or on a per folder basis within the Vagrantfile:

  config.vm.synced_folder '/host/path', '/guest/path',
SharedFoldersEnableSymlinksCreate: false
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) =>  (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Retrying...
default: Warning: Remote connection disconnect. Retrying...
default: Warning: Connection reset. Re