Azure / Azure/azure-quickstart-templates

Cannot use docker-swarm-cluster template

Open
#2,315 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Bicep
Stars
14.9k
Forks
16.2k
Avg merge
6d 21h
Merged PRs (30d)
6

Description

```
info: Resource 'swarm-masters-firewall' of type 'Microsoft.Network/networkSecurityGroups' provisioning status is Succeeded
info: Resource 'swarm-nodes-firewall' of type 'Microsoft.Network/networkSecurityGroups' provisioning status is Succeeded
info: Resource 'log5uv4kclahg' of type 'Microsoft.Storage/storageAccounts' provisioning status is Succeeded
error: Deployment provisioning state was not successful
error: Cannot parse the request.
error: Cannot parse the request.
error: Cannot parse the request.
data: DeploymentName : phago-test-1
data: ResourceGroupName : phago-test-1
data: ProvisioningState : Failed
data: Timestamp : Wed Aug 03 2016 19:08:37 GMT+0530 (IST)
data: Mode : Incremental
data: CorrelationId : 54f6b9c4-7d14-4b78-922f-40f689c5b540
data: DeploymentParameters :
data: Name Type Value
data: ------------ ------------ ---------
data: sshPublicKey SecureString undefined
data: nodeCount Int 3
info: group deployment create command OK
```

There are no master nodes, but if I set masterNodeCount to be 1 instead of 3 it succeeds.

Repo steps:
- azure login
- azure group create -n "test-1" -l "West US"
- azure group deployment create -f azuredeploy.json -e azuredeploy.parameters.json -g test-1 -n "test-1"

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the docker-swarm-cluster deployment files, azuredeploy.json and azuredeploy.parameters.json, and reproduce the reported deployment using the listed Azure CLI commands. Compare deployments with the reported masterNodeCount values and inspect the failed resources and request-parsing errors. Done means the template deploys successfully with the intended master count and does not report missing master nodes.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, docker
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.