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

Yum Metadata being impartially regenerated.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.14.0
    • Fix Version/s: None
    • Component/s: Yum
    • Labels:
    • Environment:
      redhat
    • Story Points:
      2

      Description

      We have a fairly large yum repository for our devops builds.  Our repodata folder rarely seems to be consistent.

      It appears that the primary.xml.gz is being updated and repomd.xml but not the -other.xml.gz and -filelists.xml.gz.  

      I believe this inconsistency is primarily due to NEXUS-18737, but i'm creating this bug as the repomd.xml file shouldn't be changed, and the old metadata should never be deleted, until the new metadata files are written.

      I.e. the workflow that I believe should be occuring:

      1) User uploads new rpm.

      2) Partial Metadata update regenerates primary, filelists, other, persists with new filenames.

      3) repomd.xml is updated to the new files.

      4) old metadata primary, filelists, other files are deleted.

       

      I believe what is actually occuring:

      1) User uploads new rpm.

      2) repomd.xml is updated to point to new, uncreated files.

      3) primary gets created, written, old primary is deleted

      4) NEXUS-18737 occurs, -filelists & -other don't get updated.

      5) A full metadata regeneration occurs, which corrects the corrupt metadata.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ruckc Curtis Ruck
              Last Updated By:
              Peter Lynch Peter Lynch
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Date of First Response:

                  tigCommentSecurity.panel-title