ns delete with --force option fails

Bug #1892151 reported by Yoshito Ito
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
python-tackerclient
Fix Released
Undecided
Donghun Cha

Bug Description

When deleting NS with ``--force`` option, it fails with an error message of arguments.

Error message is:

Unable to delete the below ns(s):
 Cannot delete 97a2ba62-a5d1-49b1-8ab2-16240abbe395: delete_ns() takes 2 positional arguments but 3 were given

Changed in python-tackerclient:
assignee: nobody → Yoshito Ito (ito.yoshito)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to python-tackerclient (master)

Fix proposed to branch: master
Review: https://review.opendev.org/751964

Changed in python-tackerclient:
assignee: Yoshito Ito (ito.yoshito) → Donghun Cha (donghuncha)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to python-tackerclient (master)

Reviewed: https://review.opendev.org/751964
Committed: https://git.openstack.org/cgit/openstack/python-tackerclient/commit/?id=a0d2ef8fb1332c48e437d8d69801157b5da684f8
Submitter: Zuul
Branch: master

commit a0d2ef8fb1332c48e437d8d69801157b5da684f8
Author: Donghun Cha <email address hidden>
Date: Tue Sep 15 03:24:15 2020 +0000

    Deleting Network Service(NS) with force option bug fixes

    Currently in tacker, deleting the NS that already exist
    has a problem like below Closes-Bug #1892151.
    It has positional arguments error with command:
    openstack ns delete <NS> (--force)
    tacker ns-delete <NS> --force
    because of client interface problem, so correct the
    client's pyhton function delete_ns()

    Change-Id: I7e100b065dbfb4503a5a45b10d3a962a4af36d76
    Closes-Bug: #1892151

Changed in python-tackerclient:
status: In Progress → Fix Released
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.