From f3c09ea952108a5bf9b0bc143ffeee2a1bf73fd3 Mon Sep 17 00:00:00 2001 From: Akhila Kishore Date: Tue, 21 Jan 2020 11:37:44 -0800 Subject: Reverting vagrant images back to 16.04 VM deployment Currently we face issue with VM based deployment causing vagrant up to fail and quit abruptly. Signed-off-by: Akhila Kishore Issue-ID: MULTICLOUD-974 Change-Id: I9a9e28357f1f56d17643d8f2a31f4cdca70fb456 --- kud/hosting_providers/vagrant/Vagrantfile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'kud') diff --git a/kud/hosting_providers/vagrant/Vagrantfile b/kud/hosting_providers/vagrant/Vagrantfile index f771d549..2d1b5ab4 100644 --- a/kud/hosting_providers/vagrant/Vagrantfile +++ b/kud/hosting_providers/vagrant/Vagrantfile @@ -10,8 +10,8 @@ ############################################################################## box = { - :virtualbox => { :name => 'elastic/ubuntu-18.04-x86_64', :version => '20191013.0.0' }, - :libvirt => { :name => 'generic/ubuntu1810'} + :virtualbox => { :name => 'elastic/ubuntu-16.04-x86_64', :version => '20180708.0.0' }, + :libvirt => { :name => 'elastic/ubuntu-16.04-x86_64', :version=> '20180210.0.0'} } require 'yaml' -- cgit 1.2.3-korg