Status Update
Comments
ba...@google.com <ba...@google.com>
ma...@google.com <ma...@google.com> #2
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback. Thank you for your understanding and collaboration.
Thanks & Regards,
Ashalatha
Google Cloud Support
np...@paypal.com <np...@paypal.com> #3
da...@google.com <da...@google.com> #4
Thanks
on...@google.com <on...@google.com>
on...@google.com <on...@google.com>
ss...@google.com <ss...@google.com> #5
any update about ETA for this ask ?
Thanks
ka...@google.com <ka...@google.com> #6
This is also important to my Cx. So now there are Cx from multiple regions requesting this ask.
Description
Here GCP Project is taken as example, but other objects like service account, user accounts also have the same issue.
When a project listed in the IngressTo or EgressTo section of a VPC Service Controls perimeter is deleted (perimeter with Dry Run enabled), subsequent updates to the perimeter become impossible. This creates a deadlock situation where attempts to update the enforced configuration or dry run configuration result in the following error message:
Error 400: com.google.apps.framework.request.NotFoundException: Project, projects/447257904342, does not exist.
Steps to Reproduce:
Create a VPC Service Controls perimeter and add a project to the IngressTo or EgressTo section.
Enable Dry Run for the perimeter.
Delete the project from the GCP Console or via gcloud commands.
Attempt to update the VPC SC perimeter to remove the deleted project from IngressTo or EgressTo.
Expected Behaviour:
The update to the VPC SC perimeter should succeed without error, allowing the removal of the deleted project.
Actual Behaviour:
The update fails with a NotFoundException, leading to a deadlock situation.
Impact:
This issue prevents necessary updates to VPC SC perimeters, potentially affecting security configurations and resource access management.
Proposed Solution:
Consider enhancing the handling of deleted projects or objects within VPC Service Controls, particularly when Dry Run is enabled. Automatically removing non-existent projects or objects from the Dry Run configuration could help resolve this issue.