Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-56169

[release-4.16] Azure Capacity Reservation Group does not work across subscriptions

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 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
    • Hide
      * Before this update, an outdated version of the {azure-short} API prevented specifying a Capacity Reservation Group for a `MachineSet`, if that group resided in a different subscription than the one originating the server creation. With this release, the most recent version of the {azure-short} API is used, which allows a Capacity Reservation Group for a `MachineSet` to be specified, even when that group is located in a separate subscription from the server creation point. (link:https://issues.redhat.com/browse/OCPBUGS-56169[OCPBUGS-56169])
      Show
      * Before this update, an outdated version of the {azure-short} API prevented specifying a Capacity Reservation Group for a `MachineSet`, if that group resided in a different subscription than the one originating the server creation. With this release, the most recent version of the {azure-short} API is used, which allows a Capacity Reservation Group for a `MachineSet` to be specified, even when that group is located in a separate subscription from the server creation point. (link: https://issues.redhat.com/browse/OCPBUGS-56169 [ OCPBUGS-56169 ])
    • 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

      https://github.com/openshift/machine-api-provider-azure/blob/main/pkg/cloud/azure/services/virtualmachines/virtualmachines.go#L29 

       

              rhn-gps-mbooth Matthew Booth
              openshift-crt-jira-prow OpenShift Prow Bot
              None
              None
              Zhaohua Sun Zhaohua Sun
              None
              Votes:
              1 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: