duplicate_server_entries_in_controller
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
duplicate_server_entries_in_controller [2021/09/22 12:39] – walkeradmin | duplicate_server_entries_in_controller [2021/09/22 12:42] – walkeradmin | ||
---|---|---|---|
Line 28: | Line 28: | ||
ipaddress=ipaddress of the controller | ipaddress=ipaddress of the controller | ||
servername=the name of the failed server listed in controller | servername=the name of the failed server listed in controller | ||
+ | |||
+ | For orchestrated deployments, | ||
\\ | \\ | ||
\\ | \\ | ||
- | For orchestrated deployments, | + | Login to the node with MDT installed (normally the first HA node) |
+ | \\ | ||
+ | \\ | ||
+ | Execute | ||
+ | kubectl -n mediakind get pods (to find exact name of unified-ui pod) | ||
+ | We are looking for the name of the unified-ui pod. | ||
+ | \\ | ||
+ | \\ | ||
+ | On my test system it was called unified-ui-576c87cbbd-vd42h. Your system will be different. | ||
+ | \\ | ||
+ | \\ | ||
+ | Now execute the following, using your unified-ui name | ||
+ | \\ | ||
+ | \\ | ||
+ | kubectl -n mediakind exec -it unified-ui-576c87cbbd-vd42h -c ui /bin/sh (edit pod, ui is the name of the internal pod) | ||
\\ | \\ | ||
\\ | \\ | ||
- | kubectl -n mediakind get pods (to find exact name of unified-ui pod) | ||
- | kubectl -n mediakind exec -it unified-ui-576c87cbbd-vd42h -c ui /bin/sh (edit pod, ui is the name of the internal pod) | ||
curl api-gateway: | curl api-gateway: | ||
curl -X DELETE api-gateway: | curl -X DELETE api-gateway: |
duplicate_server_entries_in_controller.txt · Last modified: 2023/03/09 22:35 by 127.0.0.1