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
@@ -192,12 +192,12 @@ If you plan to use network security groups to control network traffic, take
192
192
- Identify the Azure region that you plan to use for HDInsight, and create a safe list of the IP addresses for your region. For more information, see [Health and management services: Specific regions](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses#health-and-management-services-specific-regions).
193
193
- Identify the IP addresses that HDInsight requires. For more information, see [HDInsight management IP addresses](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses).
194
194
- Create or modify the network security groups for the subnet that you plan to install HDInsight into. For network security groups, allow inbound traffic on port 443 from the IP addresses. This configuration ensures that HDInsight management services can reach the cluster from outside the virtual network.
195
-
195
+
196
196
---
197
197
198
198
## Error code: Cluster setup failed to install components on one or more hosts
199
199
200
-
### Error
200
+
### Error
201
201
202
202
"Cluster setup failed to install components on one or more hosts. Please retry your request."
203
203
@@ -209,6 +209,42 @@ Typically, this error is generated when there's a transient problem or an Azure
209
209
210
210
Check the [Azure status](https://status.azure.com) page for any Azure outages that might affect cluster deployment. If there are no outages, retry cluster deployment.
Unable to connect to cluster management endpoint. Please retry later.
219
+
220
+
### Cause
221
+
222
+
HDInsight Service cannot connect to your cluster when attempting to create the cluster
223
+
224
+
### Resolution
225
+
226
+
If you are using custom VNet network security group (NSGs) and user-defined routes (UDRs), ensure that your cluster can communicate with HDInsight management services. For additional information see [HDInsight management IP addresses](https://docs.microsoft.com/azure/hdinsight/hdinsight-management-ip-addresses).
227
+
228
+
---
229
+
230
+
## Error Code: Deployments failed due to policy violation: 'Resource '<ResourceURI>' was disallowed by policy. Policy identifiers: '[{"policyAssignment":{"name":"<PolicyName> ","id":"/providers/Microsoft.Management/managementGroups/<ManagementGroupName> providers/Microsoft.Authorization/policyAssignments/<PolicyName>"},"policyDefinition": <PolicyDefinition>
231
+
232
+
### Cause
233
+
234
+
Subscription-based Azure policies can deny the creation of public IP addresses. HDInsight cluster creation requires two public IPs.
235
+
236
+
The following policies generally impact cluster creation:
237
+
238
+
* Policies which prevent creating IP Addresses or Load balancers within the subscription.
239
+
* Policy which prevent creating storage accounts.
240
+
* Policy which prevent deleting networking resources such as IP Addresses or Load Balancers.
241
+
242
+
### Resolution
243
+
244
+
Delete or Disable the subscription-based Azure policy while creating HDInsight Cluster.
245
+
246
+
---
247
+
212
248
## Next steps
213
249
214
250
For more information about troubleshooting errors in cluster creation, see [Troubleshoot cluster creation failures with Azure HDInsight](https://docs.microsoft.com/azure/hdinsight/hadoop/hdinsight-troubleshoot-cluster-creation-fails).
0 commit comments