Deployment script fail to deploy functions successfully due to Azure Function runtime version mismatch

[sesmyrnov]

Deployment script fail to deploy functions due to v1 vs v4 mismatch.

Deployment error
Your function app is targeting v4, but Azure host has function version ~1, \nplease change the version using the portal or update your 'FUNCTIONS_EXTENSION_VERSION' appsetting and retry

[markjbrown]

ack. Will look into this. Thanks.

[sesmyrnov]

Mark Brown (@markjbrown) - have you had a chance to look at this issue? just want to follow up on this..

[cjoakim]

I just experienced this same error that Sergiy reported, above. Function failed to deploy, properly. The Function seemed to exist, but the /api/ingestandvectorize endpoint produced a 404 error.

[markjbrown]

I'm going to try to repro. btw, did you get an error in the deployment itself? I got one for the Azure Function but it wasn't the same one. Just gave me "terminal state" failed error.

[yoichiozaki]

Mark Brown (@markjbrown) maybe the deployed function app lost some AppSettings like AzureWebJobsStorage FUNCTIONS_WORKER_RUNTIME etc

[yoichiozaki]

Mark Brown (@markjbrown) and is it ok to link the function app with this repo as a CI/CD external source?
I redeploy the function app (source is under Vectorize.csproj) by zip-deploy with VSCode and reset app settings by hands, then finally got 2 http functions

[markjbrown]

@zakimal I redeployed and got the functions to deploy successfully. This has been deploying successfully for about a year. Whatever is happening is transient, albeit quite frequently lately. Still not sure exactly why this is happening.

Someone on our team is working through this now to hopefully repro to uncover why this is happening then fix. We will update this issue when complete.

thanks.

[yoichiozaki]

Hi Mark Brown (@markjbrown) I redeploy from the link in README and got all resources successfully at this morning trial (around 2024-03-04 00:30 UTC) ... I am not sure why my deployment failed last time
It may not necessarily mean that there was a problem with this repo. Sorry for confusing

[mirmajeed1]

Has there been any fix for this issue, as it is still happening?

[markjbrown]

Wasn't clear there was an issue still as a user had indicated they had deployed successfully.

As it stands now this sample is getting a major update to it, including azd deployment. This should be ready very soon. I will update here when it is ready. The sample will be located in another repo.

Thanks.