Return both project_id when validating auto allocate network
When neutron API is called to check requirements for the auto_allocate
topology, it needs to return not only 'tenant_id' field but also
'project_id' as that is required for the policy enforcement.
Without this 'project_id' field requirements check was failing for
member and reader users as they got 404 from the Neutron API. And the
reason why Neutron was returning 404 was that it wasn't passing policy
enforcement due to missing project_id field in the 'target' object.
Closes-bug: #2066369
Change-Id: Idf96a82bc6c8cb0b47dfde3baba94b42a8a8beba
(cherry picked from commit dfc01beab22f1c2b977d3e399c3fcda69a72082d)
Reviewed: https:/ /review. opendev. org/c/openstack /neutron/ +/920482 /opendev. org/openstack/ neutron/ commit/ 75eefdbc69e40f9 d73211852cc729b b91bb73693
Committed: https:/
Submitter: "Zuul (22348)"
Branch: stable/2023.1
commit 75eefdbc69e40f9 d73211852cc729b b91bb73693
Author: Slawek Kaplonski <email address hidden>
Date: Wed May 22 15:28:05 2024 +0200
Return both project_id when validating auto allocate network
When neutron API is called to check requirements for the auto_allocate
topology, it needs to return not only 'tenant_id' field but also
'project_id' as that is required for the policy enforcement.
Without this 'project_id' field requirements check was failing for
member and reader users as they got 404 from the Neutron API. And the
reason why Neutron was returning 404 was that it wasn't passing policy
enforcement due to missing project_id field in the 'target' object.
Closes-bug: #2066369 0b47dfde3baba94 b42a8a8beba b977d3e399c3fcd a69a72082d)
Change-Id: Idf96a82bc6c8cb
(cherry picked from commit dfc01beab22f1c2