diff --git a/_topic_maps/_topic_map_rosa.yml b/_topic_maps/_topic_map_rosa.yml index ca594e8940..8b2ce4076c 100644 --- a/_topic_maps/_topic_map_rosa.yml +++ b/_topic_maps/_topic_map_rosa.yml @@ -392,10 +392,10 @@ Topics: # File: troubleshooting-installations - Name: Review your cluster notifications File: mos-tshoot-cluster-notifications - - Name: Troubleshooting ROSA installations + - Name: Troubleshooting Red Hat OpenShift Service on AWS classic architecture installations File: rosa-troubleshooting-installations - - Name: Troubleshooting ROSA with HCP installations - File: rosa-troubleshooting-installations-hcp +# - Name: Troubleshooting Red Hat OpenShift Service on AWS installations +# File: rosa-troubleshooting-installations-hcp - Name: Troubleshooting networking File: rosa-troubleshooting-networking - Name: Verifying node health diff --git a/_topic_maps/_topic_map_rosa_hcp.yml b/_topic_maps/_topic_map_rosa_hcp.yml index d15560ea12..a9f7d70c23 100644 --- a/_topic_maps/_topic_map_rosa_hcp.yml +++ b/_topic_maps/_topic_map_rosa_hcp.yml @@ -402,9 +402,9 @@ Topics: # File: troubleshooting-installations - Name: Review your cluster notifications File: mos-tshoot-cluster-notifications - - Name: Troubleshooting ROSA installations - File: rosa-troubleshooting-installations - - Name: Troubleshooting ROSA with HCP installations +# - Name: Troubleshooting ROSA installations +# File: rosa-troubleshooting-installations + - Name: Troubleshooting Red Hat OpenShift Service on AWS installations File: rosa-troubleshooting-installations-hcp - Name: Troubleshooting networking File: rosa-troubleshooting-networking diff --git a/modules/rosa-hcp-no-console-access.adoc b/modules/rosa-hcp-no-console-access.adoc index 56fd169d8c..656fe1d969 100644 --- a/modules/rosa-hcp-no-console-access.adoc +++ b/modules/rosa-hcp-no-console-access.adoc @@ -5,7 +5,7 @@ [id="rosa-hcp-no-console-access_{context}"] = Troubleshooting access to {hybrid-console} -In {hcp-title} clusters, the {product-title} OAuth server is hosted in the Red Hat service's AWS account while the web console service is published using the cluster's default ingress controller in the cluster's AWS account. If you can log in to your cluster using the OpenShift CLI (oc) but cannot access the {product-title} web console, verify the following criteria are met: +In {product-title} clusters, the {product-title} OAuth server is hosted in the Red Hat service's AWS account while the web console service is published using the cluster's default ingress controller in the cluster's AWS account. If you can log in to your cluster using the OpenShift CLI (oc) but cannot access the {product-title} web console, verify the following criteria are met: * The console workloads are running. * The default ingress controller's load balancer is active. diff --git a/modules/rosa-hcp-private-ready-no-console-access.adoc b/modules/rosa-hcp-private-ready-no-console-access.adoc index ea68871978..67b9afd306 100644 --- a/modules/rosa-hcp-private-ready-no-console-access.adoc +++ b/modules/rosa-hcp-private-ready-no-console-access.adoc @@ -3,10 +3,10 @@ // * support/rosa-troubleshooting-installations-hcp .adoc :_mod-docs-content-type: PROCEDURE [id="rosa-hcp-private-ready-no-console-access_{context}"] -= Verifying access to {hybrid-console} for private {hcp-title} clusters += Verifying access to {hybrid-console} for private {product-title} clusters The console of the private cluster is private by default. During cluster installation, the default Ingress Controller managed by OpenShift's Ingress Operator is configured with an internal AWS Network Load Balancer (NLB). -If your private {hcp-title} cluster shows a `ready` status but you cannot access the {product-title} web console for the cluster, try accessing the cluster console from either within the cluster VPC or from a network that is connected to the VPC. +If your private {product-title} cluster shows a `ready` status but you cannot access the {product-title} web console for the cluster, try accessing the cluster console from either within the cluster VPC or from a network that is connected to the VPC. diff --git a/modules/rosa-hcp-ready-no-console-access.adoc b/modules/rosa-hcp-ready-no-console-access.adoc index c7a3b2dfff..356af27243 100644 --- a/modules/rosa-hcp-ready-no-console-access.adoc +++ b/modules/rosa-hcp-ready-no-console-access.adoc @@ -3,10 +3,10 @@ // * support/rosa-troubleshooting-installations-hcp .adoc :_mod-docs-content-type: PROCEDURE [id="rosa-hcp-ready-no-console-access_{context}"] -= Verifying access to {product-title} web console for {hcp-title} cluster in ready state += Verifying access to {product-title} web console for {product-title} cluster in ready state -{hcp-title} clusters return a `ready` status when the control plane hosted in the {product-title} service account becomes ready. Cluster console workloads are deployed on the cluster's worker nodes. The {product-title} web console will not be available and accessible until the worker nodes have joined the cluster and console workloads are running. +{product-title} clusters return a `ready` status when the control plane hosted in the {product-title} service account becomes ready. Cluster console workloads are deployed on the cluster's worker nodes. The {product-title} web console will not be available and accessible until the worker nodes have joined the cluster and console workloads are running. -If your {hcp-title} cluster is ready but you are unable to access the {product-title} web console for the cluster, wait for the worker nodes to join the cluster and retry accessing the console. +If your {product-title} cluster is ready but you are unable to access the {product-title} web console for the cluster, wait for the worker nodes to join the cluster and retry accessing the console. -You can either log in to the {hcp-title} cluster or use the `rosa describe machinepool` command in the `rosa` CLI watch the nodes. +You can either log in to the {product-title} cluster or use the `rosa describe machinepool` command in the `rosa` CLI watch the nodes. diff --git a/modules/rosa-troubleshoot-hcp-install.adoc b/modules/rosa-troubleshoot-hcp-install.adoc index 980f9718ba..d65fb41b65 100644 --- a/modules/rosa-troubleshoot-hcp-install.adoc +++ b/modules/rosa-troubleshoot-hcp-install.adoc @@ -4,11 +4,11 @@ :_mod-docs-content-type: CONCEPT [id="rosa-troubleshoot-hcp-install_{context}"] -= Troubleshooting {hcp-title} installation error codes += Troubleshooting {product-title} installation error codes -The following table lists {hcp-title-first} installation error codes and what you can do to troubleshoot these errors. +The following table lists {product-title} installation error codes and what you can do to troubleshoot these errors. -.{hcp-title} installation error codes +.{product-title} installation error codes [options="header",cols="3"] |=== | Error code | Description | Resolution @@ -18,7 +18,7 @@ The following table lists {hcp-title-first} installation error codes and what yo | Check the cluster installation logs for more details, or delete this cluster and retry cluster installation. If this issue persists, contact support by logging in to the link:https://access.redhat.com/support/cases/#/case/list[*Customer Support* page]. | OCM5001 -| {hcp-title} cluster provision has failed. +| {product-title} cluster provision has failed. | Check the cluster installation logs for more details, or delete this cluster and retry cluster installation. If this issue persists, contact support by logging in to the link:https://access.redhat.com/support/cases/#/case/list[*Customer Support* page]. | OCM5002 @@ -27,15 +27,15 @@ The following table lists {hcp-title-first} installation error codes and what yo | OCM5003 | Unable to establish an AWS client to provision the cluster. -| You must create several role resources on your AWS account to create and manage a {hcp-title} cluster. Ensure that your provided AWS credentials are correct and retry cluster installation. +| You must create several role resources on your AWS account to create and manage a {product-title} cluster. Ensure that your provided AWS credentials are correct and retry cluster installation. -For more information about {hcp-title} IAM role resources, see _ROSA IAM role resources_ in the _Additional resources_ section. +For more information about {product-title} IAM role resources, see _ROSA IAM role resources_ in the _Additional resources_ section. | OCM5004 | Unable to establish a cross-account AWS client to provision the cluster. -| You must create several role resources on your AWS account to create and manage a {hcp-title} cluster. Ensure that your provided AWS credentials are correct and retry cluster installation. +| You must create several role resources on your AWS account to create and manage a {product-title} cluster. Ensure that your provided AWS credentials are correct and retry cluster installation. -For more information about {hcp-title} IAM role resources, see _ROSA IAM role resources_ in the _Additional resources_ section. +For more information about {product-title} IAM role resources, see _ROSA IAM role resources_ in the _Additional resources_ section. | OCM5005 | Failed to retrieve AWS subnets defined for the cluster. @@ -55,7 +55,7 @@ For more information about {hcp-title} IAM role resources, see _ROSA IAM role re | OCM5009 | The cluster version could not be found. -| Ensure that the configured version ID matches a valid {hcp-title} version. +| Ensure that the configured version ID matches a valid {product-title} version. | OCM5010 | Failed to tag subnets for the cluster. diff --git a/modules/rosa-verify-hcp-install.adoc b/modules/rosa-verify-hcp-install.adoc index 6d0e83ce93..ea840db7ec 100644 --- a/modules/rosa-verify-hcp-install.adoc +++ b/modules/rosa-verify-hcp-install.adoc @@ -3,6 +3,6 @@ // * support/rosa-troubleshooting-installations-hcp .adoc :_mod-docs-content-type: PROCEDURE [id="rosa-verify-hcp-install_{context}"] -= Verifying installation of {hcp-title} clusters += Verifying installation of {product-title} clusters If the {hcp-title} cluster is in the installing state for over 30 minutes and has not become ready, ensure the AWS account environment is prepared for the required cluster configurations. If the AWS account environment is prepared for the required cluster configurations correctly, try to delete and recreate the cluster. If the problem persists, contact support. \ No newline at end of file diff --git a/modules/support-collecting-host-network-trace.adoc b/modules/support-collecting-host-network-trace.adoc index fceaa747f7..e0456d604c 100644 --- a/modules/support-collecting-host-network-trace.adoc +++ b/modules/support-collecting-host-network-trace.adoc @@ -74,23 +74,23 @@ ifdef::openshift-origin[] [source,terminal] ---- $ oc adm must-gather \ - --dest-dir /tmp/captures \ <.> - --source-dir '/tmp/tcpdump/' \ <.> - --image quay.io/openshift/origin-network-tools:latest \ <.> - --node-selector 'node-role.kubernetes.io/worker' \ <.> - --host-network=true \ <.> - --timeout 30s \ <.> + --dest-dir /tmp/captures \ <1> + --source-dir '/tmp/tcpdump/' \ <2> + --image quay.io/openshift/origin-network-tools:latest \ <3> + --node-selector 'node-role.kubernetes.io/worker' \ <4> + --host-network=true \ <5> + --timeout 30s \ <6> -- \ - tcpdump -i any \ <.> + tcpdump -i any \ <7> -w /tmp/tcpdump/%Y-%m-%dT%H:%M:%S.pcap -W 1 -G 300 ---- -<.> The `--dest-dir` argument specifies that `oc adm must-gather` stores the packet captures in directories that are relative to `/tmp/captures` on the client machine. You can specify any writable directory. -<.> When `tcpdump` is run in the debug pod that `oc adm must-gather` starts, the `--source-dir` argument specifies that the packet captures are temporarily stored in the `/tmp/tcpdump` directory on the pod. -<.> The `--image` argument specifies a container image that includes the `tcpdump` command. -<.> The `--node-selector` argument and example value specifies to perform the packet captures on the worker nodes. As an alternative, you can specify the `--node-name` argument instead to run the packet capture on a single node. If you omit both the `--node-selector` and the `--node-name` argument, the packet captures are performed on all nodes. -<.> The `--host-network=true` argument is required so that the packet captures are performed on the network interfaces of the node. -<.> The `--timeout` argument and value specify to run the debug pod for 30 seconds. If you do not specify the `--timeout` argument and a duration, the debug pod runs for 10 minutes. -<.> The `-i any` argument for the `tcpdump` command specifies to capture packets on all network interfaces. As an alternative, you can specify a network interface name. +<1> The `--dest-dir` argument specifies that `oc adm must-gather` stores the packet captures in directories that are relative to `/tmp/captures` on the client machine. You can specify any writable directory. +<2> When `tcpdump` is run in the debug pod that `oc adm must-gather` starts, the `--source-dir` argument specifies that the packet captures are temporarily stored in the `/tmp/tcpdump` directory on the pod. +<3> The `--image` argument specifies a container image that includes the `tcpdump` command. +<4> The `--node-selector` argument and example value specifies to perform the packet captures on the worker nodes. As an alternative, you can specify the `--node-name` argument instead to run the packet capture on a single node. If you omit both the `--node-selector` and the `--node-name` argument, the packet captures are performed on all nodes. +<5> The `--host-network=true` argument is required so that the packet captures are performed on the network interfaces of the node. +<6> The `--timeout` argument and value specify to run the debug pod for 30 seconds. If you do not specify the `--timeout` argument and a duration, the debug pod runs for 10 minutes. +<7> The `-i any` argument for the `tcpdump` command specifies to capture packets on all network interfaces. As an alternative, you can specify a network interface name. endif::openshift-origin[] . Perform the action, such as accessing a web application, that triggers the network communication issue while the network trace captures packets. diff --git a/rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc b/rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc index 8bc45c3cf2..5e6520ed5e 100644 --- a/rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc +++ b/rosa_hcp/rosa-hcp-aws-private-creating-cluster.adoc @@ -16,21 +16,22 @@ include::modules/rosa-additional-principals-overview.adoc[leveloffset=+1] include::modules/rosa-additional-principals-create.adoc[leveloffset=+2] include::modules/rosa-additional-principals-edit.adoc[leveloffset=+2] -//unclear on why this is here given this is a HCP assembly -ifndef::openshift-rosa-hcp[] +ifdef::openshift-rosa[] [id="next-steps_rosa-hcp-aws-private-creating-cluster"] == Next steps xref:../rosa_install_access_delete_clusters/rosa-sts-config-identity-providers.adoc#rosa-sts-config-identity-providers[Configuring identity providers] +endif::openshift-rosa[] [role="_additional-resources"] [id="additional-resources_rosa-hcp-aws-privatelink-creating-cluster"] == Additional resources * xref:../rosa_planning/rosa-hcp-aws-prereqs.adoc#rosa-hcp-firewall-prerequisites_rosa-hcp-aws-prereqs[AWS PrivateLink firewall prerequisites] -// This link must remain hidden until the HCP migration is completed +// Commenting out until pruning of other books is complete as these are breaking the build for Pruning Support task // * xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-hcp-firewall-prerequisites_rosa-sts-aws-prereqs[AWS PrivateLink firewall prerequisites] -* xref:../rosa_getting_started/rosa-sts-getting-started-workflow.adoc#rosa-sts-overview-of-the-deployment-workflow[Overview of the ROSA with STS deployment workflow] -* xref:../rosa_install_access_delete_clusters/rosa-sts-deleting-cluster.adoc#rosa-sts-deleting-cluster[Deleting a ROSA cluster] -* xref:../architecture/rosa-architecture-models.adoc#rosa-architecture-models[ROSA architecture models] +//* xref:../rosa_getting_started/rosa-sts-getting-started-workflow.adoc#rosa-sts-overview-of-the-deployment-workflow[Overview of the ROSA with STS deployment workflow] +//* xref:../rosa_install_access_delete_clusters/rosa-sts-deleting-cluster.adoc#rosa-sts-deleting-cluster[Deleting a ROSA cluster] +//* xref:../architecture/rosa-architecture-models.adoc#rosa-architecture-models[ROSA architecture models] +ifdef::openshift-rosa-hcp[] * xref:../support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc#rosa-troubleshooting-installations-hcp[Troubleshooting ROSA with HCP cluster installations] endif::openshift-rosa-hcp[] \ No newline at end of file diff --git a/rosa_hcp/rosa-hcp-creating-cluster-with-aws-kms-key.adoc b/rosa_hcp/rosa-hcp-creating-cluster-with-aws-kms-key.adoc index 71348d4984..ba463f0920 100644 --- a/rosa_hcp/rosa-hcp-creating-cluster-with-aws-kms-key.adoc +++ b/rosa_hcp/rosa-hcp-creating-cluster-with-aws-kms-key.adoc @@ -100,6 +100,8 @@ ifndef::openshift-rosa-hcp[] // * xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-sts-aws-prereqs[AWS prerequisites for ROSA with STS]] * xref:../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-with-customizations.adoc#rosa-understanding-deployment-modes_rosa-sts-creating-a-cluster-with-customizations[Understanding the auto and manual deployment modes] * link:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html[Creating OpenID Connect (OIDC) identity providers] -* xref:../support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc#rosa-troubleshooting-installations-hcp[Troubleshooting ROSA with HCP cluster installations] -* xref:../support/getting-support.adoc#getting-support[Getting support for Red{nbsp}Hat OpenShift Service on AWS] +endif::openshift-rosa-hcp[] +* xref:../support/getting-support.adoc#getting-support[Getting support for Red{nbsp}Hat OpenShift Service on AWS] +ifdef::openshift-rosa-hcp[] +* xref:../support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc#rosa-troubleshooting-installations-hcp[Troubleshooting ROSA with HCP cluster installations] endif::openshift-rosa-hcp[] diff --git a/rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc b/rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc index c1b61a3801..be2651449f 100644 --- a/rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc +++ b/rosa_hcp/rosa-hcp-sts-creating-a-cluster-ext-auth.adoc @@ -89,5 +89,7 @@ include::modules/rosa-hcp-sts-creating-a-cluster-external-auth-provider-delete-c // * xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-sts-aws-prereqs[AWS prerequisites for ROSA with STS]] //* xref:../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-with-customizations.adoc#rosa-understanding-deployment-modes_rosa-sts-creating-a-cluster-with-customizations[Understanding the auto and manual deployment modes] * link:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html[Creating OpenID Connect (OIDC) identity providers] in the AWS documentation. +ifdef::openshift-rosa-hcp[] * xref:../support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc#rosa-troubleshooting-installations-hcp[Troubleshooting ROSA with HCP cluster installations] +endif::openshift-rosa-hcp[] * xref:../support/getting-support.adoc#getting-support[Getting support for Red{nbsp}Hat OpenShift Service on AWS] \ No newline at end of file diff --git a/rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc b/rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc index 953d4e3ddb..2facd2dd6d 100644 --- a/rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc +++ b/rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc @@ -155,6 +155,7 @@ ifndef::openshift-rosa-hcp[] // * xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-sts-aws-prereqs[AWS prerequisites for ROSA with STS] * xref:../rosa_install_access_delete_clusters/rosa-sts-creating-a-cluster-with-customizations.adoc#rosa-understanding-deployment-modes_rosa-sts-creating-a-cluster-with-customizations[Understanding the auto and manual deployment modes] * link:https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_create_oidc.html[Creating OpenID Connect (OIDC) identity providers] -* xref:../support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc#rosa-troubleshooting-installations-hcp[Troubleshooting ROSA with HCP installations] +ifdef::openshift-rosa-hcp[] +* xref:../support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc#rosa-troubleshooting-installations-hcp[Troubleshooting {product-title} installations] +endif::openshift-rosa-hcp[] * xref:../support/getting-support.adoc#getting-support[Getting support for Red{nbsp}Hat OpenShift Service on AWS] -endif::openshift-rosa-hcp[] \ No newline at end of file diff --git a/rosa_install_access_delete_clusters/rosa-aws-privatelink-creating-cluster.adoc b/rosa_install_access_delete_clusters/rosa-aws-privatelink-creating-cluster.adoc index a86fb8e0ef..cf541cefa1 100644 --- a/rosa_install_access_delete_clusters/rosa-aws-privatelink-creating-cluster.adoc +++ b/rosa_install_access_delete_clusters/rosa-aws-privatelink-creating-cluster.adoc @@ -36,6 +36,8 @@ endif::openshift-rosa[] ifdef::openshift-dedicated[] * xref:../rosa_planning/rosa-sts-aws-prereqs.adoc#osd-aws-privatelink-firewall-prerequisites_rosa-sts-aws-prereqs[Firewall prerequisites] endif::openshift-dedicated[] +ifdef::openshift-rosa[] * xref:../rosa_getting_started/rosa-sts-getting-started-workflow.adoc#rosa-sts-overview-of-the-deployment-workflow[Overview of the ROSA with STS deployment workflow] * xref:../rosa_install_access_delete_clusters/rosa-sts-deleting-cluster.adoc#rosa-sts-deleting-cluster[Deleting a ROSA cluster] * xref:../architecture/rosa-architecture-models.adoc#rosa-architecture-models[ROSA architecture models] +endif::openshift-rosa[] diff --git a/rosa_planning/rosa-sts-aws-prereqs.adoc b/rosa_planning/rosa-sts-aws-prereqs.adoc index 2df6bcf5c6..7ad7358a68 100644 --- a/rosa_planning/rosa-sts-aws-prereqs.adoc +++ b/rosa_planning/rosa-sts-aws-prereqs.adoc @@ -1,11 +1,11 @@ :_mod-docs-content-type: ASSEMBLY include::_attributes/attributes-openshift-dedicated.adoc[] //title and ID conditions so this can be shared between Classic and HCP docs while it remains accurate for both -ifndef::openshift-rosa-hcp[] +ifdef::openshift-rosa[] :context: rosa-classic-aws-prereqs [id="rosa-sts-classic-aws-prereqs"] = Detailed requirements for deploying {product-title} using STS -endif::openshift-rosa-hcp[] +endif::openshift-rosa[] ifdef::openshift-rosa-hcp[] :context: rosa-hcp-aws-prereqs [id="rosa-sts-hcp-aws-prereqs"] diff --git a/snippets/vpc-troubleshooting.adoc b/snippets/vpc-troubleshooting.adoc index 5be8cd286d..9e5b458a97 100644 --- a/snippets/vpc-troubleshooting.adoc +++ b/snippets/vpc-troubleshooting.adoc @@ -15,7 +15,8 @@ If your cluster fails to install, troubleshoot these common issues: * Make sure your link:https://docs.aws.amazon.com/vpc/latest/userguide/VPC_DHCP_Options.html[DHCP option set] includes a domain name, and ensure that the domain name does not include any spaces or capital letters. * If your VPC uses a custom DNS resolver (the `domain name servers` field of your DHCP option set is not `AmazonProvideDNS`), make sure it is able to properly resolve the private hosted zones configured in Route53. -For more information about troubleshooting ROSA cluster installations, see xref:../support/troubleshooting/rosa-troubleshooting-installations.adoc#rosa-troubleshooting-installations[Troubleshooting {product-title} installations]. +//commented out until pruning is complete for the other books as this is breaking the build for the Pruning Support task +//For more information about troubleshooting {product-title} cluster installations, see xref:../../support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc#rosa-troubleshooting-installations-hcp[Troubleshooting {product-title} cluster installations]. [discrete] [id="troubleshooting_vpc-support_{context}"] diff --git a/support/troubleshooting/rosa-troubleshooting-deployments.adoc b/support/troubleshooting/rosa-troubleshooting-deployments.adoc index 44151cea97..bc7bcb9885 100644 --- a/support/troubleshooting/rosa-troubleshooting-deployments.adoc +++ b/support/troubleshooting/rosa-troubleshooting-deployments.adoc @@ -1,7 +1,7 @@ :_mod-docs-content-type: ASSEMBLY include::_attributes/attributes-openshift-dedicated.adoc[] [id="rosa-troubleshooting-cluster-deployments"] -= Troubleshooting cluster deployments += Troubleshooting {product-title} cluster deployments :context: rosa-troubleshooting-cluster-deployments toc::[] @@ -10,6 +10,8 @@ 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] + +ifdef::openshift-rosa[] include::modules/rosa-troubleshooting-awsnatgatewaylimitexceeded-failure-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-awsapiratelimitexceeded-failure-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-s3bucketslimitexceeded-failure-deployment.adoc[leveloffset=+1] @@ -18,38 +20,30 @@ include::modules/rosa-troubleshooting-awsinsufficientcapacity-failure-deployment include::modules/rosa-troubleshooting-toomanyroute53zones-failure-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-awssubnetnotexist-failure-deployment.adoc[leveloffset=+1] -// Remove conditional once HCP split happens. Conditional was added due to build break. -ifndef::openshift-rosa-hcp[] [role="_additional-resources"] .Additional resources -* xref:../../rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc#rosa-vpc_prerequisites[AWS prerequisites for ROSA] -endif::openshift-rosa-hcp[] +* xref:../../rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc#rosa-vpc_prerequisites[AWS prerequisites for {product-title}] include::modules/rosa-troubleshooting-invalidkmskey-failure-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-multipleroute53zonesfound-failure-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-invalidinstallconfigsubnet-failure-deployment.adoc[leveloffset=+1] -// Remove conditional once HCP split happens. Conditional was added due to build break. -ifndef::openshift-rosa-hcp[] [role="_additional-resources"] .Additional resources * xref:../../networking/networking_overview/cidr-range-definitions.adoc#cidr-range-definitions[CIDR range definitions] -endif::openshift-rosa-hcp[] + include::modules/rosa-troubleshooting-awsinsufficientpermission-failure-deployment.adoc[leveloffset=+1] -// Remove conditional once HCP split happens. Conditional was added due to build break. -ifndef::openshift-rosa-hcp[] + [role="_additional-resources"] .Additional resources -* xref:../../rosa_planning/rosa-classic-aws-prereqs.adoc#rosa-classic-aws-prereqs[Detailed requirements for deploying ROSA (classic architecture) using STS] -// This link needs to remain hidden until the HCP migration is completed -// * xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-sts-aws-prereqs[Detailed requirements for deploying ROSA (classic architecture) using STS] -* xref:../../rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc#rosa-aws-prereqs[AWS prerequisites for ROSA] -endif::openshift-rosa-hcp[] +* xref:../../rosa_planning/rosa-classic-aws-prereqs.adoc#rosa-classic-aws-prereqs +* xref:../../rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-aws-prereqs.adoc#rosa-aws-prereqs[AWS prerequisites for {product-title}] include::modules/rosa-troubleshooting-deleteiamrole-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-awsec2quotaexceeded-failure-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-pendingverification-failure-deployment.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-lblimitexceeded-failure-deployment.adoc[leveloffset=+1] +endif::openshift-rosa[] include::modules/rosa-troubleshooting-elb-service-role.adoc[leveloffset=+1] include::modules/rosa-troubleshooting-cluster-deletion.adoc[leveloffset=+1] diff --git a/support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc b/support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc index 5feda8f69b..91a263e69b 100644 --- a/support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc +++ b/support/troubleshooting/rosa-troubleshooting-installations-hcp.adoc @@ -1,52 +1,42 @@ :_mod-docs-content-type: ASSEMBLY include::_attributes/attributes-openshift-dedicated.adoc[] [id="rosa-troubleshooting-installations-hcp"] -= Troubleshooting {hcp-title} cluster installations += Troubleshooting {product-title} cluster installations :context: rosa-troubleshooting-installations-hcp -//Remove this adoc from rosa-classic docs and add xrefs back in once HCP migration occurs. toc::[] -For help with the installation of {hcp-title-first} clusters, refer to the following sections. +For help with the installation of {product-title} clusters, see the following sections. + +include::modules/rosa-troubleshooting-installing.adoc[leveloffset=+1] include::modules/rosa-verify-hcp-install.adoc[leveloffset=+1] -//remove these conditionals once HCP migration happens -ifndef::openshift-rosa-hcp[] [role="_additional-resources"] .Additional resources -* For information about the prerequisites for installing {hcp-title} clusters, see xref:../../rosa_planning/rosa-hcp-aws-prereqs.adoc#rosa-hcp-aws-prereqs[AWS prerequisites for ROSA with STS]. -// This link must remain hidden until the HCP migration is completed -// * For information about the prerequisites for installing {hcp-title} clusters, see xref:../../rosa_planning/rosa-sts-aws-prereqs.adoc#rosa-sts-aws-prereqs[AWS prerequisites for ROSA with STS]. -endif::openshift-rosa-hcp[] +* For information about the prerequisites for installing {product-title} clusters, see xref:../../rosa_planning/rosa-hcp-aws-prereqs.adoc#rosa-hcp-aws-prereqs[Detailed requirements for deploying {product-title}]. include::modules/rosa-troubleshoot-hcp-install.adoc[leveloffset=+1] -//remove these conditionals once HCP migration happens - -// [role="_additional-resources"] -// .Additional resources +[role="_additional-resources"] +.Additional resources // * For information about the required IAM, see xref:../../rosa_planning/rosa-sts-ocm-role.adoc#rosa-sts-ocm-role[ROSA IAM role resources]. -// ifndef::openshift-rosa-hcp[] -// * For information about the AWS STS prerequisites for {hcp-title} clusters, see xref:../../welcome/cloud-experts-rosa-hcp-sts-explained.adoc#cloud-experts-rosa-hcp-sts-explained[AWS STS and ROSA with HCP explained]. -// endif::openshift-rosa-hcp[] +* For information about the AWS STS prerequisites for {product-title} clusters, see xref:../../rosa_architecture/cloud-experts-rosa-hcp-sts-explained.adoc#cloud-experts-rosa-hcp-sts-explained[AWS STS and {product-title} explained]. include::modules/rosa-hcp-no-console-access.adoc[leveloffset=+1] [role="_additional-resources"] .Additional resources -ifndef::openshift-rosa-hcp[] -* For more information about the {product-title} OAuth server, see xref:../../authentication/understanding-authentication.adoc#oauth-server-overview[ROSA OAuth server]. -* For more information about the {product-title} ingress operator, xref:../../networking/networking_operators/ingress-operator.adoc#configuring-ingress-controller[Configuring the Ingress Controller]. -endif::openshift-rosa-hcp[] +* For more information about the {product-title} OAuth server, see xref:../../authentication/understanding-authentication.adoc#oauth-server-overview[{product-title} OAuth server]. +//Commented out until Networking book has been fully migrated. +//* For more information about the {product-title} ingress operator, xref:../../networking/networking_operators/ingress-operator.adoc#configuring-ingress-controller[Configuring the Ingress Controller]. * For more information about the web console, see xref:../../web_console/web-console-overview.adoc#web-console-overview[Web Console Overview]. include::modules/rosa-hcp-ready-no-console-access.adoc[leveloffset=+1] -ifndef::openshift-rosa-hcp[] + [role="_additional-resources"] .Additional resources * For more information about the `rosa describe machinepool` command, see xref:../../cli_reference/rosa_cli/rosa-manage-objects-cli.adoc#rosa-list-objects[List and describe objects]. -endif::openshift-rosa-hcp[] include::modules/rosa-hcp-private-ready-no-console-access.adoc[leveloffset=+1] diff --git a/support/troubleshooting/rosa-troubleshooting-installations.adoc b/support/troubleshooting/rosa-troubleshooting-installations.adoc index 7852aaa963..3672c70561 100644 --- a/support/troubleshooting/rosa-troubleshooting-installations.adoc +++ b/support/troubleshooting/rosa-troubleshooting-installations.adoc @@ -7,3 +7,7 @@ include::_attributes/attributes-openshift-dedicated.adoc[] toc::[] include::modules/rosa-troubleshooting-installing.adoc[leveloffset=+1] + + + +