diff --git a/modules/rosa-troubleshooting-elb-service-role.adoc b/modules/rosa-troubleshooting-elb-service-role.adoc index 170932994a..7a23dca069 100644 --- a/modules/rosa-troubleshooting-elb-service-role.adoc +++ b/modules/rosa-troubleshooting-elb-service-role.adoc @@ -12,6 +12,8 @@ If you have not created a load balancer in your AWS account, it is possible that Error: Error creating network Load Balancer: AccessDenied: User: arn:aws:sts::xxxxxxxxxxxx:assumed-role/ManagedOpenShift-Installer-Role/xxxxxxxxxxxxxxxxxxx is not authorized to perform: iam:CreateServiceLinkedRole on resource: arn:aws:iam::xxxxxxxxxxxx:role/aws-service-role/elasticloadbalancing.amazonaws.com/AWSServiceRoleForElasticLoadBalancing" ---- +.Procedure + To resolve this issue, ensure that the role exists on your AWS account. If not, create this role with the following command: [source,terminal] diff --git a/modules/rosa-troubleshooting-general-deployment.adoc b/modules/rosa-troubleshooting-general-deployment.adoc index fb157b7d54..1ad66125ae 100644 --- a/modules/rosa-troubleshooting-general-deployment.adoc +++ b/modules/rosa-troubleshooting-general-deployment.adoc @@ -3,40 +3,14 @@ // * rosa_support/rosa-troubleshooting-deployments.adoc :_content-type: PROCEDURE [id="rosa-troubleshooting-general-deployment-failure_{context}"] -== General deployment failure += Obtaining information on a failed cluster If a cluster deployment fails, the cluster is put into an "error" state. +.Procedure Run the following command to get more information: [source,terminal] ---- $ rosa describe cluster -c --debug ---- - -[id="rosa-troubleshooting-deployment-failure-osdccsadmin_{context}"] -== Deployment failure with an `osdCcsAdmin` error - -If a cluster creation action fails, you can receive the following error message. - -.Example output -[source,terminal] ----- -Failed to create cluster: Unable to create cluster spec: Failed to get access keys for user 'osdCcsAdmin': NoSuchEntity: The user with name osdCcsAdmin cannot be found. ----- - -To fix this issue: - -. Delete the stack: -+ -[source,terminal] ----- -$ rosa init --delete-stack ----- - -. Reinitialize your account: -+ -[source,terminal] ----- -$ rosa init ----- diff --git a/modules/rosa-troubleshooting-deployment.adoc b/modules/rosa-troubleshooting-osdccsadmin-deployment.adoc similarity index 65% rename from modules/rosa-troubleshooting-deployment.adoc rename to modules/rosa-troubleshooting-osdccsadmin-deployment.adoc index 5a923c21d3..a95f9d2952 100644 --- a/modules/rosa-troubleshooting-deployment.adoc +++ b/modules/rosa-troubleshooting-osdccsadmin-deployment.adoc @@ -2,20 +2,8 @@ // // * rosa_support/rosa-troubleshooting-deployments.adoc :_content-type: PROCEDURE -[id="rosa-troubleshooting-general-deployment-failure_{context}"] -= General deployment failure - -If a cluster deployment fails, the cluster is put into an "error" state. - -Run the following command to get more information: - -[source,terminal] ----- -$ rosa describe cluster -c --debug ----- - [id="rosa-troubleshooting-deployment-failure-osdccsadmin_{context}"] -== Deployment failure with an `osdCcsAdmin` error += Failing to create a cluster with an `osdCcsAdmin` error If a cluster creation action fails, you can receive the following error message. @@ -25,6 +13,7 @@ If a cluster creation action fails, you can receive the following error message. Failed to create cluster: Unable to create cluster spec: Failed to get access keys for user 'osdCcsAdmin': NoSuchEntity: The user with name osdCcsAdmin cannot be found. ---- +.Procedure To fix this issue: . Delete the stack: diff --git a/rosa_planning/rosa-sts-aws-prereqs.adoc b/rosa_planning/rosa-sts-aws-prereqs.adoc index bb8a8208ce..38f6770ea9 100644 --- a/rosa_planning/rosa-sts-aws-prereqs.adoc +++ b/rosa_planning/rosa-sts-aws-prereqs.adoc @@ -21,6 +21,13 @@ When you create a ROSA cluster using AWS STS, an associated AWS OpenID Connect ( ==== include::modules/rosa-sts-aws-requirements.adoc[leveloffset=+1] +[role="_additional-resources"] +[id="additional-resources_aws-requirements_{context}"] +.Additional resources +* xref:../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[AWS limits] +* xref:../rosa_support/rosa-troubleshooting-deployments.adoc#rosa-troubleshooting-general-deployment-elb[Creating the service role for the Elastic load balancer (ELB)] +* xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#osd-aws-privatelink-firewall-prerequisites_rosa-sts-aws-prereqs[AWS firewall prerequisites] + include::modules/rosa-requirements-deploying-in-opt-in-regions.adoc[leveloffset=+1] include::modules/rosa-setting-the-aws-security-token-version.adoc[leveloffset=+2] include::modules/rosa-sts-aws-iam.adoc[leveloffset=+1] @@ -31,9 +38,7 @@ include::modules/osd-aws-privatelink-firewall-prerequisites.adoc[leveloffset=+1] * xref:../rosa_planning/rosa-sts-required-aws-service-quotas.adoc#rosa-sts-required-aws-service-quotas[Review the required AWS service quotas] [role="_additional-resources"] +[id="additional-resources_aws-prerequisites_{context}"] == Additional resources -* xref:../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[Limits and scalability] * xref:../rosa_architecture/rosa_policy_service_definition/rosa-policy-process-security.adoc#rosa-policy-sre-access_rosa-policy-process-security[SRE access to all Red Hat OpenShift Service on AWS clusters] * xref:../applications/deployments/osd-config-custom-domains-applications.adoc#osd-applications-config-custom-domains[Configuring custom domains for applications] -* xref:../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[AWS limits] -* xref:../rosa_support/rosa-troubleshooting-deployments.adoc#rosa-troubleshooting-general-deployment-elb[Creating the service role for the Elastic load balancer (ELB)] diff --git a/rosa_support/rosa-troubleshooting-deployments.adoc b/rosa_support/rosa-troubleshooting-deployments.adoc index ca3ab81c93..c1ba769108 100644 --- a/rosa_support/rosa-troubleshooting-deployments.adoc +++ b/rosa_support/rosa-troubleshooting-deployments.adoc @@ -3,11 +3,11 @@ include::_attributes/attributes-openshift-dedicated.adoc[] [id="rosa-troubleshooting-cluster-deployments"] = Troubleshooting cluster deployments :context: rosa-troubleshooting-cluster-deployments + toc::[] -[id="rosa-troubleshooting-deployment_{context}"] -= Troubleshooting cluster deployments This document describes how to troubleshoot cluster deployment errors. include::modules/rosa-troubleshooting-general-deployment.adoc[leveloffset=+1] +include::modules/rosa-troubleshooting-osdccsadmin-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-elb-service-role.adoc[leveloffset=+1]