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 <akhila.kishore@intel.com> Issue-ID: MULTICLOUD-974 Change-Id: I9a9e28357f1f56d17643d8f2a31f4cdca70fb456
onap · Jan 21, 2020 · f3c09ea · f3c09ea
1 parent 42efc31
commit f3c09ea
Showing 1 changed file with 2 additions and 2 deletions.
diff --git 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'