Recovering corrupted content

Resynchronize corrupted repositories on orcharhino Server, verify checksums on orcharhino Proxy Servers, and republish repository or content view metadata when the repository metadata no longer matches stored content.

Additional resources

Recovering a corrupted repository by using orcharhino management UI

Recover a corrupted repository with optimized or complete advanced sync, and optionally verify content checksums to confirm packages match upstream sources.

Procedure

  1. In the orcharhino management UI, navigate to Content > Products.

  2. Select the product containing the corrupted repository.

  3. Select the name of a repository you want to synchronize.

  4. To perform optimized sync or complete sync, select Advanced Sync from the Select Action menu.

  5. Select the required option and click Sync.

  6. Optional: To verify the checksum for a Yum repository, click Verify Content Checksum from the Select Action menu.

Additional resources

Recovering a corrupted repository by using Hammer CLI

Recover a corrupted repository by using optimized sync, complete sync, or validate-content synchronization when packages or metadata no longer match expected content.

Procedure

  1. Obtain a list of repository IDs:

    $ hammer repository list \
--organization "My_Organization"

  2. Synchronize a corrupted repository using the necessary option:

    • For the optimized synchronization:

      $ hammer repository synchronize \
--id My_ID

    • For the complete synchronization:

      $ hammer repository synchronize \
--id My_ID \
--skip-metadata-check true

    • For validating content of a Yum repository:

      $ hammer repository synchronize \
--id My_ID \
--validate-contents true
Additional resources

Recovering corrupted content on a orcharhino Proxy Server by using orcharhino management UI

Verify checksums for a lifecycle environment or content view on your orcharhino Proxy Server when hosts cannot consume content and you need to repair corrupted files on the orcharhino Proxy Server.

Procedure

  1. In the orcharhino management UI, navigate to Infrastructure > orcharhino Proxies.

  2. Select your orcharhino Proxy Server.

  3. Recover corrupted content on your orcharhino Proxy Server.

    • To repair content in a lifecycle environment, click the options menu icon next to your lifecycle environment and select Verify Content Checksum.

    • To repair content in a content view, click the options menu icon next to your content view and select Verify Content Checksum.

Verification

  1. In the orcharhino management UI, navigate to Monitor > orcharhino Tasks > Tasks.

  2. Search for Verify checksum for content.

  3. Verify that the task completed successfully.

Recovering corrupted content on a orcharhino Proxy Server by using CLI

Verify checksums on your orcharhino Proxy Server for a repository, content view, lifecycle environment, or all orcharhino Proxy Server content when hosts cannot consume synchronized packages.

Prerequisites

  • The lifecycle environment, content view, or repository that you want to repair is available on the orcharhino Proxy Server.

Procedure

  1. Display a list of all orcharhino Proxies:

    $ hammer proxy list

    Note the ID of your orcharhino Proxy Server.

  2. Recover corrupted content on your orcharhino Proxy Server:

    • Repair content in a content view:

      $ hammer proxy content verify-checksum \
--content-view-id My_Content_View_ID \
--id My_orcharhino_Proxy_Server_ID \
--organization-id My_Organization_ID

    • Repair content in a lifecycle environment:

      $ hammer proxy content verify-checksum \
--id My_orcharhino_Proxy_Server_ID \
--lifecycle-environment-id My_Lifecycle_Environment_ID \
--organization-id My_Organization_ID

    • Repair content in a repository:

      $ hammer proxy content verify-checksum \
--id My_orcharhino_Proxy_Server_ID \
--organization-id My_Organization_ID \
--repository-id My_Repository_ID

    • Repair all content on your orcharhino Proxy Server:

      $ hammer proxy content verify-checksum \
--id My_orcharhino_Proxy_Server_ID
Verification

  • Verify that the task completed successfully:

    $ hammer task list --search "Verify checksum for content"

Republishing repository metadata by using orcharhino management UI

Republish repository metadata when published metadata does not match repository contents.

ATIX AG recommends a complete repository sync or publishing a new content view version to repair broken metadata instead.
Prerequisites

  • The mirroring policy of the repository is not set to Complete Mirroring. For more information, see Mirroring Policies Overview content-management.

    This action is not available for repositories that use the Complete Mirroring policy because the metadata is copied verbatim from the upstream source of the repository.

Procedure

  1. In the orcharhino management UI, navigate to Content > Products.

  2. Select the product that includes the repository for which you want to republish metadata.

  3. On the Repositories tab, select a repository.

  4. To republish metadata for the repository, click Republish Repository Metadata from the Select Action menu.

Republishing repository metadata by using CLI

Republish repository metadata when published metadata does not match repository contents.

ATIX AG recommends a complete repository sync or publishing a new content view version to repair broken metadata in favor of republishing repository metadata.
Prerequisites

  • The mirroring policy of the repository is not set to Complete Mirroring. For more information, see Mirroring Policies Overview content-management.

    This action is not available for repositories that use the Complete Mirroring policy because the metadata is copied verbatim from the upstream source of the repository.

Procedure

  • Republish metadata for your repository:

    $ hammer repository verify-checksum \
--name "My_Repository_Name" \
--organization-id My_Organization_ID \
--product "My_Product_Name"
Verification

  • Verify that the task completed successfully:

    $ hammer task list --search "Metadata generate repository"

Republishing content view metadata by using orcharhino management UI

Republish content view version metadata when hosts report checksum mismatches. orcharhino can regenerate metadata for repositories that do not use complete mirroring.

Republishing regenerates metadata for all repositories in the content view version that do not adhere to the Complete Mirroring policy.

Prerequisites

  • The content view version includes repositories that do not use the Complete Mirroring policy.

Procedure

  1. In the orcharhino management UI, navigate to Content > Lifecycle > Content Views.

  2. Select a content view.

  3. On the Versions tab, select a content view version.

  4. To republish metadata for the content view version, click Republish repository metadata from the options icon.

Republishing content view metadata by using CLI

Republish content view version metadata when hosts report checksum mismatches. orcharhino can regenerate metadata for repositories that do not use complete mirroring.

Republishing regenerates metadata for all repositories in the content view version that do not adhere to the Complete Mirroring policy.

Prerequisites

  • The content view version includes repositories that do not use the Complete Mirroring policy.

Procedure

  • Republish metadata for your content view version:

    $ hammer content-view version verify-checksum --id My_Content_View_Version_ID
Verification

  • Verify that the task completed successfully:

    $ hammer task list --search "Verify checksum of repositories in"

The text and illustrations on this page are licensed by ATIX AG under a Creative Commons Attribution Share Alike 4.0 International ("CC BY-SA 4.0") license. This page also contains text from the official Foreman documentation which uses the same license ("CC BY-SA 4.0").