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

[BUG] Can Create A Cluster Network & Config On Device Used for SR-IOV #4017

Closed
irishgordo opened this issue May 31, 2023 · 1 comment
Closed

[BUG] Can Create A Cluster Network & Config On Device Used for SR-IOV #4017

irishgordo opened this issue May 31, 2023 · 1 comment
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release reproduce/always Reproducible 100% of the time severity/1 Function broken (a critical incident with very high impact)

Comments

@irishgordo
Copy link

irishgordo commented May 31, 2023 •
edited

Describe the bug
On a node that has a network device, that network device can be used for a Cluster Network & Config.

To Reproduce
Steps to reproduce the behavior:

  1. Have enabled PCI Passthrough Addon
  2. Enable SR-IOV on the device
  3. Create VFs on the SR-IOV Device
  4. Enable Passthrough on those VFs
  5. Goto Cluster Network/Config
  6. Create a Cluster Network/Config, using that same uplink

Expected behavior
The device if being used for SR-IOV would not be allowed to be used for Cluster Network & Config
Based on HEP

Environment

  • Harvester ISO version: v1.2.0-rc1
  • Underlying Infrastructure: 3 node bare-metal HP Proliant

Additional context
Screenshot from 2023-05-31 16-51-48
Screenshot from 2023-05-31 16-43-14
Screenshot from 2023-05-31 16-42-17
Screenshot from 2023-05-31 16-41-59
@irishgordo irishgordo added kind/bug Issues that are defects reported by users or that we know have reached a real release severity/1 Function broken (a critical incident with very high impact) reproduce/always Reproducible 100% of the time labels May 31, 2023
@irishgordo irishgordo mentioned this issue Jun 1, 2023
Closed
@irishgordo
Copy link
Author

This is expected behavior, so I'll go ahead and close this out 😄 👍
cc: @ibrokethecloud

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Issues that are defects reported by users or that we know have reached a real release reproduce/always Reproducible 100% of the time severity/1 Function broken (a critical incident with very high impact)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@irishgordo