Search code examples
artifactoryrpmyumoraclelinux

After 2023-03-28 http://yum.oracle.com/repo/OracleLinux/ fails Artifactory testremote via API and Admin UI

Problem

We seem to have a replication problem on a remote rpm/yum repo. We replicate http://yum.oracle.com/repo/OracleLinux/ as rpm-oraclelinux-remote and up until 28-03-23 15:29:41 +00:00 it worked fine but now it is failing it's Artifactory /ui/api/v1/ui/admin/repositories/testremote repository check with a 404. This check can be run via XMLHttpRequest or directly from the Artifactory Admin UI

When I look at a syncing or passing yum repo I see the following for repomd.xml

  • created: 09-06-22 20:07:12 +00:00
  • last modified: 30-03-23 13:24:26 +00:00
  • last download: 30-03-23 18:40:43 +00:00

When I look at oraclelinux's I see

  • created: 30-03-23 18:37:16 +00:00
  • last modified: 28-03-23 15:29:41 +00:00
  • last download: 30-03-23 18:37:16 +00:00

I also did some testing and it does seem like we have what is cached by Artifactory but cannot pull additional content.

So, anyone have any ideas as to if Oracle changed their repo policy for http://yum.oracle.com/

My guess is that I'll need to make one remote repo per OL* version as in

Solution

  • It turns out that the test button in Jfrog artifactory failures cannot be trusted in Artifactory 7.33 at least. Here's the evidence

    • remote repo test button still report failure 404
    • 2023-04-04 16:13:23 UTC metadata updated, new kernel + associated packages auto cached into the repo

    So, my guess is that in our version and perhaps in the most recent that the test api naively attempts to access the root of the external url and does not do so via an appropriate repo type. For instance the yum/dnf or repoquery approach would seek out the repo metadata below an additional path whereas maven could look at the root.

    At any rate, if you get a fail, you really want 2ndry confirmation that the failure is real and not a phantom