Missing Location in http header when changing external connectivity

[YaoYudie]

ACcording to the specification file, When operating on VNF instance resource
The VNFM returns a "202 Accepted" response with an empty payload body and a "Location" HTTP header
that points to the new "Individual VNF LCM operation occurrence" resource, i.e. it includes the URI of that
resource which is "…/vnf_lcm_op_occs/{vnfLcmOpOccId}"
but now the "Location" HTTP header is missing in the response when changing external connectivity.

opertion log:
curl -i POST /vnflcm/v1/vnf_instances/69dc33ee-598a-47fa-860d-01f5f9a07583/change_ext_conn

{
    "seconds": 0.857558,
    "status": 202,
    "body": "",
    "headers": {
        "Content-Length": "0",
        "Content-Type": "application/json",
        "X-Openstack-Request-Id": "req-f87be405-94eb-4793-b6cd-3954fd5f99c3",
        "Date": "Tue, 28 Sep 2021 06:13:18 GMT",
        "Connection": "keep-alive"
    }
}

[Pooja Singla (psingla)]

Dear YaoYudie, Please let me know if you are working on this bug. If no, I would like to start working on it.

[Yasufumi Ogawa (yasufum)]

Hi Pooja,
No reply on your comment. So, please try to tackle to fix the issue if you are still interested. Thanks!

[Ayumu Ueha (ueha)]

Hi Pooja,

It doesn't seem to be working, could you please start fixing this bug?

It seems that the following patch posted by your colleague was not enough.
https://review.opendev.org/c/openstack/tacker/+/783896

[Navum Gupta (navum)]

Hi Ayumu Ueha san,

We will start fixing this

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tacker/+/871083

[OpenStack Infra (hudson-openstack)]

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

commit c062072813ed68472dc461f2fc8df625f7238372
Author: navum <email address hidden>
Date: Thu Jan 19 12:14:01 2023 +0000

    Missing Location in http header

    This patch fixes the problem regarding the "Location" HTTP header
    which is missing in the response when changing external connectivity.
    According to the specification file, When operating on VNF instance
    resource.

    The VNFM returns a "202 Accepted" response with an empty payload body
    and a "Location" HTTP header that points to the new "Individual VNF LCM
    operation occurrence" resource, i.e. it includes the URI of that
    resource which is "…/vnf_lcm_op_occs/{vnfLcmOpOccId}" but now "Location"
    HTTP header is missing in the response when changing external
    connectivity.

    Closes-Bug: #1945387
    Change-Id: I77c161b08c9c468fe6d4d243c1d098a0855bb2c8

[OpenStack Infra (hudson-openstack)]

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