Bug 223474 - Concerns about FreeBSD Vagrant boxes
Summary: Concerns about FreeBSD Vagrant boxes
Status: Closed Overcome By Events
Alias: None
Product: Services
Classification: Unclassified
Component: Core Infrastructure (show other bugs)
Version: unspecified
Hardware: Any Any
: --- Affects Many People
Assignee: FreeBSD Release Engineering
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-06 13:54 UTC by Guangyuan Yang
Modified: 2017-11-06 19:40 UTC (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Guangyuan Yang freebsd_committer freebsd_triage 2017-11-06 13:54:45 UTC
I am trying out FreeBSD Vagrant boxes. I do have several concerns that I could not find the answer anywhere:

1. The default login user is vagrant (passwd:vagrant), while I cannot login as root. What is the default password for root? (and can we document this somewhere?)

2. Confusions about Vagrantfile has been raised over the Internet[1]. While instructions are posted[2], is it possible to add this configuration to the official page[3]?

3. The latest security/sudo has a known bug: while hostname was not defined, sudo will immediately encounter segfault (see PR222510[4]). Is it beneficial to consider adding a default hostname for Vagrant boxes?


I didn't find the proper bug tracker field for releng, please forgive me if I posted this in the wrong place.

Specifically, I am using FreeBSD-11.1-RELEASE[4] box. Not sure if these affect other boxes.

Thanks!

[1]: https://groups.google.com/forum/#!topic/vagrant-up/dNnloUOVCI4
[2]: https://forums.freebsd.org/threads/52717/
[3]: https://app.vagrantup.com/freebsd/boxes/FreeBSD-11.1-RELEASE
[4]: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222510
Comment 1 Glen Barber freebsd_committer freebsd_triage 2017-11-06 17:23:55 UTC
(In reply to Guangyuan Yang from comment #0)
> I am trying out FreeBSD Vagrant boxes. I do have several concerns that I
> could not find the answer anywhere:
> 
> 1. The default login user is vagrant (passwd:vagrant), while I cannot login
> as root. What is the default password for root? (and can we document this
> somewhere?)
> 

The root user does not have a default password.  Obtaining root access is done with sudo.  (This is a Vagrant-specific configuration, not FreeBSD.)

> 2. Confusions about Vagrantfile has been raised over the Internet[1]. While
> instructions are posted[2], is it possible to add this configuration to the
> official page[3]?
> 

Invoking 'vagrant up' a second time will boot correctly, with a random generated MAC.  This is documented in the 10.4-RELEASE errata page, but apparently missed in the 11.1-RELEASE errata page.  I'll add it.

https://www.freebsd.org/releases/10.4R/errata.html

Adding a static MAC to the release tools will likely cause problems when multiple Vagrant boxes are running on the same network.  Adding random generated MAC addresses to the build tools 

> 3. The latest security/sudo has a known bug: while hostname was not defined,
> sudo will immediately encounter segfault (see PR222510[4]). Is it beneficial
> to consider adding a default hostname for Vagrant boxes?
> 

This was added last week in r325156 to 12-CURRENT.  The MFC is not done yet.
Comment 2 commit-hook freebsd_committer freebsd_triage 2017-11-06 17:28:41 UTC
A commit references this bug:

Author: gjb
Date: Mon Nov  6 17:27:50 UTC 2017
New revision: 325489
URL: https://svnweb.freebsd.org/changeset/base/325489

Log:
  Document issuing 'vagrant up' a second time will boot properly if the
  virtual machine does not yet have a MAC address.

  PR:		223474 (related)
  Sponsored by:	The FreeBSD Foundation

Changes:
  stable/11/release/doc/en_US.ISO8859-1/errata/article.xml
Comment 3 commit-hook freebsd_committer freebsd_triage 2017-11-06 17:29:44 UTC
A commit references this bug:

Author: gjb
Date: Mon Nov  6 17:29:00 UTC 2017
New revision: 51183
URL: https://svnweb.freebsd.org/changeset/doc/51183

Log:
  Regen after r325489.

  PR:		223474 (related)
  Sponsored by:	The FreeBSD Foundation

Changes:
  head/en_US.ISO8859-1/htdocs/releases/11.1R/errata.html
Comment 4 Glen Barber freebsd_committer freebsd_triage 2017-11-06 17:31:18 UTC
(In reply to Glen Barber from comment #1)
> (In reply to Guangyuan Yang from comment #0)
> > I am trying out FreeBSD Vagrant boxes. I do have several concerns that I
> > could not find the answer anywhere:
> > 
> > 1. The default login user is vagrant (passwd:vagrant), while I cannot login
> > as root. What is the default password for root? (and can we document this
> > somewhere?)
> > 
> 
> The root user does not have a default password.  Obtaining root access is
> done with sudo.  (This is a Vagrant-specific configuration, not FreeBSD.)
> 
> > 2. Confusions about Vagrantfile has been raised over the Internet[1]. While
> > instructions are posted[2], is it possible to add this configuration to the
> > official page[3]?
> > 
> 
> Invoking 'vagrant up' a second time will boot correctly, with a random
> generated MAC.  This is documented in the 10.4-RELEASE errata page, but
> apparently missed in the 11.1-RELEASE errata page.  I'll add it.
> 
> https://www.freebsd.org/releases/10.4R/errata.html
> 
> Adding a static MAC to the release tools will likely cause problems when
> multiple Vagrant boxes are running on the same network.  Adding random
> generated MAC addresses to the build tools 
> 

This last sentence is incomplete.  It should have read:

Adding random generated MAC addresses to the build tools breaks build reproducibility.

> > 3. The latest security/sudo has a known bug: while hostname was not defined,
> > sudo will immediately encounter segfault (see PR222510[4]). Is it beneficial
> > to consider adding a default hostname for Vagrant boxes?
> > 
> 
> This was added last week in r325156 to 12-CURRENT.  The MFC is not done yet.
Comment 5 Guangyuan Yang freebsd_committer freebsd_triage 2017-11-06 19:40:36 UTC
(In reply to Glen Barber from comment #4)

Thanks! This PR did clear things up. Now my only concern is - some boxes would be unusable before the MFC period ends. 

I think it is safe to close this PR now.