network interruption when there is no change on the netplan config
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Netplan |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Network interruption may occur even when there is no change on the netplan config. eg: when running 'juju config ovn-chassis sriov-numvfs=
I checked the code [1], it has the following code comment:
# Re-start service when
# 1. We have configuration files for it
# 2. Previously we had config files for it but not anymore
# Ideally we should compare the content of the *netplan-* files before and
# after generation to minimize the number of re-starts, but the conditions
# above works too.
So running 'netplan apply' will cause a networkd restart if there are existing *netplan-* files present. I think we had better compare the content of the *netplan-* files before and after generation to minimize the number of re-starts.
[What is known and has been done so far?]
A snippet from the syslog
https:/
[Distribution/
Jammy/Yoga
[Steps to Reproduce]
'netplan apply'
[1] https:/
description: | updated |
tags: | added: sts |
Yes, Netplan should implement improved/seamless "netplan apply" and only re-configure interfaces that actually changes, instead of re-configuring all interfaces or re-starting the full networking daemon.
(See FR-3700)