How to forcefully regenerate metadata of a content view or repository on Red Hat Satellite 6?
Environment
- Red Hat Satellite 6
Issue
- How to recreate metadata of a
Content View
orRepository
? -
Unable to update package(s) and the below error is faced:
https://satellite.lab.example.com/pulp/repos/Organization/Library/RHEL7_Baseline/content/dist/rhel/server/7/7Server/x86_64/os/repodata/repomd.xml: [Errno 14] HTTPS Error 404 - Not Found
Resolution
-
To forcefully regenerate metadata of a Content View or Repository, the below steps need to be followed on the Red Hat Satellite WebUI:
-
For a Content View:
- Go to
Content
->Content Views
-> Select the particular Content View -> Click onPublish New Version
-> Check mark the box ofForce Yum Metadata Regeneration
-> Save.
- Go to
-
For an existing version of Content View:
- Go to Content -> Content Views -> Select the content view -> Click
Versions
tab -> Click inActions
column besidePromote
drop down arrow ->Regenerate Repository Metadata
- Go to Content -> Content Views -> Select the content view -> Click
-
For a particular repository:
- Go to
Content
->Products
-> Select the Product -> Click on the particular repository -> SelectAction
->Republish Repository Metadata.
- Go to
-
Via hammer:
# hammer content-view version republish-repositories --content-view-id 4 --version 2.0
Replace 4 and 2.0 according to your environment.
# hammer content-view list ==> this gives the content-view-id for the concerned content view # hammer content-view info --id=4 ==> this gives the version of that content view. [ replace 4 by the id from previous command ]
-
-
For
pulp-3
/ since Satellite 6.10, follow this solution andhammer
command like:
hammer content-view version republish-repositories --id 23 --force true
to forcefully republish a given Content View version.
For more KB articles/solutions related to Red Hat Satellite 6.x Content View Issues, please refer to the Red Hat Satellite Consolidated Troubleshooting Article for Red Hat Satellite 6.x Content View Issues
Root Cause
- The repodata of a Content View or Repository is unavailable or corrupted.
This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.
Comments