Confirm that your Satellite Server is installed and operating, with a correctly named organization and subscription manifest.
Outcomes
Verify the status of Red Hat Satellite services.
Verify the prerequisites for Red Hat Satellite.
Configure an organization and a location.
Associate a location with an organization.
As the student user on the workstation machine, use the lab command to prepare your system for this exercise.
This command prepares your environment and ensures that all required resources are available.
[student@workstation ~]$ lab start deploy-review
Instructions
To reduce exercise wait time, the initial Satellite classroom environment contains the preconfigured Operations and Finance organizations, each with an imported subscription manifest and presynchronized RHEL 9 BaseOS and AppStream repositories.
Verify the status of the Red Hat Satellite services.
Log in to the satellite system as the student user and switch to the root user.
[student@workstation ~]$ssh student@satellite[student@satellite ~]$sudo -i[sudo] password for student:student[root@satellite ~]#
Verify the status for Red Hat Satellite services.
[root@satellite ~]# satellite-maintain service list
Running Service List
================================================================================
List applicable services:
dynflow-sidekiq@.service indirect
foreman-proxy.service enabled
foreman.service enabled
httpd.service enabled
postgresql.service enabled
pulpcore-api.service enabled
pulpcore-content.service enabled
pulpcore-worker@.service indirect
redis.service enabled
tomcat.service enabled
All services listed [OK]
--------------------------------------------------------------------------------Verify the health of the Red Hat Satellite installation.
[root@satellite ~]# satellite-maintain health check
Running ForemanMaintain::Scenario::FilteredScenario
pass:[================================================================================]
Check number of fact names in database: [OK]
--------------------------------------------------------------------------------
Check whether all services are running: [OK]
--------------------------------------------------------------------------------
Check whether all services are running using the ping call: [OK]
--------------------------------------------------------------------------------
Check for paused tasks: [OK]
--------------------------------------------------------------------------------
Check whether system is self-registered or not: [OK]
--------------------------------------------------------------------------------Verify that the satellite system supports the prerequisites for running Red Hat Satellite Server, including firewall ports, time synchronization, and DNS name resolution.
Verify that both services and ports that Red Hat Satellite requires are enabled in the firewalld service.
[root@satellite ~]# firewall-cmd --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: eth0
sources:
services: dhcpv6-client ssh
ports: 53/udp 53/tcp 67/udp 69/udp 80/tcp 443/tcp 5647/tcp 8000/tcp 9090/tcp 8140/tcp
protocols:
forward: no
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:Verify that the chronyd service is active and enabled.
[root@satellite ~]#systemctl status chronyd● chronyd.service - NTP client/server Loaded: loaded (/usr/lib/systemd/system/chronyd.service;enabled; vendor preset: enabled) Active:active(running) since Tue 2022-02-22 11:38:21 EST; 6h ago ...output omitted...
Verify that localhost and the hostname for the satellite server resolve correctly.
[root@satellite ~]#ping -c1 localhostPING localhost(localhost (::1)) 56 data bytes 64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=1 ms ...output omitted... [root@satellite ~]#ping -c1 satellite.lab.example.comPING satellite.lab.example.com (172.25.250.16) 56(84) bytes of data. 64 bytes from satellite.lab.example.com (172.25.250.16): icmp_seq=1 ttl=64 time=1 ms ...output omitted...
Verify that the satellite system's reverse DNS name resolution succeeds.
[root@satellite ~]# host 172.25.250.16
16.250.25.172.in-addr.arpa domain name pointer satellite.lab.example.com.Return to the workstation system as the student user.
[root@satellite ~]#exitlogout [student@satellite ~]$exitlogout Connection to satellite closed. [student@workstation ~]$
Using the Satellite web UI, verify that the Finance organization exists and is configured with the local classroom CDN.
Use your browser to navigate to https://satellite.lab.example.com.
Log in as the admin user with the redhat password.
Select the Finance organization and the Any Location context in the top navigation bar.
Click → .
Verify that the Finance organization exists in the table and with Simple Content Access enabled.
Click → , and then click in the upper-right corner of the page.
On the Manage Manifest dialog, click the tab.
Verify that the URL field is set to http://cdn.lab.example.com.
Click .
Verify that the Subscriptions page lists multiple subscriptions for the Finance organization.
Create the San Francisco and Tokyo locations, and associate those locations with the Finance organization.
Click → .
On the page, click .
Enter San Francisco in the field, and then click .
On the page, click again .
Enter Tokyo in the field, and then click .
Click → .
On the page, click the link.
Click the link to open the dual-list selector.
Move the and items from the column to the column, to associate the San Francisco and Tokyo locations with the Finance organization.
Click to accept the changes.