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

multus install broken on reboot #1810

Open
kfox1111 opened this issue Jun 18, 2024 · 7 comments
Open

multus install broken on reboot #1810

kfox1111 opened this issue Jun 18, 2024 · 7 comments
Labels

Comments

@kfox1111
Copy link

https://github.com/kubevirt/cluster-network-addons-operator/blob/main/data/multus/001-multus.yaml#L179-L182

needs the fix as described here:
https://github.com/k8snetworkplumbingwg/multus-cni/pull/1213/files#diff-70f0e7b0ef7f980082ffd2486d26c037ed565ed340245067916736c9b7195c0e

or else things break on node reboot.

@kfox1111
Copy link
Author

Tried digging through things, but not sure how the binaries at bitnami/containers are actually built for the container.

@kubevirt-bot
Copy link
Collaborator

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 16, 2024
@kubevirt-bot
Copy link
Collaborator

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

@kubevirt-bot kubevirt-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Oct 16, 2024
@kubevirt-bot
Copy link
Collaborator

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

@kubevirt-bot
Copy link
Collaborator

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kfox1111
Copy link
Author

/reopen
/remove-lifecycle rotten

Just tested. still an issue

@kubevirt-bot kubevirt-bot reopened this Nov 16, 2024
@kubevirt-bot
Copy link
Collaborator

@kfox1111: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Just tested. still an issue

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@kubevirt-bot kubevirt-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Nov 16, 2024
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

2 participants