Bug 1623084

see also bug 1642461

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

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!

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)

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.

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!

(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.

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.

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!

(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.

(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.

We are OK in AWS and GCP, there is a regression in Azure (Bug 1912236) that needs to be fixed.

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