Thomas Haller 1e980c38e9 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) (cherry picked from commit c861e87b7f)		2021-03-12 13:17:45 +01:00
..
cli	cli: fix showing active state for nmcli con show with fields	2020-10-13 21:47:14 +02:00
cloud-setup	cloud-setup: fix replacing IPv4 addresses during update	2021-03-12 13:17:45 +01:00
common	libnm-core,clients: add support for ipv4.dhcp-vendor-class-identifier option	2020-08-26 11:57:19 +02:00
tests	Correct python black rules	2021-02-09 11:51:25 +01:00
tui	tui: allow configuring "primary" bond option with "balance-{alb,tlb}"	2020-09-10 22:17:05 +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	nm-online: allow configuring timeout via NM_ONLINE_TIMEOUT environment	2020-04-30 21:46:59 +02:00