StarlingX isolcpus resource reported as "windriver.com/isolcpus"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Triaged
|
Low
|
Unassigned |
Bug Description
Currently in StarlingX the custom isolated CPUs resource is reported as "windriver.
Severity: Minor
Steps to Reproduce:
Configure isolated CPUs via "system host-cpu-modify", then run "kubectl describe node <hostname>" to see the isolated CPU resources.
Expected Behavior:
Should use the starlingx name for upstream code rather than windriver.com.
Actual Behavior:
Uses windriver.com as the resource name in starlingx.
Reproducibility:
Reproducible
The complicating factors are that we can't break existing customer applications which are using the windriver.
A possible fix would be to modify the system to accept both names for one release and deprecate the windriver.
tags: | added: stx.containers stx.integ |
screening: low priority / not gating issue, but should be considered for a fix.