Red Hat Certificate Upload Issues

Problem

The patch scan or deployment failed with the message "Linux package manager metadata files are not available because the Red Hat certificates are invalid"

Cause

• No active subscription on the agent-installed system.
• Valid certificate with access to cdn.redhat.com is missing in the selected system.

Resolution

1. Navigate to Threats & Patches → Settings → Redhat Linux Settings and ensure if any one of the below possible errors has encountered.
   • Error while uploading certificate from Agent to Server:
     • Certificate upload process from the chosen system is in-progress.
     • Certificate upload process from a previously nominated system is in-progress.
     • Certificate upload process from a previously nominated system has failed; a valid certificate will be uploaded from other agents.
     • Certificate upload from the chosen system has failed; a valid certificate will be uploaded from other agents.
   • Uploaded certificate is invalid:
     • Red Hat subscription validation process has failed due to timeout.
     • Red Hat patching for this edition will fail due to the certificate being expired; a valid certificate will be uploaded from other agents.
     • Uploaded certificate is about to expire; renew subscription.
   • Error remarks shown while choosing the alternate system:
     • The chosen system has an invalid Red Hat subscription; kindly choose an alternate system.
     • The chosen system has an RHUI subscription, which is not supported; kindly choose an alternate system.
     • The chosen system has configured a private mirror, which is not supported; kindly choose an alternate system.
     • The chosen system has a Red Hat Satellite subscription, which is not supported; kindly choose an alternate system.
2. If you encounter the above errors, kindly follow these resolution steps,
   • To receive updates from the Red Hat portal, you need to have an active subscription.
     • Refer here for purchasing a redhat subscription.
     • Refer here for managing your subscriptions .
   • Verify your purchased subscription.
     • Check the subscription status of the system by running the command: sudo subscription-manager status in the Linux terminal.
       • If you have Simple Content Access(SCA) enabled in your redhat account, then systems simply need to be registered (via subscription-manager) to get access to the repositories. Ensure that either of the following status is displayed.

         1. When SCA is enabled

            subscription-manager status +-------------------------------------------+     System Status Details +-------------------------------------------+ Overall Status: Disabled Content Access Mode is set to Simple Content Access. This host has access to content, regardless of subscription status. System Purpose Status: Disabled

         2. When SCA is disabled

            subscription-manager status +-------------------------------------------+     System Status Details +-------------------------------------------+ Overall Status: Current System Purpose Status: Matched

       • If the Red Hat Subscription status is 'Unknown', then it could be because your machine was registered when it was offline. If that's the case, refer to the steps here.
       • If the Red Hat Subscription Status is 'Insufficient', then it could be because you have subscribed a VM machine which was migrated. In that case, refer to the steps here.
       • If you still face a problem or the subscription status was neither of the above two cases, then try to reattach the subscription or try executing the command "subscription-manager refresh", which updates your system with the latest subscription information from Red Hat. Then verify that the entitlement certificates are present in /etc/pki/entitlement/ directory.
     • If the purchased subscription is expired, renew your subscription. Refer here for the renewal steps.
   • Verify if valid Red Hat repository is configured in your systems,
     • Check if it meets the required criteria, as mentioned here.
     • If the valid .repo file is missing, ensure /etc/rhsm/rhsm.conf has manage_repos set to "1".

Further Assistance

If you encounter any error messages other than the ones mentioned, or if the issue persists after following the resolution steps, kindly contact patchmanagerplus-support@manageengine.com.