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

ERROR: Could not find a runtime version for runtime {} with functions version {} and os {}Run #117

Closed
eliassal opened this issue Jan 26, 2024 · 13 comments

Comments

@eliassal
Copy link

Hi, I ran the
./sample-1-azure-setup.sh uniqname
(I changed the location to francecentral) It created some resources as fllows
image

but errored as follows

create: functionapp checkgccfunctionapp
WARNING: No functions version specified so defaulting to 3. In the future, specifying a version will be required. To create a 3.x function you would pass in the flag --functions-version 3
ERROR: Could not find a runtime version for runtime {} with functions version {} and os {}Run 'az functionapp list-runtimes' for more details on supported runtimes.

I added -functions-version 3 as follows

az functionapp create --name "${PREFIX}functionapp" --plan "${PREFIX}plan" --resource-group "${RG}" --storage-account "${PREFIX}storage" --functions-version 3 -o json >> azcli-execution.log

it errored again

create: functionapp checkgccfunctionapp
ERROR: Could not find a runtime version for runtime {} with functions version {} and os {}Run 'az functionapp list-runtimes' for more details on supported runtimes.

Thanks for your help

@eliassal
Copy link
Author

OK, after googling, I updated
--functions-version 3
by
--functions-version 4
all creations went through except for
eventgrid event-subscription function
I got

create: eventgrid event-subscription function
WARNING: If you are creating an event subscription from a topic that has “Azure” as the value for its “kind” property, you must validate your webhook endpoint by following the steps described in https://aka.ms/eg-webhook-endpoint-validation.
ERROR: (Url validation) Webhook validation handshake failed for https://checkgccfunctionapp.azurewebsites.net/api/ClaimCheck. Http POST request failed with response code Unknown. For troublehooting, visit https://aka.ms/esvalidation. Activity id:4738f3a6-e422-4009-9909-f773981d5266, timestamp: 1/26/2024 3:33:00 PM (UTC).
Code: Url validation
Message: Webhook validation handshake failed for https://checkgccfunctionapp.azurewebsites.net/api/ClaimCheck. Http POST request failed with response code Unknown. For troublehooting, visit https://aka.ms/esvalidation. Activity id:4738f3a6-e422-4009-9909-f773981d5266, timestamp: 1/26/2024 3:33:00 PM (UTC).

@eliassal
Copy link
Author

Hi, can somebody respond please?

@ckittel
Copy link
Member

ckittel commented Jan 30, 2024

I'm sorry you are running into this. Due to capacity constraints with prior planned work, please do not expect anyone from the team to be able to help you with troubleshooting. This example implementation is scheduled for a refresh in March. I know that's likely too late for your immediate needs, but because of this scheduled refresh, we likely will not be able to find time between now and then to support directly on this issue. If we could drop our current commitments to help, please know we would.

I'm assuming something about this sample is just out of date (technology moves fast), and the refresh scheduled for March is doing to be our next scheduled point to update it. February's pattern updates have already been scheduled and allocated resources.

@eliassal
Copy link
Author

Thanks, so in this case I hae no other option, only wait for march :-)

@ckittel
Copy link
Member

ckittel commented Jan 30, 2024

Yeah, I wish I had a better answer for you. If you do figure out something prior to that, we'd always appreciate the learnings (as might anyone else who gets to this prior to our refresh.)

@eliassal
Copy link
Author

eliassal commented Feb 9, 2024

Hi Chad, I am following the learning post at
https://github.com/mspnp/iaas-baseline?tab=readme-ov-file
where I saw your name as one of the contributors. It seems that we cant report any issue on this. I am getting an error when I try to run the

az deployment group create -g rg-iaas -f infra-as-code/bicep/main.bicep -p location............................................................

"message":"Operation could not be completed as it results in exceeding approved Total Regional Cores quota.
Additional details - Deployment Model: Resource Manager, Location: FranceCentral, Current Limit: 10,
Current Usage: 0, Additional Required: 18, (Minimum) New Limit Required: 18.

Whis is supporting this and who can help? Thanks in advance

@ckittel
Copy link
Member

ckittel commented Feb 12, 2024

Looks like you are out of Quota, @eliassal. The deployment requires 18 cores but you only have 10 available in FranceCentral in your subscription. You'll need to modify the template to use less cores or increase your quota in that subscription.

I'll see if I can find out why Issues are disabled on that repo. I enabled issues and replicated moved your issue there. Thanks for pointing that out.

@eliassal
Copy link
Author

Thanks, I modified the tempalet with VMs with 2 cores instead the VMs in the templates which have 4 cores but still getting the same error. I moved to use West Europe instead of FranceCentral, same thing is happeining

@ckittel
Copy link
Member

ckittel commented Feb 12, 2024

Please continue the conversation at the issue I opened on your behalf, and not in this thread. Thank you. Maybe a community member or Azure support can help you troubleshoot why you believe the error message is wrong for you.

@eliassal
Copy link
Author

Ok I will do, thanks again

@ckittel
Copy link
Member

ckittel commented Feb 25, 2024

There are no cloud design patterns that deploy Data Collection Rules or VM insights. Can you please verify you are posting this on an issue in the correct repo. Thanks.

@eliassal
Copy link
Author

eliassal commented Feb 25, 2024

Sorry, it was supposed to go for the thread at mspnp/iaas-baseline#30. I update it right now and deleted my post from this thread

@ckittel
Copy link
Member

ckittel commented Apr 26, 2024

All of the claim check samples are being updated @eliassal. You can see the PR at #129. Because they have all been rewritten (and will be merged to main soon), I'm going to close this issue.

@ckittel ckittel closed this as completed Apr 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants