Closed RaistGH closed 7 years ago
Thanks @RaistGH
a possible solution would be to use a more specific name for the EMS package openbaton-ems
. Or simply try to install the EMS.
the reason behind that if is that we don't want to execute any command that would require internet connectivity in case it is not provided in the VM.
was already fixed: https://github.com/openbaton/generic-vnfm/issues/25
which version are you using?
anyways we are also working on the renaming of the EMS debian package
Indeed, you're completely right. I was using last release of OpenBaton but I've been a couple of months not touching it so it may need an update. Sorry for that.
P.S.: Updating OpenBaton indeed solved the issue as expected.
Using a customized Xenial dist of Ubuntu Cloud I got connection error through EMS with my instance. Checking the logs I find the following line:
[ 17.330490] cloud-init[1227]: EMS is already installed
What's of course not possible. Reviewing the script I see that it check for EMS with the following command:dpkg -l | grep "ems" | wc -l
What in my distribution is not null given that the commanddpkg -l | grep "ems"
prints the following:ii dosfstools 3.0.28-2ubuntu0.1 amd64 utilities for making and checking MS-DOS FAT filesyst
emsii init-system-helpers 1.29ubuntu4 all helper tools for all init syst
emsii irqbalance 1.1.0-2ubuntu1 amd64 Daemon to balance interrupts for SMP syst
emsii libbsd0:amd64 0.8.2-1 amd64 utility functions from BSD syst
ems- shared library
ii mount 2.27.1-6ubuntu3.3 amd64 tools for mounting and manipulating filesyst
emsii squashfs-tools 1:4.3-3ubuntu2 amd64 Tool to create and append to squashfs filesyst
emsii zerofree 1.0.3-1 amd64 zero free blocks from ext2, ext3 and ext4 file-syst
ems`As it's not null the GVNFM thinks that EMS is already installed and it's never done.
My workaround so far is to install ems-0.20 manually for my customized dist.