Skip to content

ovs: fix triggering stage3 activation without DHCP client initialized

Fernando Fernández Mancera requested to merge ff/fix_no_dhcp_ovs into main

Summary

It is possible that we learn the link is ready on stage3_ip_config rather than in link_changed event due to a stage3_ip_config scheduled by another component. In such cases, we proceed with IP configuration without allocating the resources needed like initializing DHCP client.

In order to avoid that, if we learn during stage3_ip_config that the link is now ready, we need to schedule another stage3_ip_config to allocate the resources we might need.

Purpose

Fix a race condition when we proceed with IP configuration without DHCP client initialization.

Checklist

Please read https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/main/CONTRIBUTING.md before opening the merge request. In particular, check that:

  • the subject for all commits is concise and explicative
  • the message for all commits explains the reason for the change
  • the source is properly formatted
  • any relevant documentation is up to date
  • you have added unit tests if applicable
  • the NEWS file is updated when the change deserves to be mentioned, for example for new features, behavior changes, API deprecations, etc.

Merge request reports