What is the probability and severity of the issue? I.e. the overall risk

• Probability: High – This occurs during an upgrade from RHOSP 17.1.3 to 17.1.4, which is a common operation.
• Severity: Critical – The issue prevents instances from spawning that rely on SR-IOV networking, making it a major blocker for affected customers. 

Does this affect specific configurations, hardware, environmental factors, etc.?

• Yes, this specifically affects SR-IOV enabled compute nodes running RHOSP 17.1.4.
• It occurs on HPE ProLiant DL360 Gen10 servers with Intel Ethernet Controller XXV710 NICs.
• The issue is tied to the os-net-config-sriov service, failing due to a missing drivers_autoprobe key.

What proportion of our customers could hit this issue?

• Any customer using SR-IOV networking in RHOSP 17.1.4 could encounter this issue.

Does this happen for only a specific use case?

• Yes, it occurs only when upgrading SR-IOV enabled computes from RHOSP 17.1.3 to 17.1.4.
• Affects customers relying on VF (Virtual Function) interfaces for networking.

Is there a clear workaround?

• Potential workaround: Manually modify the os-net-config-sriov script to handle missing drivers_autoprobe.
• However, this is not a long-term fix and may not be viable at scale.

Doc impact:

• Upgrade documentation for SR-IOV in RHOSP 17.1.4 should mention this issue.
• If a workaround is identified, it should be documented in Known Issues.