Uploaded image for project: 'Dev - Nexus Repo'
  1. Dev - Nexus Repo
  2. NEXUS-31817

Yum metadata in group repository shows as empty.

    Details

    • Type: Bug
    • Status: New
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.37.3
    • Fix Version/s: None
    • Component/s: Yum
    • Labels:
    • Notability:
      2

      Description

      Create a set of yum repositories in Nexus Repo:

      ├ ⧈ yum-group (yum-group)
      │   ├ ▶ yum-proxy (yum-proxy) ≻ http://mirror.centos.org/centos/
      │   ├ • yum-hosted (yum-hosted)
      │   └ ▶ rhel-proxy (yum-proxy) ≻ https://cdn.redhat.com/content/dis/rhel/server/7
      

      For the purposes of this test it is not necessary to add the client certificate for the redhat proxy.

      Then request the "/repository/yum-group/7/os/x86_64/repodata/repomd.xml" file through the instance. Sometimes (but not always) this will come back empty:

      <?xml version="1.0" ?>
      <repomd xmlns="http://linux.duke.edu/metadata/repo" xmlns:rpm="http://linux.duke.edu/metadata/rpm">
      	<revision>1649878384</revision>
      </repomd>
      

      But the same down request made to the proxy (/repository/yum-proxy/7/os/x86_64/repodata/repomd.xml) will have correct metadata.

      When this happens there is no good way to recover. Expiring cache will not fix it, nor will adding or removing members from the group repository. The only option is to delete the group and recreate it.

      The logs will show the group is attempting to merge metadata from the yum-proxy repository:

      2022-04-14 12:25:23,846-0500 INFO [qtp1852501519-712] admin org.sonatype.nexus.repository.yum.internal.group.YumGroupMergerImpl - Requesting repodata/845e42288d3b73a069e781b4307caba890fc168327baba20ce2d78a7507eb2af-other.xml.gz from yum-proxy
      2022-04-14 12:25:23,859-0500 INFO [qtp1852501519-712] admin org.sonatype.nexus.repository.yum.internal.group.YumGroupMergerImpl - Requesting repodata/5319616dde574d636861a6e632939f617466a371e59b555cf816cf1f52f3e873-filelists.xml.gz from yum-proxy
      2022-04-14 12:25:23,869-0500 INFO [qtp1852501519-712] admin org.sonatype.nexus.repository.yum.internal.group.YumGroupMergerImpl - Requesting repodata/a4e2b46586aa556c3b6f814dad5b16db5a669984d66b68e873586cd7c7253301-c7-x86_64-comps.xml.gz from yum-proxy
      2022-04-14 12:25:23,884-0500 INFO [qtp1852501519-712] admin org.sonatype.nexus.repository.yum.internal.group.YumGroupMergerImpl - Requesting repodata/2b479c0f3efa73f75b7fb76c82687744275fff78e4a138b5b3efba95f91e099e-primary.xml.gz from yum-proxy

      But those requests will not cause those files to be downloaded into the proxy repository. I believe that is the source of this bug, although I can't explain why it is intermittent.

       

      Note looks like that the outbound request from the group repository isn't firing to the proxy repository and thus leaving the metadata empty

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            rseddon Rich Seddon
            Last Updated By:
            Michael Oliverio Michael Oliverio
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Dates

              Created:
              Updated:

                tigCommentSecurity.panel-title