Warning: This build has drifted.
The coverage report for this pull request build may be inaccurate because its base commit is no longer the HEAD of its target branch.
This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

    • Learn more: For more information on this, see Tracking coverage changes for pull request builds.
    • Fix now: For a quick fix, rebase this PR at GitHub. Your next report should be accurate.
    • Prevent going forward: To avoid this issue with future PRs, see these Recommended CI Configurations.

fix: skip unallocated pods during IPAM initialization to avoid spurious errors

During controller startup, InitIPAM() iterates over all pods and calls
getPodKubeovnNets(), which checks namespace network annotations. However,
namespace annotations are not yet set at this point because the namespace
worker starts after InitIPAM(). This causes spurious error logs like
"namespace kube-system network annotations is empty" for pods that have
not been allocated an IP by kube-ovn (e.g., coredns on first startup).

Skip pods without any allocated annotation before calling
getPodKubeovnNets(), since they have no IP to restore into IPAM anyway.

Signed-off-by: Mengxin Liu <liumengxinfly@gmail.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Mengxin Liu <liumengxinfly@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>