Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1913932 +++
Description of problem:
From customer (SAP):
"Groking through the code I see the project is determined using the metadata services of the Instance, this will not work in the case of a shared service project
There needs to be a feature enabled to support a project to be a user-defined input within the context of the VPC since the VPC and its routes may reside in the host project, while the instance may reside in the service project so companies who leverages shared service project will not benefit by using this resource agent since it will not work as expected, it will fail to determine the VPC and the routes since it will not exist"
Seems to be tied conceptually to this: https://cloud.google.com/vpc/docs/shared-vpc
I have not constructed a test environment for a shared service project (I'm not sure whether I even have the necessary privileges to do so). But it should be straightforward to add a resource attribute for project and sanity-test it, if this fix prevents the resources from breaking valid customer use cases.
-----
Version-Release number of selected component (if applicable):
resource-agents-gcp-4.1.1-61.el7_9.4
master
-----
How reproducible:
Always (based on description)
-----
Steps to Reproduce:
Create an instance so that "the VPC and its routes may reside in the host project, while the instance may reside in the service project."
- https://cloud.google.com/vpc/docs/shared-vpc
Attempt to start a gcp-vpc-move-route or gcp-vpc-move-vip resource.
-----
Actual results:
Operation fails. Will request failure details from reporter.
-----
Expected results:
Operation succeeds.
Comment 3Oyvind Albrigtsen
2021-01-19 10:06:32 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (resource-agents bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2021:0858