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.

Sign up for GitHub

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

Jump to bottom

Flaky CI: Virtual Machines Check the client When all the VMs are not serviced by default (opt-in mode) and kubemacpool is not opted-in on a namespace and 2 vms is created in the non opted-in namespace and another vm is created in an opted-in namespace and kubemacpool restarts should still reject a new opted-in VM object with the occupied MAC assigned #450

Open
RamLavi opened this issue Jan 7, 2025 · 0 comments
Open

Flaky CI: Virtual Machines Check the client When all the VMs are not serviced by default (opt-in mode) and kubemacpool is not opted-in on a namespace and 2 vms is created in the non opted-in namespace and another vm is created in an opted-in namespace and kubemacpool restarts should still reject a new opted-in VM object with the occupied MAC assigned #450

RamLavi opened this issue Jan 7, 2025 · 0 comments

Comments

@RamLavi
Copy link
Member

RamLavi commented Jan 7, 2025

What happened:
failed here

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:
@RamLavi RamLavi changed the title Flaky CI: ]Virtual Machines Check the client When all the VMs are not serviced by default (opt-in mode) and kubemacpool is not opted-in on a namespace and 2 vms is created in the non opted-in namespace and another vm is created in an opted-in namespace and kubemacpool restarts should still reject a new opted-in VM object with the occupied MAC assigned Flaky CI: Virtual Machines Check the client When all the VMs are not serviced by default (opt-in mode) and kubemacpool is not opted-in on a namespace and 2 vms is created in the non opted-in namespace and another vm is created in an opted-in namespace and kubemacpool restarts should still reject a new opted-in VM object with the occupied MAC assigned Jan 7, 2025
@RamLavi RamLavi mentioned this issue Jan 7, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@RamLavi