[Bug 1589721] [NEW] vagrant username is incorrect

[Jack Peterson]

Public bug reported:

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/xenial64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'ubuntu/xenial64' is up to date...
==> default: Setting the name of the VM: ##########
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 80 (guest) => 8888 (host) (adapter 1)
    default: 22 (guest) => 2322 (host) (adapter 1)
    default: 81 (guest) => 8889 (host) (adapter 1)
    default: 3306 (guest) => 3307 (host) (adapter 1)
    default: 15672 (guest) => 8890 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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: password
    default: Warning: Remote connection disconnect. Retrying...
^C==> default: Waiting for cleanup before exiting...

Specifying various forms of config.ssh.username and config.ssh.password
fails to get vagrant to be able to properly authenticate. Once booted up
though, one can ssh into the system with the ubuntu user. This bug
breaks the default vagrant workflow.

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/1589721

Title:
  vagrant username is incorrect

Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  Bringing machine 'default' up with 'virtualbox' provider...
  ==> default: Importing base box 'ubuntu/xenial64'...
  ==> default: Matching MAC address for NAT networking...
  ==> default: Checking if box 'ubuntu/xenial64' is up to date...
  ==> default: Setting the name of the VM: ##########
  ==> default: Clearing any previously set network interfaces...
  ==> default: Preparing network interfaces based on configuration...
      default: Adapter 1: nat
  ==> default: Forwarding ports...
      default: 80 (guest) => 8888 (host) (adapter 1)
      default: 22 (guest) => 2322 (host) (adapter 1)
      default: 81 (guest) => 8889 (host) (adapter 1)
      default: 3306 (guest) => 3307 (host) (adapter 1)
      default: 15672 (guest) => 8890 (host) (adapter 1)
      default: 22 (guest) => 2222 (host) (adapter 1)
  ==> default: Running 'pre-boot' VM customizations...
  ==> 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: password
      default: Warning: Remote connection disconnect. Retrying...
  ^C==> default: Waiting for cleanup before exiting...

  Specifying various forms of config.ssh.username and
  config.ssh.password fails to get vagrant to be able to properly
  authenticate. Once booted up though, one can ssh into the system with
  the ubuntu user. This bug breaks the default vagrant workflow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1589721/+subscriptions