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
Copy file name to clipboardExpand all lines: articles/operator-nexus/troubleshoot-dns-issues.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,6 @@ can't be contacted which impacts deployment or management of Nexus resources.
20
20
## Diagnosis
21
21
22
22
* Deployment or management of remote Nexus resources fails with "DeploymentFailed."
23
-
* Geneva logging shows 500 and/or 503 HTTP errors and failure to access Azure resources such as VM images hosted in ACRs (Azure Container Registry).
24
23
* Azure portal shows no errors being generated for the Azure resources that are unreachable; there are no errors because the failing operations aren't reaching the Azure resources at all.
25
24
26
25
## Mitigation steps
@@ -30,9 +29,8 @@ Follow these steps for mitigation.
30
29
### Trigger a DNS cache refresh for the NNF Workload Proxy
31
30
32
31
```bash
33
-
az login
34
-
az account set --subscription <SUBSCRIPTION>
35
-
az resource tag --tags exampleTag=exampleValue --name <CLUSTER> --resource-group <CLUSTER_RG> --resource-type "Microsoft.ContainerService/managedClusters"
32
+
# TBD awaiting feedback from folks who worked on the original IcMs as to
0 commit comments