[RTFACT-15481] Better Error Handling in UI for Remote Repo Issues Created: 15/Dec/17  Updated: 14/May/18

Status: Open
Project: Artifactory Binary Repository
Component/s: Remote Repository , Web UI
Affects Version/s: 5.5.1
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Sean Quinn Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: artifactory, ui

HA Artifactory Setup on Centos 7


It appears that we are unable to configure an existing remote rpm repo via the UI if the remote is inaccessible.

Steps to reproduce:

1. Configure a remote rpm repo with a valid url

2. Make the remote url inaccessible

3. Attempt to navigate to https://<artifactory url> /artifactory/webapp/#/admin/repository/remote/<repo name>/edit

After step #3 is complete the UI will sit on a spinning wheel until the server finally returns a 500 error. In our specific case were using https://repos.influxdata.com as the remote.

We would like to see something better than a spinning wheel under these circumstances, traffic to remotes often can be blocked by proxies or because of remotes being unavailable for whatever reason. The UI should reflect this so customers without access to logs can have better visibility into the problem and reconfigure remotes to point elsewhere when issues are encountered.

Comment by Guy Cohen [ 14/May/18 ]

Hello Sean Quinn, we added this issue to our backlog but since this is not a common use-case, we have no ETA to share at the moment.

Generated at Thu Jul 02 10:10:35 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.