Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NSR Error: "VimDriverException: Image is not yet in active. Try again later..." #293

Open
askmanas opened this issue May 9, 2018 · 1 comment

Comments

@askmanas
Copy link

askmanas commented May 9, 2018

Hi,

I have installed openbaton 5.2.0 on Ubuntu 16.04 VM & got it successfully integrated to DevStack OpenStack Single Machine setup. After uploading the VNF packages i.e. iPerf-server/client & creating the NSD, when I try to launch the service its getting failed with following error.

"ERROR:org.openbaton.common.vnfm_sdk.exception.VnfmSdkException: Not able to allocate Resources because: org.openbaton.exceptions.VimException: Not launched VM with hostname iperf-server-2316800 successfully on VimInstance devstack-demo. Caused by: org.openbaton.exceptions.VimDriverException: Image (name: cda6cae3-2a4a-4738-8ca8-af482ef731c1) is not yet in active. Try again later..."

Also find the openbaton.log attached herewith.

I could see in the OpenBaton Dashboard that the given Image is showing Active. Here is details of my openbaton setup:

  • openbaton-fms 1.4.2
  • openbaton-nfvo 5.2.0
  • openbaton-plugin-monitoring-zabbix 5.0.0
  • openbaton-plugin-vimdriver-openstack-4j 5.2.0
  • openbaton-plugin-vimdriver-test 5.2.0
  • openbaton-vnfm-generic 5.2.0

Thanks is Advance to provide resolution to this problem.

Regards
Manas...

NSR Error Image is yet not active.txt

@mpauls
Copy link
Member

mpauls commented Dec 21, 2018

This error logs indicates that you were uploading the image when trying to deploy. Since the image was not yet uploaded completely, it gives you this error message.

Nevertheless, it would be great if you can provide also the logs of VNFM and Driver so that we may have a deeper look in case the problem is related to the NFVO and a wrong setting of the image status.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants