Description
When providing a proxy via the collect logs UI which is necessary to reach outside of the network, the preflight reachability check prior to initiating the log collection will fail as it does not make use of the provided proxy.
If a proxy is given via the Web UI, we should use that with the preflight check or perhaps provide context that the proxy was not used in this check and allow the user to proceed with the collection.
Attachments
Gerrit Reviews
For Gerrit Dashboard: MB-32561 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
110977,2 | MB-32561 Check proxy reachability on log collection | master | ns_server | Status: ABANDONED | -2 | +1 |
111115,12 | MB-32561 Check proxy reachability on log collection | master | ns_server | Status: MERGED | +2 | +1 |
111929,1 | MB-32561 Check proxy reachability on log collection | master | ns_server | Status: ABANDONED | -1 | 0 |
118501,2 | MB-37064 Backport Check proxy reachability on log collection MB-32561 Check proxy reachability on log collection | alice | ns_server | Status: MERGED | +2 | +1 |
118597,4 | MB-32561 Remove unreachable function clause | master | ns_server | Status: MERGED | +2 | +1 |
118601,1 | Merge commit 'couchbase/alice~3' into madhatter | mad-hatter | ns_server | Status: MERGED | +2 | +1 |
118750,1 | Merge remote-tracking branch 'couchbase/mad-hatter' | master | ns_server | Status: MERGED | +2 | +1 |