tacker

OpenWRT vnf stuck in "PENDING-UPDATE" state.

Bug #1525808 reported by Aqsa Malik
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Medium
Unassigned

Bug Description

When deploying OpenWRT vnf through horizon or gui the vnf is created successfully and comes in active state.
But when i run the vnf-update command with sample openwrt configuration file. it returns the "Request Failed: internal server error while processing your request." in the command line. And the vnf is stuck in the "PENDING-UPDATE" state in horizon. Also i am not being able to delete that vnf as it returns "Device is still in use" error.

Tags: mitaka-rfe
Revision history for this message
bharaththiruveedula (bharath-ves) wrote :

Hi Aqsa,

Can you upload the files you have used for creating VNFD and updating the VNF. And can you also upload tacker logs?

Revision history for this message
Aqsa Malik (aqsamm) wrote :

I have attached the vnfd and the update.yaml file and tacker logs

Revision history for this message
Aqsa Malik (aqsamm) wrote :
Revision history for this message
bharaththiruveedula (bharath-ves) wrote :

But you have attached only update.yaml

Revision history for this message
Aqsa Malik (aqsamm) wrote :
Revision history for this message
Aqsa Malik (aqsamm) wrote :
bharaththiruveedula (bharath-ves)
Changed in tacker:
assignee: nobody → bharaththiruveedula (bharath-ves)
Revision history for this message
bharaththiruveedula (bharath-ves) wrote :

Thanks for uploading the files. The problem is when you update the VNF, we are getting the error from the heat/heat.py. And we need a small change tacker too to handle this error.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tacker (master)

Fix proposed to branch: master
Review: https://review.openstack.org/257360

Changed in tacker:
status: New → In Progress
Revision history for this message
Aqsa Malik (aqsamm) wrote :

Now it falls in error instead of getting stuck in pending update.

Revision history for this message
Vasubabu Kandimalla (vasubabukandimalla9) wrote :

Hi,

I am also facing the same issue.
Any help is appriciated.
Thanks,
 Vasu.

Revision history for this message
koren (korenlev) wrote :

i see he exact same thing.
any fix ready ?

Sridhar Ramaswamy (srics-r)
Changed in tacker:
importance: Undecided → Medium
Sridhar Ramaswamy (srics-r)
tags: added: mitaka-rfe
dharmendra (dharmendra-kushwaha)
Changed in tacker:
assignee: bharaththiruveedula (bharath-ves) → dharmendra (dharmendra-kushwaha)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: master
Review: https://review.openstack.org/292932

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on tacker (master)

Change abandoned by bharaththiruveedula (<email address hidden>) on branch: master
Review: https://review.openstack.org/257360

Revision history for this message
Abhijeet (abhijeet-karve) wrote :

Even i am also facing same issue while passing config file with vRouter VNF deployment. Spawned vnf but not able to delete. The tacker vnf-delete command says the "device is still in use". I have a failed vnf-update with state still says "PENDING-UPDATE".

Nguyen Hai (nguyentrihai93-deactivatedaccount)
Changed in tacker:
status: In Progress → Invalid
Nguyen Hai (nguyentrihai93-deactivatedaccount)
Changed in tacker:
status: Invalid → In Progress
Nguyen Hai (nguyentrihai93-deactivatedaccount)
Changed in tacker:
assignee: dharmendra (dharmendra-kushwaha) → Nguyen Hai (nguyentrihai93)
Revision history for this message
Nguyen Hai (nguyentrihai93-deactivatedaccount) wrote :

The reason is OpenWRT VNF cannot ping, so that it cannot be updated by 'vnf-update'.

This patch solve the problem: https://review.openstack.org/#/c/543413/

Nguyen Hai (nguyentrihai93-deactivatedaccount)
Changed in tacker:
status: In Progress → Fix Committed
Nguyen Hai (nguyentrihai93-deactivatedaccount)
Changed in tacker:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.