Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionCarlos Goncalves
2023-02-02 09:09:31 UTC
As an OpenShift cluster administrator, I would like to create SR-IOV VFs and configure them in a single context so that I can use them as gateway network interfaces for the SDN and other host services at node provision time (day-1 operations).
Currently, this is not possible. The only way is to first enable the SR-IOV VFs and then (in a second context) configure them. Doing this in a two-part is not possible at node provisioning.
Example:
interfaces:
- name: eno1
type: ethernet
ethernet:
sr-iov:
total-vfs: 1
- name: eno1v0
type: ethernet
state: up
ipv4:
dhcp: true
enabled: true
Patch sent to upstream: https://github.com/nmstate/nmstate/pull/2225
Considering VF might have different naming scheme, please use `sriov:<pf_name>:<vf_id>` to refer the about-to-create VF.
For example:
```yml
---
interfaces:
- name: sriov:eth1:1
type: ethernet
state: up
ipv4:
enabled: false
ipv6:
enabled: false
- name: eth1
type: ethernet
state: up
ethernet:
sr-iov:
total-vfs: 2
```
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (nmstate bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2023:2190
As an OpenShift cluster administrator, I would like to create SR-IOV VFs and configure them in a single context so that I can use them as gateway network interfaces for the SDN and other host services at node provision time (day-1 operations). Currently, this is not possible. The only way is to first enable the SR-IOV VFs and then (in a second context) configure them. Doing this in a two-part is not possible at node provisioning. Example: interfaces: - name: eno1 type: ethernet ethernet: sr-iov: total-vfs: 1 - name: eno1v0 type: ethernet state: up ipv4: dhcp: true enabled: true