-
Notifications
You must be signed in to change notification settings - Fork 921
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
NetworkManager activator failed to apply DataSourceNoCloudNet network configuration #6064
Labels
bug
Something isn't working correctly
Comments
RHEL internal ticket https://issues.redhat.com/browse/RHEL-81703 |
ani-sinha
added a commit
to ani-sinha/cloud-init
that referenced
this issue
Mar 4, 2025
…ork conns Reloading the network manager service is equivalent to "nmcli reload" and this command only reloads the global .conf files and DNS config, not connections. This means changes to connection files will not take effect. For those to take effect, we need "nmcli conn load/reload" and then "nmcli conn up". Thus, reloading network manager as well as reloading the connections are required to cover all cases. While at it, rename "reload-or-try-restart" -> "try-reload-or-restart" since the former is legacy and the later is the officially documented sub-command. Fixes: canonicalGH-6064 Fixes: bde913a ("fix(NetworkManager): Fix network activator") Signed-off-by: Ani Sinha <[email protected]>
ani-sinha
added a commit
to ani-sinha/cloud-init
that referenced
this issue
Mar 4, 2025
…ork conns Reloading the network manager service is equivalent to "nmcli reload" and this command only reloads the global .conf files and DNS config, not connections. This means changes to connection files will not take effect. For those to take effect, we need "nmcli conn load/reload" and then "nmcli conn up". Thus, reloading network manager as well as reloading the connections are required to cover all cases. Also see canonical#5512 (comment) While at it, rename "reload-or-try-restart" -> "try-reload-or-restart" since the former is legacy and the later is the officially documented sub-command. Fixes: canonicalGH-6064 Fixes: bde913a ("fix(NetworkManager): Fix network activator") Signed-off-by: Ani Sinha <[email protected]>
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
I tested “(NoCloudNet): Add network-config support” (24.3+) with a RHEL KVM instance and found that when network-config contains static IP, cloud-init created configuration file but it was ineffective.
The root cause is the command ['systemctl', 'reload-or-try-restart', 'NetworkManager.service'] does not apply the changes to an active connection.
We may need the solution that Ani mentioned before, see this comment
#5512 (comment)
I also have another question about "“Applying network configuration from fallback” in " "init-local" stage, which created the DHCP network configuration, is it expected or not?
Steps to reproduce the problem
Prepare network data in http server and then launch a KVM instance
For example, using rhel9 guest image which contains cloud-init 24.4 to create a KVM instance,
br1.xml
virsh net-define br1.xml
virsh net-start br1
sudo virt-install --name ${DOMAIN_NAME} --disk /var/lib/libvirt/images/${RHEL_CLOUD_IMAGE},device=disk,bus=virtio,format=qcow2 --os-variant rhel-unknown --network bridge=virbr1,model=virtio --graphics none --sysinfo system.serial="ds=nocloud;s=http://10.0.2.1:8000/" --import
Environment details
cloud-init logs
cloud-init_rhel9.log
The text was updated successfully, but these errors were encountered: