Add guidance on allowed Geo IPs for 401 troubleshooting
What does this MR do and why?
This is copied over from the linked MR that Brie had open, I wanted to make sure this gets merged.
This MR updates the Geo Admin Area shows ‘Unknown’ for health status and ‘Request failed with status code 401’ troubleshooting section to add an additional suggestion.
Folks may be encountering this error because the IP address for the impacted secondary is not permitted in Allowed Geo IPs.
These issues may be of interest to folks interested in this MR:
This information was a critical part of resolving a ticket that is available to GitLab team members with access to Zendesk
This MR is being added to help reduce the time to resolve tickets like this in the future.
The Geo Admin Area shows ‘Unknown’ for health status and ‘Request failed with status code 401’ section was discussed regularly in our efforts. Having this information there at the time would have helped us to resolve the ticket much more effectively.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
| Before | After |
|---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.