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.
Bug 1913936 - gcp-vpc-move-route, gcp-vpc-move-vip: Failures if the instance is in a shared service project [rhel-7.9.z]
Summary: gcp-vpc-move-route, gcp-vpc-move-vip: Failures if the instance is in a shared...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: resource-agents
Version: 7.9
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Oyvind Albrigtsen
QA Contact: Brandon Perkins
URL:
Whiteboard:
Depends On:
Blocks: 1919343 1919344
TreeView+ depends on / blocked
 
Reported: 2021-01-07 19:59 UTC by Reid Wahl
Modified: 2021-03-16 13:56 UTC (History)
9 users (show)

Fixed In Version: resource-agents-4.1.1-61.el7_9.8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1913932
: 1919343 1919344 (view as bug list)
Environment:
Last Closed: 2021-03-16 13:56:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github ClusterLabs resource-agents pull 1604 0 None closed gcp-vpc-move-route, gcp-vpc-move-vip: Parameterize project ID 2021-02-15 14:44:21 UTC
Red Hat Knowledge Base (Solution) 5716021 0 None None None 2021-01-20 00:04:44 UTC

Description Reid Wahl 2021-01-07 19:59:32 UTC 
+++ 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 3 Oyvind Albrigtsen 2021-01-19 10:06:32 UTC 
Additional patch to fix stop-action and incorrect call of a function: https://github.com/ClusterLabs/resource-agents/pull/1609
Comment 11 Michael Varun 2021-03-01 17:35:36 UTC 
Team, I See the service account is not parametrised yet does it include in this change ?
Comment 12 Oyvind Albrigtsen 2021-03-02 10:59:25 UTC 
This is the bz to implement it in RHEL 7.9z.
Comment 17 errata-xmlrpc 2021-03-16 13:56:25 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
Note You need to log in before you can comment on or make changes to this bug.