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 1623084 - [RFE] - make Network Manager work best of public clouds.
Summary: [RFE] - make Network Manager work best of public clouds.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.2
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 8.2
Assignee: Thomas Haller
QA Contact: Vladimir Benes
URL:
Whiteboard:
Depends On: 1642461 1791212 1821787 1823315 1867997
Blocks: 1868000
TreeView+ depends on / blocked
 
Reported: 2018-08-28 12:51 UTC by Yaniv Lavi
Modified: 2021-05-18 13:30 UTC (History)
22 users (show)

Fixed In Version: NetworkManager-1.28.0-0.1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 13:29:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Yaniv Lavi 2018-08-28 12:51:10 UTC 
Description of problem:

RH CoreOS expressed the need to have out of the box defaults for public cloud deployments. Their defaults for networkd from container linux are:
https://github.com/coreos/bootengine/tree/master/dracut/03coreos-network

EC2 also added similar capabilities using ec2-net-utils:
https://github.com/lorengordon/ec2-net-utils

This request is to bake these default to network manager and RHEL, so we can get the best out of the box experience for cloud instances.
Comment 3 Thomas Haller 2019-02-26 15:43:30 UTC 
see also bug 1642461
Comment 4 sushil kulkarni 2019-04-23 13:21:57 UTC 
Dropping this from the RPL. This needs more investigation. Will continue the investigation work on using NM in AWS, Azure and CoreOS and create separate bzs for any work that comes out of the effort to make NM more usable in such environments.

-Sushil
Comment 5 Marcelo Ricardo Leitner 2019-07-03 15:11:24 UTC 
Mass-moving bugs RHEL <= 7.6.0 to 7.7.0.
As we are past RFE deadline for 7.7.0 and we should have no new features on 7.8.0, please evaluate if it's still wanted on RHEL7 and contact PM for exception. You may also move it to RHEL8 if that's wanted. Thanks!
Comment 7 Thomas Haller 2019-08-08 06:05:31 UTC 
During a meeting with ailan, ribarry we discussed the following:

So far, these pain points identified are:

 - dynamic IP address configuration and secondary IP addresses (bug 1642461)

 - possibly on Azure bonding of interfaces (now done in kernel, should require no work from NM, bug 1519138)

 - maybe other Azure bugs, but those are closed or seem under control (e.g. bug 1720157)
Comment 9 Thomas Haller 2020-08-11 11:27:25 UTC 
in the meantime, nm-cloud-setup was added and support EC2, GCE and Azure (IPv4 only).


It does a similar job as SUSE's cloud-netconfig ([1], [2]) and the ec2 tools ([3], [4]).

Also, CoreOS is now using NetworkManager and hopefully can start using this tool ([5], [6]).

[1] https://www.suse.com/c/multi-nic-cloud-netconfig-ec2-azure/
[2] https://github.com/SUSE-Enceladus/cloud-netconfig

[3] https://github.com/lorengordon/ec2-net-utils
[4] https://github.com/aws/ec2-net-utils.git

[5] https://github.com/coreos/bootengine/tree/master/dracut/03coreos-network
[6] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/407



See also:

  * Secondary interface on Amazon

      * https://aws.amazon.com/premiumsupport/knowledge-center/ec2-centos-rhel-secondary-interface/

      * https://aws.amazon.com/premiumsupport/knowledge-center/ec2-ubuntu-secondary-network-interface/




This bug in it's general sense is thus fixed upstream (and partly in rhel-8.3).
rhel-8.4 will also get nm-cloud-support for Azure.


What we need now is more testing, more documentation, and enable it by default.

Moving this bug to MODIFIED.
Comment 15 Yuxin Sun 2020-10-20 08:28:23 UTC 
Hi @Thomas,

Is this package ready for Azure now? It seems that it was not ready for Azure in comment 9. Could you please help to update the current status? Thanks!
Comment 16 Thomas Haller 2020-10-20 09:22:17 UTC 
(In reply to Yuxin Sun from comment #15)
> Is this package ready for Azure now? It seems that it was not ready for
> Azure in comment 9. Could you please help to update the current status?

support for Azure was added upstream in version 1.28.0.

It will be thus be introduced in rhel-8.4.

This rhbz is not very specific and not particularly about Azure. But we will declare it as complete with rhel-8.4, when it also has Azure support. So the "Fixed In Version: NetworkManager-1.28.0-0.1.el8" is accurate and covers Azure as well.
Comment 17 Yuxin Sun 2020-10-21 08:40:33 UTC 
Thanks Thomas!

Verified in Azure VM with NetworkManager-1.28.0-0.1.el8 in RHEL-8.3. Can get 2 IP addresses.
Steps:
1. Configure 2 IP addresses in one NIC from Azure portal.
2. Set Environment=NM_CLOUD_SETUP_AZURE=yes in /usr/lib/systemd/system/nm-cloud-setup.service
3. systemctl restart nm-cloud-setup.service
4. ip addr
Can show the second IP.
5. systemctl enable nm-cloud-setup.service , then reboot, can get 2 IP addresses.
Comment 19 Yuxin Sun 2021-01-06 09:52:44 UTC 
Hi Thomas,

I see this issue recently on Azure: BZ#1912236 , which may block this BZ. Could you please help to have a look? Thanks!
Comment 20 Thomas Haller 2021-01-06 12:03:04 UTC 
(In reply to Yuxin Sun from comment #19)
> Hi Thomas,
> 
> I see this issue recently on Azure: BZ#1912236 , which may block this BZ.
> Could you please help to have a look? Thanks!

Hi, this rhbz is wide scoped and says basically to improve something about cloud with NetworkManager (and that was done, with nm-cloud-setup being the solution).

As the goal of this rhbz is not well defined, it seems not useful to have a very generic bug (like this) and keep it open if sub-issues appear.

Yes, you found an issue. Thank you. But that does not block this rhbz, instead is a new (related, follow-up) bug.
Comment 21 Yuxin Sun 2021-01-06 13:22:58 UTC 
(In reply to Thomas Haller from comment #20)
> (In reply to Yuxin Sun from comment #19)
> > Hi Thomas,
> > 
> > I see this issue recently on Azure: BZ#1912236 , which may block this BZ.
> > Could you please help to have a look? Thanks!
> 
> Hi, this rhbz is wide scoped and says basically to improve something about
> cloud with NetworkManager (and that was done, with nm-cloud-setup being the
> solution).
> 
> As the goal of this rhbz is not well defined, it seems not useful to have a
> very generic bug (like this) and keep it open if sub-issues appear.
> 
> Yes, you found an issue. Thank you. But that does not block this rhbz,
> instead is a new (related, follow-up) bug.

Understood. Thank you Thomas! I just removed 1912236 from depends on list.
Comment 22 Vladimir Benes 2021-01-25 14:19:32 UTC 
We are OK in AWS and GCP, there is a regression in Azure (Bug 1912236) that needs to be fixed.
Comment 27 errata-xmlrpc 2021-05-18 13:29:37 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 (Moderate: NetworkManager and libnma security, 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/RHSA-2021:1574
Note You need to log in before you can comment on or make changes to this bug.