additional ip is not removed after try/revert

Bug #1931113 reported by Philipp Gassmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Netplan
New
Undecided
Unassigned

Bug Description

Add additional file

/etc/netplan/51-floating.yaml:
---
network:
    version: 2
    ethernets:
        eth0:
            addresses:
                    - 172.16.16.16/32
...

Run: netplan try --timeout 10

Result:
IP is added to the interface, but not removed after the revert from netplan try.

Expected result:
If an ip is added by netplan try, it should be removed after the revert.

System:
Ubuntu 20.04

# dpkg -l | grep netplan
ii libnetplan0:amd64 0.102-0ubuntu1~20.04.2
ii netplan.io 0.102-0ubuntu1~20.04.2

System Type: Hetzner.com cloud server with default cloud-init:

cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by the datasource. Changes
# to it will not persist across an instance reboot. To disable cloud-init's
# network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
    version: 2
    ethernets:
        eth0:
            addresses:
            - 2a01:4f8:dead:beef::1/64
            dhcp4: true
            gateway6: fe80::1
            match:
                macaddress: 96:00:00:00:00:00
            set-name: eth0

description: updated
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.