sriov i/f not created in container in ipv6 environment
Bug #1836972 reported by
Brent Rowsell
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
Medium
|
Steven Webster |
Bug Description
Brief Description
-----------------
Cannot create a container with an sriov interface in an ipv6 deployment
Severity
--------
Major
Steps to Reproduce
------------------
In a ipv6 deployment, attempt to create a container with a sriov interface
Expected Behavior
------------------
Container should have a calico and and sriov interface
Actual Behavior
----------------
Container only has the container interface
Reproducibility
---------------
100%
System Configuration
-------
All
Branch/Pull Time/Commit
-------
Recent load
Last Pass
---------
Never
Timestamp/Logs
--------------
Not required, issue is 100% reproducible
Test Activity
-------------
Other
Changed in starlingx: | |
assignee: | nobody → Brent Rowsell (brent-rowsell) |
tags: | added: stx.2.0 stx.containers |
description: | updated |
tags: | added: stx.networking |
tags: | added: in-r-stx20 |
To post a comment you must log in.
This is an issue with the multus-cni image. /github. com/intel/ multus- cni/pull/ 238/commits/ 5513f6c744a73e9 bc42b09660dd030 971b3493b4
There is a pull request to fix the issue, but it has not been merged:
https:/
Perhaps we can ping the owners to get this merged. In the meantime, we will likely need to build the image in stx and apply the required fix to enable IPv6 deployments.