The vnffg-update functionality leaves database in an error state

Bug #1724809 reported by Dimitrios Markou
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Medium
Dimitrios Markou

Bug Description

When we execute the vnffg-update command through tacker CLI it raises the error "NotImplementedError: sf chain update not supported" and leaves the already created VNFFG in an error state.
In addition to that we cannot delete the vnffg which now is in error state because tacker thinks that the chain which corresponds to that vnffg is still in use.

This bug was observed after we applied this patch: https://review.openstack.org/#/c/513329/

description: updated
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/513384

Changed in tacker:
assignee: nobody → Dimitrios Markou (mardim)
status: New → In Progress
Changed in tacker:
milestone: none → queens-2
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.openstack.org/513384
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=43a019ea0c0bdb95852edc2f3574991b0918aa84
Submitter: Zuul
Branch: master

commit 43a019ea0c0bdb95852edc2f3574991b0918aa84
Author: Dimitrios Markou <email address hidden>
Date: Thu Oct 19 16:26:44 2017 +0300

    [Bug-Fix] Update VNFFG leaves db in error state

    Currently in tacker there is no support for updating a chain or
    a classifier. So if anyone was trying to update a chain through
    the vnffg-update command of the tackerclient a NotImplementedError
    was raising and that was leaving the whole tacker ecosystem in an error
    state.

    That was happening because some objects in the database was in an status
    ERROR and some other in a status PENDING_UPDATE.

    With this patch we are setting all the objects in the database in a
    ERROR status therefore the user can delete the failed VNFFG without
    erasing the whole tacker database.

    Closes-Bug: #1724809

    Change-Id: I2c399a33055ccce41be941eca0bee52508399fd7
    Signed-off-by: Dimitrios Markou <email address hidden>

Changed in tacker:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/tacker 0.9.0

This issue was fixed in the openstack/tacker 0.9.0 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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