microsoft / microsoft/durabletask-mssql
Kubernetes Quickstart Error - Docker Desktop (Windows)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
While attempting the Kubernetes Quickstart, I've encountered the following error when deploying to a local k8s cluster using Docker Desktop for Windows. I had seen an SO thread about a possibly missing WEBSITE_HOSTNAME env var, but adding it as localhost:80 in msssql-secrets.yml did not resolve the issue.
PS C:\Users\conreaux\source\repos\durabletask-mssql\test\PerformanceTests> func kubernetes deploy --name $deploymentName --image-name "$repo/mssql-durable-functions:latest" --secret-name "mssql-secrets" --max-replicas 5
secret/func-keys-kube-secret-durabletask-mssql-app created
serviceaccount/durabletask-mssql-app-function-keys-identity-svc-act created
role.rbac.authorization.k8s.io/functions-keys-manager-role created
rolebinding.rbac.authorization.k8s.io/durabletask-mssql-app-function-keys-identity-svc-act-functions-keys-manager-rolebinding created
service/durabletask-mssql-app-http created
deployment.apps/durabletask-mssql-app-http created
deployment.apps/durabletask-mssql-app created
scaledobject.keda.sh/durabletask-mssql-app created
Waiting for deployment "durabletask-mssql-app-http" rollout to finish: 0 of 1 updated replicas are available...
deployment "durabletask-mssql-app-http" successfully rolled out
PurgeOrchestrationData - [httpTrigger]
Invalid URI: The hostname could not be parsed.
The durabletask-mssql-app-http-* pod starts, and I'm able to POST to the StartManySequences endpoint, but get subsequent errors. I assume not everything has instantiated correctly due to the prior error. Any suggestions?
2022-11-18 07:32:46 Hosting environment: Production
2022-11-18 07:32:46 Content root path: /azure-functions-host
2022-11-18 07:32:46 Now listening on: http://[::]:80
2022-11-18 07:32:46 Application started. Press Ctrl+C to shut down.
2022-11-18 07:35:37 warn: Function.StartManySequences.User[0]
2022-11-18 07:35:37 Scheduling 100 orchestration(s) with a prefix of '20221118-013537'...
2022-11-18 07:35:38 warn: Function.StartManySequences.User[0]
2022-11-18 07:35:38 All 100 orchestrations were scheduled successfully!
2022-11-18 07:35:38 fail: Function.HelloCities[3]
2022-11-18 07:35:38 Executed 'HelloCities' (Failed, Id=7b6b25c1-9abb-462b-a529-5badb17ef1b5, Duration=17ms)
2022-11-18 07:35:38 System.InvalidOperationException: Unable to load metadata for function 'HelloCities'.
2022-11-18 07:35:38 at Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.FunctionInstanceLogger.StartFunction(FunctionInstanceLogEntry item) in /src/azure-functions-host/src/WebJobs.Script.WebHost/Diagnostics/FunctionInstanceLogger.cs:line 75
2022-11-18 07:35:38 at Microsoft.Azure.WebJobs.Script.WebHost.Diagnostics.FunctionInstanceLogger.AddAsync(FunctionInstanceLogEntry item, CancellationToken cancellationToken) in /src/azure-functions-host/src/WebJobs.Script.WebHost/Diagnostics/FunctionInstanceLogger.cs:line 53
2022-11-18 07:35:38 at Microsoft.Azure.WebJobs.Host.Loggers.CompositeFunctionEventCollector.AddAsync(FunctionInstanceLogEntry item, CancellationToken cancellationToken) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Loggers\CompositeFunctionEventCollector.cs:line 23
2022-11-18 07:35:38 at Microsoft.Azure.WebJobs.Host.Executors.FunctionExecutor.TryExecuteAsync(IFunctionInstance functionInstance, CancellationToken cancellationToken) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Executors\FunctionExecutor.cs:line 106
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Kubernetes Quickstart deployment command from test/PerformanceTests and inspect msssql-secrets.yml alongside the reported pod logs. Reproduce the Docker Desktop for Windows deployment and trace the Invalid URI and metadata errors. Done means the quickstart deploys without those errors and the subsequent endpoint requests succeed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, docker, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100