The Vagrant image may be old and have stale metadata leading to
failures when installing packages. As such, it's best to update
it as soon as possible. This is also inline with the AIO documentation
which suggests to always use an up to date OS.
Change-Id: I43d9f8431e1a6ed877936adc65c54be466b76aff
Signed-off-by: Markos Chandras <mchandras@suse.de>
config.vm.provision "shell"do |s|
s.privileged = false
s.inline = <<-SHELL
+ sudo apt-get update
cd /vagrant
export XCI_FLAVOR=${XCI_FLAVOR:-mini}
export VM_CPU=${VM_CPU:-2}
config.vm.provision "shell" do |s|
s.privileged = false
s.inline = <<-SHELL
+ sudo yum update
cd /vagrant
PART_START=$(sudo parted /dev/sda --script unit MB print | awk '/^ 3 / {print $3}')
sudo parted /dev/sda --script unit MB mkpart primary ${PART_START} 100%
# btrfs filesystem.
s.privileged = false
s.inline = <<-SHELL
+ sudo zypper -n up -l
cd /vagrant
echo -e 'd\n2\nn\np\n\n\n\nn\nw' | sudo fdisk /dev/sda
PART_END=$(sudo fdisk -l /dev/sda | grep ^/dev/sda2 | awk '{print $4}')
# btrfs filesystem.
s.privileged = false
s.inline = <<-SHELL
+ sudo zypper -n up -l
cd /vagrant
echo -e 'd\n2\nn\np\n\n\n\nn\nw' | sudo fdisk /dev/sda
PART_END=$(sudo fdisk -l /dev/sda | grep ^/dev/sda2 | awk '{print $4}')