BZ1990953: Only the first container can use SR-IOV network attachment #38234
Conversation
openshift-ci
bot
added
the
size/XS
|
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: afd3277 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/617c5d8cc7dee70008647764 😎 Browse the preview: https://deploy-preview-38234--osdocs.netlify.app/openshift-enterprise/latest/networking/hardware_networks/add-pod |
|
✔️ Deploy Preview for osdocs ready! 🔨 Explore the source changes: c4cbf17 🔍 Inspect the deploy log: https://app.netlify.com/sites/osdocs/deploys/618ddc5bb187f50008ddc459 😎 Browse the preview: https://deploy-preview-38234--osdocs.netlify.app/openshift-enterprise/latest/networking/hardware_networks/add-pod |
|
@zshi-redhat, I re-opened this under a separate PR. |
Thanks @jboxman ! /lgtm |
|
/bugzilla refresh |
|
@zshi-redhat: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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/test-infra repository. |
|
PR title may need to change from |
jboxman-rh
changed the title
|
/bugzilla refresh |
|
@jboxman-rh: No Bugzilla bug is referenced in the title of this pull request. In response to this:
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/test-infra repository. |
modules/nw-multus-add-pod.adoc
Outdated
|
|
||
| If you are using an Intel network interface controller (NIC) in Data Plane Development Kit (DPDK) mode, only the first container in your pod is configured to access the NIC. Your SR-IOV additional network is configured for DPDK mode if the `deviceType` is set to `vfio-pci` in the `SriovNetworkNodePolicy` object. | ||
|
|
||
| You can workaround this issue by either ensuring that the container that needs access to the NIC is the first container defined in the `Pod` object or by disabling the Network Resource Injector. For more information, see link:https://bugzilla.redhat.com/show_bug.cgi?id=1990953[BZ#1990953]. |
There was a problem hiding this comment.
I believe "workaround" is a noun only. If you want to make it a verb, I'd say "You can work around"
|
New changes are detected. LGTM label has been removed. |
|
/cherry-pick enterprise-4.10 |
|
@jboxman-rh: new pull request created: #38696 In response to this:
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/test-infra repository. |
|
/cherry-pick enterprise-4.9 |
|
@jboxman-rh: new pull request created: #38697 In response to this:
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/test-infra repository. |
|
/cherry-pick enterprise-4.8 |
|
@jboxman-rh: new pull request created: #38698 In response to this:
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/test-infra repository. |
|
/cherry-pick enterprise-4.7 |
|
@jboxman-rh: new pull request created: #38699 In response to this:
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/test-infra repository. |
|
/cherry-pick enterprise-4.6 |
|
@jboxman-rh: new pull request created: #38700 In response to this:
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/test-infra repository. |
https://bugzilla.redhat.com/show_bug.cgi?id=1990953