Azure / Azure/azure-quickstart-templates

It's impossible to use openshift-origin-rhel to create a cluster

Open
#3,285 10 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

openshift-origin-rhel https://github.com/Azure/azure-quickstart-templates/tree/master/openshift-origin-rhel

### Issue Details

I've tried to create a cluster using this template , but I always get an error on OpenshiftDeployment resource

STATUSMESSAGE{
"status": "Failed",
"error": {
"code": "ResourceDeploymentFailure",
"message": "The resource operation completed with terminal provisioning state 'Failed'.",
"details": [
{
"code": "DeploymentFailed",
"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage 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 'deployOpenShift'. Error message: \\\"Enable failed: failed to execute command: command terminated with exit status=2\\\".\"\r\n }\r\n ]\r\n }\r\n}"
}
]
}
]
}
}
RESOURCE
OpenShiftDeployment

### Repro steps
1. Create your keyvault etc
2. deploy the Arm template

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the openshift-origin-rhel template linked in the issue and inspect the OpenShiftDeployment resource and deployOpenShift VM extension failure. Review the deployment operation details and extension logs to identify the exit-status-2 cause. Done means the ARM template can create the cluster without the reported provisioning failure.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cloud, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 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.