Metadata 404 Not Found

bli111 · May 21, 2025, 6:01pm

We’re experiencing an issue where older metadata is causing “Metadata Not Found” errors after syncing from upstream and creating a new publication. Our goal is to avoid these errors while still being able to update the repository with new metadata.

Is it possible to retain the old metadata after performing a sync from upstream, and still create a new publication that includes both the old and new metadata? This way, we can prevent the metadata errors when clients attempt to fetch data during the sync process.

x9c4 · May 22, 2025, 6:26am

I assume “metadata” means, you are in the RPM world.
I know that pulp_deb has something resembling that by serving a layered stack of recent publications.

github.com

pulp/pulp_deb/blob/main/pulp_deb/app/models/publication.py#L135

    
      
                      return pa.content_artifact
                  return
          
          
    class Meta:
                  default_related_name = "%(app_label)s_%(model_name)s"
                  permissions = [
                      ("manage_roles_aptdistribution", "Can manage roles on an APT distribution"),
                  ]
          
          

          
class DistributedPublication(BaseModel):
              """
              Represents a history of distributed publications.
          
          
    This allows the content handler to serve a previous Publication's content for a set period of
              time.
          
          
    When a new Publication is served by a Distribution, it creates a new DistributionPublication and
              sets the expires_at field on any existing DistributionPublications.
              """

bli111 · May 22, 2025, 1:11pm

Yes, they are rpm repos. Will the same feature be added to pulp_rpm?