Skip to content
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

Ipam lane flakes on the first test #1857

Closed
oshoval opened this issue Aug 13, 2024 · 4 comments
Closed

Ipam lane flakes on the first test #1857

oshoval opened this issue Aug 13, 2024 · 4 comments
Assignees
Labels

Comments

@oshoval
Copy link
Collaborator

oshoval commented Aug 13, 2024

What happened:
The IPAM lane fails on the first test sometimes.

What you expected to happen:
Should be stable and pass.

How to reproduce it (as minimally and precisely as possible):
Steps to reproduce the behavior.

Additional context:
Going to add logs so it will ease investigating IPAM lane generally.
kubevirt/ipam-extensions#57 (need to consume on CNAO once merged).
For now just retest once happens please

Environment:

  • KubeVirt version (use virtctl version): N/A
  • Kubernetes version (use kubectl version): N/A
  • VM or VMI specifications: N/A
  • Cloud provider or hardware configuration: N/A
  • OS (e.g. from /etc/os-release): N/A
  • Kernel (e.g. uname -a): N/A
  • Install tools: N/A
  • Others: N/A
@oshoval oshoval self-assigned this Aug 13, 2024
@oshoval
Copy link
Collaborator Author

oshoval commented Aug 13, 2024

Note:
It happens also on the repo itself kubevirt/ipam-extensions#57 (comment)
hence not related to CNAO at all (i bet related to OVN itself, but will investigate first)

@oshoval
Copy link
Collaborator Author

oshoval commented Aug 14, 2024

OVN retry bug was merged
in case this bug suddenly gone, it means it is related
anyhow adding logs so it will be easier to find this or other bugs

@oshoval
Copy link
Collaborator Author

oshoval commented Aug 19, 2024

Created #1876

lately the lane didnt fail, maybe the OVN changes fixed it (we are taking latest main branch automatically).

Lets close this issue, and if the bug returns we will have logs now, which will allow us to debug

@oshoval
Copy link
Collaborator Author

oshoval commented Sep 8, 2024

For some reason it failed here (not on the first test) as the issue describes
and didnt collect the artifacts
https://github.com/kubevirt/cluster-network-addons-operator/actions/runs/10738617949/job/29782567218?pr=1840
if it repeats / once there is time we should investigate it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant