cloud-images

  1. Bug #1851186
  2. Activity log

Activity log for bug #1851186

Date Who What changed Old value New value Message
2019-11-04 02:48:03 Yasuo Honda bug added bug
2019-11-04 02:48:31 Yasuo Honda description https://github.com/rails/rails-dev-box project is making use of Vagrant Ubuntu boxes. Recently I attempted to upgrade Vagrant box Ubuntu version from 19.04 to 19.10 then it gets the following error due to missing virtualbox guest additions. Current workaround is installing `vagrant-vbguest` vagrant plugin. * Error with Ubuntu 10.10 ``` $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ubuntu/eoan64'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'ubuntu/eoan64' version '20191031.0.0' is up to date... ==> default: Setting the name of the VM: rails-dev-box_default_1572829689700_69040 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration... default: Adapter 1: nat ==> default: Forwarding ports... default: 3000 (guest) => 3000 (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: private key default: Warning: Connection reset. Retrying... default: Warning: Remote connection disconnect. Retrying... default: default: Vagrant insecure key detected. Vagrant will automatically replace default: this with a newly generated keypair for better security. default: default: Inserting generated public key within guest... default: Removing insecure key from the guest if it's present... default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM... default: No guest additions were detected on the base box for this VM! Guest default: additions are required for forwarded ports, shared folders, host only default: networking, and more. If SSH fails on this machine, please install default: the guest additions and repackage the box to continue. default: default: This is not an error message; everything may continue to work properly, default: in which case you may ignore this message. ==> default: Setting hostname... ==> default: Mounting shared folders... default: /vagrant => /home/yahonda/git/rails-dev-box Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` * Vagrantfile ``` [yahonda@myubuntu rails-dev-box (ubuntu1910)]$ more Vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure('2') do |config| config.vm.box = 'ubuntu/eoan64' # 19.10 config.vm.hostname = 'rails-dev-box' config.vm.network :forwarded_port, guest: 3000, host: 3000 config.vm.provision :shell, path: 'bootstrap.sh', keep_color: true config.vm.provider 'virtualbox' do |v| v.memory = ENV.fetch('RAILS_DEV_BOX_RAM', 2048).to_i v.cpus = ENV.fetch('RAILS_DEV_BOX_CPUS', 2).to_i end config.vm.boot_timeout = 600 end $ ``` * Workaround ``` $ vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Fetching: micromachine-3.0.0.gem (100%) Fetching: vagrant-vbguest-0.20.0.gem (100%) Installed the plugin 'vagrant-vbguest (0.20.0)'! $ ``` https://github.com/rails/rails-dev-box project is making use of Vagrant Ubuntu boxes. Recently I attempted to upgrade Vagrant box Ubuntu version from 19.04 to 19.10 then it gets the following error due to missing virtualbox guest additions. Current workaround is installing `vagrant-vbguest` vagrant plugin. * Error with Ubuntu 10.10 ``` $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ubuntu/eoan64'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'ubuntu/eoan64' version '20191031.0.0' is up to date... ==> default: Setting the name of the VM: rails-dev-box_default_1572829689700_69040 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration...     default: Adapter 1: nat ==> default: Forwarding ports...     default: 3000 (guest) => 3000 (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: private key     default: Warning: Connection reset. Retrying...     default: Warning: Remote connection disconnect. Retrying...     default:     default: Vagrant insecure key detected. Vagrant will automatically replace     default: this with a newly generated keypair for better security.     default:     default: Inserting generated public key within guest...     default: Removing insecure key from the guest if it's present...     default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM...     default: No guest additions were detected on the base box for this VM! Guest     default: additions are required for forwarded ports, shared folders, host only     default: networking, and more. If SSH fails on this machine, please install     default: the guest additions and repackage the box to continue.     default:     default: This is not an error message; everything may continue to work properly,     default: in which case you may ignore this message. ==> default: Setting hostname... ==> default: Mounting shared folders...     default: /vagrant => /home/yahonda/git/rails-dev-box Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` * Vagrantfile ``` $ more Vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure('2') do |config|   config.vm.box = 'ubuntu/eoan64' # 19.10   config.vm.hostname = 'rails-dev-box'   config.vm.network :forwarded_port, guest: 3000, host: 3000   config.vm.provision :shell, path: 'bootstrap.sh', keep_color: true   config.vm.provider 'virtualbox' do |v|     v.memory = ENV.fetch('RAILS_DEV_BOX_RAM', 2048).to_i     v.cpus = ENV.fetch('RAILS_DEV_BOX_CPUS', 2).to_i   end   config.vm.boot_timeout = 600 end $ ``` * Workaround ``` $ vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Fetching: micromachine-3.0.0.gem (100%) Fetching: vagrant-vbguest-0.20.0.gem (100%) Installed the plugin 'vagrant-vbguest (0.20.0)'! $ ```
2019-11-04 02:49:20 Yasuo Honda description https://github.com/rails/rails-dev-box project is making use of Vagrant Ubuntu boxes. Recently I attempted to upgrade Vagrant box Ubuntu version from 19.04 to 19.10 then it gets the following error due to missing virtualbox guest additions. Current workaround is installing `vagrant-vbguest` vagrant plugin. * Error with Ubuntu 10.10 ``` $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ubuntu/eoan64'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'ubuntu/eoan64' version '20191031.0.0' is up to date... ==> default: Setting the name of the VM: rails-dev-box_default_1572829689700_69040 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration...     default: Adapter 1: nat ==> default: Forwarding ports...     default: 3000 (guest) => 3000 (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: private key     default: Warning: Connection reset. Retrying...     default: Warning: Remote connection disconnect. Retrying...     default:     default: Vagrant insecure key detected. Vagrant will automatically replace     default: this with a newly generated keypair for better security.     default:     default: Inserting generated public key within guest...     default: Removing insecure key from the guest if it's present...     default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM...     default: No guest additions were detected on the base box for this VM! Guest     default: additions are required for forwarded ports, shared folders, host only     default: networking, and more. If SSH fails on this machine, please install     default: the guest additions and repackage the box to continue.     default:     default: This is not an error message; everything may continue to work properly,     default: in which case you may ignore this message. ==> default: Setting hostname... ==> default: Mounting shared folders...     default: /vagrant => /home/yahonda/git/rails-dev-box Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` * Vagrantfile ``` $ more Vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure('2') do |config|   config.vm.box = 'ubuntu/eoan64' # 19.10   config.vm.hostname = 'rails-dev-box'   config.vm.network :forwarded_port, guest: 3000, host: 3000   config.vm.provision :shell, path: 'bootstrap.sh', keep_color: true   config.vm.provider 'virtualbox' do |v|     v.memory = ENV.fetch('RAILS_DEV_BOX_RAM', 2048).to_i     v.cpus = ENV.fetch('RAILS_DEV_BOX_CPUS', 2).to_i   end   config.vm.boot_timeout = 600 end $ ``` * Workaround ``` $ vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Fetching: micromachine-3.0.0.gem (100%) Fetching: vagrant-vbguest-0.20.0.gem (100%) Installed the plugin 'vagrant-vbguest (0.20.0)'! $ ``` https://github.com/rails/rails-dev-box project is making use of Vagrant Ubuntu boxes. Recently I attempted to upgrade Vagrant box Ubuntu version from 19.04 to 19.10 https://github.com/rails/rails-dev-box/pull/169 then it gets the following error due to missing Virtualbox guest additions. Current workaround is installing `vagrant-vbguest` vagrant plugin. * Error with Ubuntu 10.10 ``` $ vagrant up Bringing machine 'default' up with 'virtualbox' provider... ==> default: Importing base box 'ubuntu/eoan64'... ==> default: Matching MAC address for NAT networking... ==> default: Checking if box 'ubuntu/eoan64' version '20191031.0.0' is up to date... ==> default: Setting the name of the VM: rails-dev-box_default_1572829689700_69040 ==> default: Clearing any previously set network interfaces... ==> default: Preparing network interfaces based on configuration...     default: Adapter 1: nat ==> default: Forwarding ports...     default: 3000 (guest) => 3000 (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: private key     default: Warning: Connection reset. Retrying...     default: Warning: Remote connection disconnect. Retrying...     default:     default: Vagrant insecure key detected. Vagrant will automatically replace     default: this with a newly generated keypair for better security.     default:     default: Inserting generated public key within guest...     default: Removing insecure key from the guest if it's present...     default: Key inserted! Disconnecting and reconnecting using new SSH key... ==> default: Machine booted and ready! ==> default: Checking for guest additions in VM...     default: No guest additions were detected on the base box for this VM! Guest     default: additions are required for forwarded ports, shared folders, host only     default: networking, and more. If SSH fails on this machine, please install     default: the guest additions and repackage the box to continue.     default:     default: This is not an error message; everything may continue to work properly,     default: in which case you may ignore this message. ==> default: Setting hostname... ==> default: Mounting shared folders...     default: /vagrant => /home/yahonda/git/rails-dev-box Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` * Vagrantfile ``` $ more Vagrantfile # -*- mode: ruby -*- # vi: set ft=ruby : Vagrant.configure('2') do |config|   config.vm.box = 'ubuntu/eoan64' # 19.10   config.vm.hostname = 'rails-dev-box'   config.vm.network :forwarded_port, guest: 3000, host: 3000   config.vm.provision :shell, path: 'bootstrap.sh', keep_color: true   config.vm.provider 'virtualbox' do |v|     v.memory = ENV.fetch('RAILS_DEV_BOX_RAM', 2048).to_i     v.cpus = ENV.fetch('RAILS_DEV_BOX_CPUS', 2).to_i   end   config.vm.boot_timeout = 600 end $ ``` * Workaround ``` $ vagrant plugin install vagrant-vbguest Installing the 'vagrant-vbguest' plugin. This can take a few minutes... Fetching: micromachine-3.0.0.gem (100%) Fetching: vagrant-vbguest-0.20.0.gem (100%) Installed the plugin 'vagrant-vbguest (0.20.0)'! $ ```
2019-12-20 19:13:42 Francis Ginther tags id-5dd2cf798e62ed0cdf203dfc
2020-01-17 10:56:13 Germain Chazot bug added subscriber Germain Chazot
2020-06-04 17:41:27 Éric St-Jean cloud-images: assignee John Chittum (jchittum)
2020-06-05 14:49:54 John Chittum marked as duplicate 1873506