-
Bug
-
Resolution: Done
-
Major
-
4.17.z, 4.16.z, 4.18.z, 4.19.0
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
Proposed
-
CLOUD Sprint 271, CLOUD Sprint 272, CLOUD Sprint 273, CLOUD Sprint 274, CLOUD Sprint 275, CLOUD Sprint 276
-
6
-
Done
-
Bug Fix
-
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-56168. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-56167. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-56163. The following is the description of the original issue:
—
This is a clone of issue OCPBUGS-55372. The following is the description of the original issue:
—
When attempting to reference a Capacity Reservation Group across subscriptions MAPI fails with the following error.
failed to create vm tst-redacted-northeurope1-rhjzl: failure sending request for machine tst-redacted-northeurope1-rhjzl: cannot create vm: compute.VirtualMachinesClient#CreateOrUpdate: Failure sending request: StatusCode=400 – Original Error: Code="BadRequest" Message="Cross subscription association with capacity reservations is not supported for api versions below 2022-11-01."
Unfortunately it looks like fixing this would require an Azure SDK bump as v0.68 does not include references to the API version mentioned above.
https://github.com/Azure/azure-sdk-for-go/tree/v68.0.0/services/compute/mgmt
- clones
-
OCPBUGS-56168 [release-4.17] Azure Capacity Reservation Group does not work across subscriptions
-
- Closed
-
- is blocked by
-
OCPBUGS-56168 [release-4.17] Azure Capacity Reservation Group does not work across subscriptions
-
- Closed
-
- links to