Red Hat Satellite: Difference between revisions

From DikapediaV2
Jump to: navigation, search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 69: Line 69:
----
----
  $ sudo subscription-manager identity
  $ sudo subscription-manager identity
==== How to fix Affected packages with CVE's ====
----
some useful commands you can use to see if there are Security Vulnerabilities/CVEs for any package:
​# Check for important security update for a package (it provides the RHSA and CVE numbers)
* NOTE: There will only be output if the registered lifecycle has the advisory information
$ dzdo dnf updateinfo list updates security | grep <package>
# Update RHSA number based off previous output (Replace XXX:YYYY with the actual number):
$ dzdo dnf updateinfo info RHSA-XXX:YYYY
# Update CVE number based off output above (Replace XXX:YYYY with the actual number):
$ dzdo dnf updateinfo info --cve CVE-XXX:YYYY
# Alternative Update method using advisory number:
$ dzdo dnf update --advisory=RHSA-XXX:YYYY

Latest revision as of 16:10, 23 October 2026

How to Enable a Red Hat Repository in Satellite


  1. . Log in to RHEL Satellite
  2. . Go to Content > Red Hat Repositories
  3. . Find the Red Hat Repository you are looking for on the left side, "Available Repositories"
  4. . Then select it and click the plus "+" symbol. It will move it to the right, "Enabled Repositories".


How to create a new repository in Satellite


  1. . Go to Red Hat Satellite > Content > Product (select organization) > Software Center > Repositories > Click New Repository.
  2. . Then select/enter/check these settings:
    1. . Name: Rhel7_test_repro
    2. . Label: Rhel7_test_repro
    3. . Description
    4. . Type: file
    5. . Verify SSL
    6. . HTTP Proxy Policy: Global Default (None)
    7. . Unprotected
  3. . Hit Save
  4. . Then click on the new repository and upload binaries, rpm/tar packages, files, etc.


Managing Content Views


https://access.redhat.com/documentation/en-us/red_hat_satellite/6.6/html/content_management_guide/managing_content_views

Red hat Satellite 6 uses Content Views to create customized repositories from the repositories. To do this, you must define which repositories to use and then apply certain filters to the content. These filters include both package filters, package group filters, and errata filters. You can use Content Views to define which software versions a particular environment uses. For example, a Production environment might use a Content View containing older package versions, while a Development environment might use a Content View containing newer package versions.

Each Content View creates a set of repositories across each environment, which Satellite Server stores and manages. When you promote a Content View from one environment to the next environment in the application life cycle, the respective repository on Satellite Server updates and publishes the packages.

  1. . Creating a Content View
  2. . Promoting a Content View


How to Create Activation Key to Allow Users to Register to Satellite Repo


  1. . Login to Red Hat Satellite
  2. . Go to Content > Activation Keys
  3. . Select Create Activation Key
  4. . Provide Name (i.e. RHEL79_SRV)
  5. . Provide Description (optional)
  6. . Select the Environment (i.e. RHEL7)
  7. . In the Content View drop down, select the Content View you want (i.e. RHEL79)
  8. . Click Save
  9. . You should now see the Activation Key which can be used during system registration, i.e.
subscription-manager register --org="org_name" --activationkey="RHEL79_SRV"


How to Unregister and Re-register to a new Satellite Repo


$ sudo subscription-manager remove --all
[sudo] password for user:
0 subscriptions removed at the server.

$ sudo subscription-manager unregister
Unregistering from: 123.xyz.com:443/rhsm
System has been unregistered.

$ sudo subscription-manager clean
All local data removed

$ sudo subscription-manager register --force --org="org_name" --activationkey="RHEL8_SRV"
The system has been registered with ID: 1234abcd-123c-34fd-vc23-1111122222333
The registered system name is: <hostname>


Check Subscription-Manager Identity


$ sudo subscription-manager identity


How to fix Affected packages with CVE's


some useful commands you can use to see if there are Security Vulnerabilities/CVEs for any package:

​# Check for important security update for a package (it provides the RHSA and CVE numbers)

  • NOTE: There will only be output if the registered lifecycle has the advisory information
$ dzdo dnf updateinfo list updates security | grep <package>
  1.  Update RHSA number based off previous output (Replace XXX:YYYY with the actual number):
$ dzdo dnf updateinfo info RHSA-XXX:YYYY
  1.  Update CVE number based off output above (Replace XXX:YYYY with the actual number):
$ dzdo dnf updateinfo info --cve CVE-XXX:YYYY
  1.  Alternative Update method using advisory number:
$ dzdo dnf update --advisory=RHSA-XXX:YYYY