-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The networkd.service isn't masked (disabled) when installing network-manager by preload #167
Comments
Created Jira card to investigate: https://warthogs.atlassian.net/browse/SNAPDENG-14960 |
Probably canonical/netplan#449 would help with this - my guess is that networkd is getting control of the interface while it shouldn't. |
@alfonsosanchezbeato Thanks for your effort. But there is another #214 that is merged too as a workaround for core22. 2 PRs' logic is the same. Checking networked configurations to restart networked if any change. |
@LaiderLai to be clear, the networkd service cannot be removed when network-manager is installed as it is part of the base. It may even be started at some times as it is socket activated. What should not happen is that it takes control of devices if NM is around (unless configured to do so). Therefore, |
Hi @alfonsosanchezbeato , sorry, I think I used the wrong words to make you misunderstand. Please reference the below operation log between 2 UC22 images. For A, the systemd-networkd.service is working as expected. After a system reboot, the systemd-networkd.service is under inactive status as expected. For B, it's a weird scenario. Do you have any idea about this scenario?
|
There is an issue scenario from core20/core22 with the latest snapd and network-manager. (including x86/arm64)
If users install network-manager by
sudo snap install
, the default networkd related services are disabled correctly.However, if users preload network-manager by model assertion, the networked related services still work there.
It means the networked and network-manager are working at the same time on a platform and it may bring out some problems.
Not sure if the handling is broken at core-base or snaps. Need core-base/snapd developer help to check it. Tks.
The text was updated successfully, but these errors were encountered: