[Merge] lp:~tribaal/livecd-rootfs/xenial-proposed-vagrant-user-changes into lp:~ubuntu-core-dev/livecd-rootfs/xenial-proposed

[Chris Glass]

Answered inline - the ubuntu user is not being dropped.

Diff comments:

> 
> === modified file 'live-build/ubuntu-cpc/hooks/042-vagrant.binary'
> --- live-build/ubuntu-cpc/hooks/042-vagrant.binary	2017-12-05 21:40:35 +0000
> +++ live-build/ubuntu-cpc/hooks/042-vagrant.binary	2017-12-07 15:49:32 +0000
> @@ -132,8 +146,6 @@
>  
>  Vagrant.configure("2") do |config|
>    config.vm.base_mac = "${macaddr}"
> -  config.ssh.username = "ubuntu"

Absolutely not.

This change tells vagrant not to use "ubuntu" as the ssh user for "vagrant ssh". The ubuntu user still exists and still behaves exactly the same way as in every other cloud image.

You can check this behaviour using the ubuntu/artful64 box (this diff is a backport from artful):

vagrant init ubuntu/artful64
vagrant up
vagrant ssh (you're now vagrant@, as per vagrant's box-creation documentation and the vagrant user's expectations).
sudo su ubuntu (you're now the normal ubuntu@ user)

You can set keys or a password for the ubuntu@ user using cloud-init (if you're so inclined), just like with every other ubuntu cloud instance.

> -  config.ssh.password = "${ubuntu_user_pass}"
>  
>    config.vm.provider "virtualbox" do |vb|
>       vb.customize [ "modifyvm", :id, "--uart1", "0x3F8", "4" ]


-- 
https://code.launchpad.net/~tribaal/livecd-rootfs/xenial-proposed-vagrant-user-changes/+merge/334921
Your team Ubuntu Core Development Team is requested to review the proposed merge of lp:~tribaal/livecd-rootfs/xenial-proposed-vagrant-user-changes into lp:~ubuntu-core-dev/livecd-rootfs/xenial-proposed.