vimConnectionID in ResouceHandle is not compliant with SOL

Bug #2046321 reported by Ayumu Ueha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tacker
Fix Released
Medium
Unassigned

Bug Description

The resourceHandle object has a vimConnectionId attribute, but Data stored in vimConnectionInfo by Tacker is different from SOL.

* https://opendev.org/openstack/tacker/src/branch/master/tacker/sol_refactored/objects/common/resource_handle.py
* https://www.etsi.org/deliver/etsi_gs/NFV-SOL/001_099/003/03.03.01_60/gs_nfv-sol003v030301p.pdf

Current Tacker implementation uses vimId as the value of vimConnectionId.
When following SOL, it is correct to use the key of VimConnectionInfo.

Ayumu Ueha (ueha)
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.opendev.org/c/openstack/tacker/+/903576

Changed in tacker:
status: New → In Progress
Yasufumi Ogawa (yasufum)
Changed in tacker:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tacker (master)

Reviewed: https://review.opendev.org/c/openstack/tacker/+/903576
Committed: https://opendev.org/openstack/tacker/commit/07908e7739c9e5077f0423b6a3a6c50e6c1f019e
Submitter: "Zuul (22348)"
Branch: master

commit 07908e7739c9e5077f0423b6a3a6c50e6c1f019e
Author: YiFeng <email address hidden>
Date: Wed Dec 13 15:08:15 2023 +0900

    Fix vimConnectionId in ResourceHandle

    This patch changes the value corresponding to the vimConnectionId field
    in the ResouceHandle data structure in the DB from the vimId value of
    VimConnectionInfo to the key of the map of VimConnectionInfo.

    Closes-Bug: #2046321
    Change-Id: I3245d5ccb97bbf9dce8364ba37b68f99ed3af6d2

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

This issue was fixed in the openstack/tacker 11.0.0.0rc1 release candidate.

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.