diff options
| author |   Akhila Kishore <akhila.kishore@intel.com> | 2020-01-21 11:37:44 -0800 |
|---|---|---|
| committer | Akhila Kishore <akhila.kishore@intel.com> | 2020-01-21 11:37:44 -0800 |
| commit | f3c09ea952108a5bf9b0bc143ffeee2a1bf73fd3 (patch) | |
| tree | baa689fcfe228d18c57bac06ee1550c985e037a5 /kud/hosting_providers/vagrant/Vagrantfile | |
| parent | 42efc317925a12c22aa87ec715df61d339bd9347 (diff) | |
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
Diffstat (limited to 'kud/hosting_providers/vagrant/Vagrantfile')
| -rw-r--r-- | kud/hosting_providers/vagrant/Vagrantfile | 4 |
1 files changed, 2 insertions, 2 deletions
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' |