You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 24, 2023. It is now read-only.
Is this an ISSUE or FEATURE REQUEST? (choose one):
Issue
What version of aks-engine?:
0.32+
Kubernetes version:
Default
What happened:
The master and workers fail with an error reported back:
In testing this is generated by the wrong distro being used as the default in Azure Government.
What you expected to happen:
Default distro for that environment to be Ubuntu and to successfully deploy
How to reproduce it (as minimally and precisely as possible):
Run aks-engine deploy against a minimal apimodel using --azure-env=AzureUSGovernmentCloud
(Example input apimodel.json)
{
"apiVersion": "vlabs",
"properties": {
"orchestratorProfile": {
"orchestratorType": "Kubernetes"
},
"masterProfile": {
"count": 1,
"dnsPrefix": "",
"vmSize": "Standard_D2_v2"
},
"agentPoolProfiles": [
{
"name": "agentpool1",
"count": 3,
"vmSize": "Standard_D2_v2",
"availabilityProfile": "AvailabilitySet"
}
],
"linuxProfile": {
"adminUsername": "azureuser",
"ssh": {
"publicKeys": [
{
"keyData": ""
}
]
}
},
"servicePrincipalProfile": {
"clientId": "",
"secret": ""
}
}
}
Anything else we need to know:
Ran deploy with arg --azure-env=AzureUSGovernmentCloud
It should default to the SovereignCloud distro: Ubuntu. Starting in version 0.32 it defaults to distro: aks which is not available in AzureUSGovernmentCloud
Workaround is to define distro manually as in #307
Is this a request for help?:
No
Is this an ISSUE or FEATURE REQUEST? (choose one):
Issue
What version of aks-engine?:
0.32+
Kubernetes version:
Default
What happened:
The master and workers fail with an error reported back:
In testing this is generated by the wrong distro being used as the default in Azure Government.
What you expected to happen:
Default distro for that environment to be Ubuntu and to successfully deploy
How to reproduce it (as minimally and precisely as possible):
Run aks-engine deploy against a minimal apimodel using --azure-env=AzureUSGovernmentCloud
(Example input apimodel.json)
{
"apiVersion": "vlabs",
"properties": {
"orchestratorProfile": {
"orchestratorType": "Kubernetes"
},
"masterProfile": {
"count": 1,
"dnsPrefix": "",
"vmSize": "Standard_D2_v2"
},
"agentPoolProfiles": [
{
"name": "agentpool1",
"count": 3,
"vmSize": "Standard_D2_v2",
"availabilityProfile": "AvailabilitySet"
}
],
"linuxProfile": {
"adminUsername": "azureuser",
"ssh": {
"publicKeys": [
{
"keyData": ""
}
]
}
},
"servicePrincipalProfile": {
"clientId": "",
"secret": ""
}
}
}
Anything else we need to know:
Ran deploy with arg --azure-env=AzureUSGovernmentCloud
It should default to the SovereignCloud distro: Ubuntu. Starting in version 0.32 it defaults to distro: aks which is not available in AzureUSGovernmentCloud
Workaround is to define distro manually as in #307
Would be alternatively resolved by #645
I'm looking into the code to see where the sovereign default distro conditionals are getting stomped or bypassed
Error message details:
Details=[{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message":
"VM has reported a failure when processing extension 'cse-agent-1'. Error message: \"Enable failed: failed to execute command: command terminated with
exit status=48\"."\r\n }\r\n ]\r\n }\r\n}"},{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'cse-agent-0'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=48\"."\r\n }\r\n ]\r\n }\r\n}"},{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'cse-master-0'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=48\"."\r\n }\r\n ]\r\n }\r\n}"},{"code":"Conflict","message":"{\r\n "status": "Failed",\r\n "error": {\r\n "code": "ResourceDeploymentFailure",\r\n "message": "The resource operation completed with terminal provisioning state 'Failed'.",\r\n "details": [\r\n {\r\n "code": "VMExtensionProvisioningError",\r\n "message": "VM has reported a failure when processing extension 'cse-agent-2'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=48\"."\r\n }\r\n ]\r\n }\r\n}"}]
The text was updated successfully, but these errors were encountered: