Vagrant enters aborted state during apt-get update

I am running into troubles when performing an update through apt-get on a virtual machine bootstrapped using Vagrant.

In particular, I have a working configuration (vagrantfile, puppet manifest, and whatsoever). However I need now to add an apt-get update, and the following cases make the VM enter the "aborted" state:

1. Through puppet, an exec block running apt-get update as root, during provisioning.
2. Through poor man's provisioner, a .sh script containingapt-get -y update as alternative provisioner.
3. sudo apt-get update on the console of the VM when provisioned without problems (as said, existing configuration is working)

I suspect it is not related to puppet, as I remember it happened some other time when I was not using it. I hoped that, if it was a known bug, it would have been fixed by updating... especially since I am not using anything esoteric. However googling doesn't give anything! (Am I the only one using ubuntu on vagrant and wanting to update package list?)

The systems on which this happens are Archbang 3.19.3-3-ARCH i686 and (just to be sure it's not because I messed with Linux) Windows 8.1 pro 64bit - both are running Vagrant 1.7.2/Virtualbox 4.3.26 r98988

The boxes are respectively ubuntu/trusty32 and ubuntu/trusty64 and it happens with both version 20150427.0.0 and 20150609.0.9

Thank you for your help

(also side question, I am unsure if I should ask here, on serverfault, or superuser)

1 Answers

Answers 1

Try with 'sudo apt-get -y update' and it will auto confirm apt-get command.

If You Enjoyed This, Take 5 Seconds To Share It

• Facebook
• Twitter
• Google+
• StumbleUpon
• Digg
• Delicious
• LinkedIn
• Reddit
• Technorati