Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deploying to GCC-H fails due to API version #825

Open
2 tasks done
sshockley opened this issue Aug 14, 2024 · 2 comments
Open
2 tasks done

Deploying to GCC-H fails due to API version #825

sshockley opened this issue Aug 14, 2024 · 2 comments
Labels
Area: Logging & Automation 📷 Issues / PR's related to Logging & Automation Status: In PR 👉 This is when an issue is due to be fixed in an open PR Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Bug 🪲 Something isn't working

Comments

@sshockley
Copy link

What happened? Provide a clear and concise description of the bug, including deployment details.

Setting up logging based on the instructions at https://github.com/Azure/ALZ-Bicep/tree/main/infra-as-code/bicep/modules/logging.

When I deploy, I get the error:

{
    "status": "Failed",
    "error": {
        "code": "DeploymentFailed",
        "target": "/subscriptions/.../resourceGroups/.../providers/Microsoft.Resources/deployments/alz-loggingDeployment-20240814T141606654142622Z",
        "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",
        "details": [{
                "code": "NoRegisteredProviderFound",
                "message": "No registered resource provider found for location 'usgovvirginia' and API version '2024-03-01' for type 'onboardingStates'. The supported api-versions are '2021-03-01-preview, 2021-09-01-preview, 2021-10-01-preview, 2022-01-01-preview, 2022-04-01-preview, 2022-05-01-preview, 2022-06-01-preview, 2022-07-01-preview, 2022-08-01-preview, 2022-09-01-preview, 2022-10-01-preview, 2022-11-01-preview, 2022-12-01-preview, 2023-02-01-preview, 2023-03-01-preview, 2023-04-01-preview, 2023-05-01-preview, 2023-06-01-preview, 2023-07-01-preview, 2023-08-01-preview, 2023-09-01-preview, 2023-10-01-preview, 2023-11-01-preview, 2023-12-01-preview, 2024-01-01-preview, 2024-04-01-preview'. The supported locations are 'usgovvirginia, usgovarizona'."
            }
        ]
    }
}

From my tenant, the supported API versions for Microsoft.SecurityInsights/onboardingStates are:

{
  "resourceType": "onboardingStates",
  "locations": [
    "USGov Virginia",
    "USGov Arizona"
  ],
  "apiVersions": [
    "2024-04-01-preview",
    "2024-01-01-preview",
    "2023-12-01-preview",
    "2023-11-01-preview",
    "2023-10-01-preview",
    "2023-09-01-preview",
    "2023-08-01-preview",
    "2023-07-01-preview",
    "2023-06-01-preview",
    "2023-05-01-preview",
    "2023-04-01-preview",
    "2023-03-01-preview",
    "2023-02-01-preview",
    "2022-12-01-preview",
    "2022-11-01-preview",
    "2022-10-01-preview",
    "2022-09-01-preview",
    "2022-08-01-preview",
    "2022-07-01-preview",
    "2022-06-01-preview",
    "2022-05-01-preview",
    "2022-04-01-preview",
    "2022-01-01-preview",
    "2021-10-01-preview",
    "2021-09-01-preview",
    "2021-03-01-preview"
  ],
  "capabilities": "SupportsExtension"
}

Odd that they're all preview. At any rate, if GCC-H is supported please use API versions allowed in that environment, or add logic so it picks the right one. Thanks.

Please provide the correlation id associated with your error or bug.

f36d1364-516f-4ccf-b879-4a8b343dca29

What was the expected outcome?

Deployment, or at least a different error.

Relevant log output

See above

Check previous GitHub issues

  • I have searched the issues for this item and found no duplicate

Code of Conduct

  • I agree to follow this project's Code of Conduct
@oZakari
Copy link
Contributor

oZakari commented Aug 19, 2024

Hi @sshockley, I can look to incorporating some logic to handle this. After changing the API version on your side, did you run into any other issues?

@oZakari oZakari added Type: Bug 🪲 Something isn't working Area: Logging & Automation 📷 Issues / PR's related to Logging & Automation labels Aug 19, 2024
@sshockley
Copy link
Author

I found a couple. I'll create a PR shortly.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: In PR 👉 This is when an issue is due to be fixed in an open PR label Aug 28, 2024
@oZakari oZakari added the Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Logging & Automation 📷 Issues / PR's related to Logging & Automation Status: In PR 👉 This is when an issue is due to be fixed in an open PR Status: Long Term ⌛ We will do it, but will take a longer amount of time due to complexity/priorities Type: Bug 🪲 Something isn't working
2 participants