LAB NOTES: Satellite Server 6.6.0 Installation on RHEL 7.7

Started off this new installation on the bright side of things after having worked through DNS issues, so I muscled thru it and published an article on that solution.

Now lets explore what it takes to install Satellite 6.6.0 on RHEL 7.7, I will leave all the documentation requirements for you to review directly from Red Hat publications. The purpose of these notes is to share the things I came into during the installation process.

Steps are pretty straight forward.

  1. Download the latest ISO from Red Hat
  2. Update the OS to the latest version or patch level
  3. Mount the ISO onto the server
  4. Make sure the server name is in DNS and matches both A Record and PTR otherwise the installation will prevent you from proceeding. This is a big fix from previous releases, it will simply not let you proceed unless DNS is Gucci
  5. Run the “install_packages” script from the mounted ISO, this takes about 10 – 15 minutes to complete (depending on the size of the machine or instance)
  6. Then run the installer “satellite-installer –scenario satellite”, this process could take about 30 minutes to complete

After the installation completed I inspected the satellite-maintain service list, produced this output

# satellite-maintain service list
Running Service List
================================================================================
List applicable services: 
dynflowd.service                              disabled
foreman-proxy.service                         enabled 
httpd.service                                 disabled
postgresql.service                            enabled 
pulp_celerybeat.service                       enabled 
pulp_resource_manager.service                 enabled 
pulp_streamer.service                         enabled 
pulp_workers.service                          enabled 
puppetserver.service                          enabled 
qdrouterd.service                             enabled 
qpidd.service                                 enabled 
rh-mongodb34-mongod.service                   enabled 
smart_proxy_dynflow_core.service              enabled 
squid.service                                 enabled 
tomcat.service                                enabled

All services listed                                                   [OK]
--------------------------------------------------------------------------------

Now to start the Satellite Server I ran the “satellite-maintain service start”

# satellite-maintain service start
Running Start Services
================================================================================
Check if command is run as root user:                                 [OK]
--------------------------------------------------------------------------------
Start applicable services: 
Starting the following service(s):

rh-mongodb34-mongod, postgresql, qdrouterd, qpidd, squid, pulp_celerybeat, pulp_resource_manager, pulp_streamer, pulp_workers, smart_proxy_dynflow_core, tomcat, dynflowd, httpd, puppetserver, foreman-proxy
- All services started                                                [OK]

Further inspection of the resources I checked for foreman and httpd

# ps -ef | grep foreman
foreman+ 16152     1  0 12:44 ?        00:00:05 ruby /usr/share/foreman-proxy/bin/smart-proxy --no-daemonize
foreman+ 16359     1  0 12:45 ?        00:00:07 ruby /usr/bin/smart_proxy_dynflow_core -d -p /var/run/foreman-proxy/smart_proxy_dynflow_core.pid
foreman  19410     1  1 13:16 ?        00:00:13 dynflow_executor_monitor
foreman  19413     1 13 13:16 ?        00:01:54 dynflow_executor
postgres 19556  5506  0 13:17 ?        00:00:00 postgres: foreman foreman [local] idle
postgres 19567  5506  0 13:17 ?        00:00:00 postgres: foreman foreman [local] idle
postgres 19569  5506  0 13:17 ?        00:00:00 postgres: foreman foreman [local] idle
postgres 19581  5506  0 13:18 ?        00:00:00 postgres: foreman foreman [local] idle
postgres 19585  5506  0 13:18 ?        00:00:00 postgres: foreman foreman [local] idle
postgres 19598  5506  0 13:18 ?        00:00:01 postgres: foreman foreman [local] idle
root     20619  2809  0 13:29 pts/0    00:00:00 grep --color=auto foreman


# ps -ef | grep http
root     12144     1  0 12:07 ?        00:00:14 /usr/sbin/httpd -DFOREGROUND
apache   12209 12144  0 12:08 ?        00:00:01 /usr/sbin/httpd -DFOREGROUND
apache   12210 12144  0 12:08 ?        00:00:01 /usr/sbin/httpd -DFOREGROUND
apache   12214 12144  0 12:08 ?        00:00:02 /usr/sbin/httpd -DFOREGROUND
apache   12215 12144  0 12:08 ?        00:00:01 /usr/sbin/httpd -DFOREGROUND
apache   12222 12144  0 12:08 ?        00:00:01 /usr/sbin/httpd -DFOREGROUND
apache   12227 12144  0 12:08 ?        00:00:01 /usr/sbin/httpd -DFOREGROUND
apache   12236 12144  0 12:08 ?        00:00:01 /usr/sbin/httpd -DFOREGROUND
apache   12242 12144  0 12:08 ?        00:00:01 /usr/sbin/httpd -DFOREGROUND
root     20633  2809 18 13:30 pts/0    00:00:00 grep --color=auto http

Leave a Reply

RELATED POST

Metamask Wallet

My metamask wallet 0x55e8D52847EC9D5b2D4c263723e57aAa4e770a35

Veritas Volume Manager: Growing a disk group and expand the filesystem

Validated by Mr Man! Lets start off on node2 [root@node02 ~]# vxdisk list DEVICE TYPE DISK GROUP STATUS sda auto:none…

Virtual Machine Manager: Error starting domain

Starting up the KVM error occurred Error starting domain: Requested operation is not valid: network 'default' is not active Locate…

Git Commands

How to initialize a Git repo: Everything starts from here. The first step is to initialize a new Git repo…