NetworkManager/clients
Thomas Haller c861e87b7f
cloud-setup: fix replacing IPv4 addresses during update
If previously the profile would track two addresses ("10.116.1.130/24",
"10.116.1.65/24"), and during an update the second address was removed
(leaving "10.116.1.130/24"), then the addresses of the profile were
wrongly not changed.

The effect is that removing a secondary IP address might not take
effect.

Fix that.

https://bugzilla.redhat.com/show_bug.cgi?id=1920838

Fixes: 69f048bf0c ('cloud-setup: add tool for automatic IP configuration in cloud')
(cherry picked from commit bbd36be44a)
2021-03-12 12:43:03 +01:00
..
cli cli: fix showing active state for nmcli con show with fields 2020-10-09 10:24:02 +02:00
cloud-setup cloud-setup: fix replacing IPv4 addresses during update 2021-03-12 12:43:03 +01:00
common Revert "dns: change default DNS priority of VPNs to -50" 2020-11-23 19:00:15 +01:00
tests Correct python black rules 2021-02-09 10:55:13 +01:00
tui all: unify comment style for SPDX-License-Identifier tag 2020-09-29 16:50:53 +02:00
meson.build docs: generate nm-settings-docs-nmcli.xml based on nmcli meta data 2020-06-11 10:53:50 +02:00
nm-online.c all: unify comment style for SPDX-License-Identifier tag 2020-09-29 16:50:53 +02:00