-
Bug
-
Resolution: Done
-
Medium
-
Casablanca Release
-
None
-
None
-
OOF-Casablanca-Sprint-3
In one flavor, we may got two hpa-features with the same name, but different values inside.
For example:
// Two 'sriovNICNetwork' features with different values {"hpa-feature": "sriovNICNetwork", "mandatory": "True", "architecture": "generic", "hpa-feature-attributes": [ {"hpa-attribute-key": "pciVendorId", "hpa-attribute-value": "1234", "operator": "=", "unit": ""}, {"hpa-attribute-key": "pciDeviceId", "hpa-attribute-value": "5678", "operator": "=", "unit": ""}, {"hpa-attribute-key": "pciCount", "hpa-attribute-value": "1", "operator": ">=", "unit": ""}, {"hpa-attribute-key": "providerNet", "hpa-attribute-value": "physnet1", "operator": "=", "unit": ""} ] }, {"hpa-feature": "sriovNICNetwork", "mandatory": "True", "architecture": "generic", "hpa-feature-attributes": [ {"hpa-attribute-key": "pciVendorId", "hpa-attribute-value": "1234", "operator": "=", "unit": ""}, {"hpa-attribute-key": "pciDeviceId", "hpa-attribute-value": "8765", "operator": "=", "unit": ""}, {"hpa-attribute-key": "pciCount", "hpa-attribute-value": "1", "operator": ">=", "unit": ""}, {"hpa-attribute-key": "providerNet", "hpa-attribute-value": "physnet2", "operator": "=", "unit": ""} ] }
Currently, our code cannot find the correct solution in situation like this.
- relates to
-
OPTFRA-322 Support SRIOV NIC
- Closed