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.

Bug 1821787

Summary: nm-cloud-setup: add support for Google Cloud load-balancing routes
Product: Red Hat Enterprise Linux 8 Reporter: Thomas Haller <thaller>
Component: NetworkManagerAssignee: Antonio Cardace <acardace>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.3CC: acardace, atragler, bgalvani, jmaxwell, leiwang, lrintel, rkhan, sukulkar, thaller, till, vbenes, wshi, ymao
Target Milestone: rcKeywords: OtherQA
Target Release: 8.0Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: NetworkManager-1.26.0-2.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 01:49:42 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1623084, 1807630    

Description Thomas Haller 2020-04-07 15:50:56 UTC 
$SUBJECT.

More details at upstream bug https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/407
Comment 1 Antonio Cardace 2020-06-18 16:46:24 UTC 
MR up for review: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/546.

Tested on Google Cloud Platform VMs with a configured load balancer.
Comment 2 Antonio Cardace 2020-06-26 15:03:17 UTC 
Patch merged upstream https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/ccbae2422e0e415af1cc742fd3e35307415dda87.
Comment 8 Vladimir Benes 2020-09-01 12:23:32 UTC 
As Wei Shi <wshi> wrote:

forwarded_ip (in metadata) will be set to the Frontend IP (LB) after the load balancer is created,

# curl --silent -L -H "Metadata-Flavor: Google" "http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/forwarded-ips/0"
10.1.2.99

---

The configure steps I used to mimic the LB setup:
https://cloud.google.com/load-balancing/docs/internal/setting-up-internal#configure-test-environment

Image: RHEL-8.3.0-Snapshot-2.0 (NetworkManager-cloud-setup-1.26.0-6.el8.x86_64)

After LB is created, forwarded_ip in metadata will be set.
# curl --silent -L -H "Metadata-Flavor: Google" "http://metadata.google.internal/computeMetadata/v1/instance/network-interfaces/0/forwarded-ips/0"
10.1.2.99

stop nginx on all machines except vm-a1

Connect to the iLB addr will get error:
vm-client:~# curl http://10.1.2.99
curl: (7) Failed to connect to 10.1.2.99 port 80: Connection refused

Uncomment "Environment=NM_CLOUD_SETUP_GCP=yes" in /lib/systemd/system/nm-cloud-setup.service

vm-a1# systemctl restart nm-cloud-setup

vm-a1# ip route show table local
...
local 10.1.2.99 dev eth0 proto static scope host metric 100
...

Connect to the iLB addr will get the nginx sample page on vm-a1:
vm-client:~# curl http://10.1.2.99
HTTP/1.1 200 OK
...
...
Comment 11 errata-xmlrpc 2020-11-04 01:49:42 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 (NetworkManager 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-2020:4499