| 2021-08-03 14:10:00 |
Oliver Grawert |
bug |
|
|
added bug |
| 2021-08-03 14:10:26 |
Oliver Grawert |
description |
when ourging NM, all teh connection info stays around in /etc/netplan:
$ snap remove --purge network-manager
...
network-manager removed
$ ls /etc/netplan/
00-default-nm-renderer.yaml 90-NM-2b0d0f1d-b79d-43af-bde1-71744625642e.yaml 90-NM-4a224744-3bc7-31c9-8346-adcb6136990f.yaml
while i would expect this behaviour when just removing, i think --purge should actually remove all remaining config bits (and preferable restore the original netwplan yaml files) ... |
when ourging NM, all the connection info stays around in /etc/netplan:
$ snap remove --purge network-manager
...
network-manager removed
$ ls /etc/netplan/
00-default-nm-renderer.yaml 90-NM-2b0d0f1d-b79d-43af-bde1-71744625642e.yaml 90-NM-4a224744-3bc7-31c9-8346-adcb6136990f.yaml
while i would expect this behaviour when just removing, i think --purge should actually remove all remaining config bits (and preferable restore the original netplan yaml files) ... |
|
| 2021-08-03 14:10:52 |
Oliver Grawert |
description |
when ourging NM, all the connection info stays around in /etc/netplan:
$ snap remove --purge network-manager
...
network-manager removed
$ ls /etc/netplan/
00-default-nm-renderer.yaml 90-NM-2b0d0f1d-b79d-43af-bde1-71744625642e.yaml 90-NM-4a224744-3bc7-31c9-8346-adcb6136990f.yaml
while i would expect this behaviour when just removing, i think --purge should actually remove all remaining config bits (and preferable restore the original netplan yaml files) ... |
when purging NM, all the connection info stays around in /etc/netplan:
$ snap remove --purge network-manager
...
network-manager removed
$ ls /etc/netplan/
00-default-nm-renderer.yaml 90-NM-2b0d0f1d-b79d-43af-bde1-71744625642e.yaml 90-NM-4a224744-3bc7-31c9-8346-adcb6136990f.yaml
while i would expect this behaviour when just removing, i think --purge should actually remove all remaining config bits (and preferable restore the original netplan yaml files) ... |
|
| 2021-08-03 14:11:39 |
Oliver Grawert |
description |
when purging NM, all the connection info stays around in /etc/netplan:
$ snap remove --purge network-manager
...
network-manager removed
$ ls /etc/netplan/
00-default-nm-renderer.yaml 90-NM-2b0d0f1d-b79d-43af-bde1-71744625642e.yaml 90-NM-4a224744-3bc7-31c9-8346-adcb6136990f.yaml
while i would expect this behaviour when just removing, i think --purge should actually remove all remaining config bits (and preferable restore the original netplan yaml files) ... |
when purging NM, all the connection info stays around in /etc/netplan:
$ snap remove --purge network-manager
...
network-manager removed
$ ls /etc/netplan/
00-default-nm-renderer.yaml 90-NM-2b0d0f1d-b79d-43af-bde1-71744625642e.yaml 90-NM-4a224744-3bc7-31c9-8346-adcb6136990f.yaml
while i would expect this behaviour when just removing, i think --purge should actually remove all remaining config bits (and preferably restore the original netplan yaml files) ... |
|
