Hi Piotr,

Thanks for the feedback. I checked the file in question and at first it was returning 404 errors but after some time artifactory was able to fetch the file. Did you zap the cache?
http://artifactory.ovirt.org/artifactory/ovirt-mirror/org/ovirt/vdsm-jsonrpc-java/vdsm-jsonrpc-java-client/1.4.5/

In any case, having the directory in place but files unreachable may mean that metadata is in place but artifact retrieval fails. There's a 2h timeout on failed failure caching as noted before so if no manual zapping happened this is in play here.

I set the following values for the jboss mirror:

Unused Artifacts Cleanup Period (Hr) 720 (30d)
Metadata Retrieval Cache Period (Sec) 7200 (2h)
Assumed Offline Period (Sec) 300 (5 min)
Missed Retrieval Cache Period (Sec) 3600 (1h)

Let's see if this makes changes appear faster on artifactory. We can't set these values too low as this may overload upstream servers. I wonder if we can modify the release process so that a new library version automatically triggers a metadata refresh on artifactory.

I release two versions together as one bundle for master and 4.1. Stable branch was built OK but there was an issue with master [1].
I am not sure why one was synchronized and the other not but it seems that we haven't fully fixed the issue.

[1] http://jenkins.ovirt.org/job/ovirt-engine_master_find-bugs_created/16376/console

Thanks, let's close it for now and re-open if we see it again.

I haven't seen any issue with synchronization recently.

does the issue still appear for you?