What is the probability and severity of the issue? I.e. the overall risk
NiC partitioning feature with DPDK ports is broken . Its fairly low/medium risk. It's always reproducible for the given use case.

Does this affect specific configurations, hardware, environmental factors, etc.?
NIC Partitioning with DPDK ports on Intel cards

Are any partners relying on this functionality in order to ship an ecosystem product?
rh-ee-gurpsing Can you please provide the details here

[GS] If these are specific to NIC partitioning with NMstate, partners should not be impacted as long as they do not transition to using NMstate. I am not aware of any partners solutions relying on NIC partitioning  

What proportion of our customers could hit this issue?
rh-ee-gurpsing Can you please provide the details here

 [GS] Intel NIC cards are use by over 50% of the customers, but NIC partitioning deployment is a very small percentage of that (under 5%). 

Does this happen for only a specific use case?
Yes, it affects only NIC Partitioning + DPDK ports on intel cards

What proportion of our CI infrastructure, automation, and test cases does this issue impact?
NIC Partitioning CI Jobs and SR-IOV CI-Jobs needs to be verified

Is this a regression in supported functionality from a previous release?
Yes

Is there a clear workaround?
No

Is there potential doc impact?
No

If this is a UI issue:
Is the UI still fit for its purpose/goal?
Not Applicable

Does the bug compromise the overall trustworthiness of the UI?
Not Applicable

Overall context and effort – is the overall impact bigger/worse than the bug in isolation? For example, 1 workaround might seem ok, 5 is getting ugly, 20 might be unacceptable (rough numbers).