tacker

  1. Bug #1945387
  2. Comment #6

Comment 6 for bug 1945387

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

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