Understand the installation process

The Service Portal installer package provides an installation script (propel_install.sh), which automates the installation process. This script executes the following steps:

  1. Installs Ansible.
  2. Sets up the environment for using Ansible over ssh (generates the target).

  3. Installs Service Portal dependencies.
  4. Installs Service Portal.
  • Between the installation of Ansible and the installation of the dependencies, the deploy_rhel_config_env.sh script is being called to generate the ansible_targets file. This script enables non-interactive execution by passing the password from propel_install.sh (which in turn is read from propel_install.config). The sensitive information from propel_install.config is erased once the installation is complete.
  • You can skip each of these steps using a command option, as described in Installation script options.

Installation script options

The following table describes important command options that you can use when running the propel_install.sh script.

Option Description

--no-install-ansible

Skips the Ansible installation step.
--no-generate-target Skips the Ansible environment setup step.
--no-deploy-prerequisites Skips the dependency installation step.
--no-install-propel Skips the Service Portal installation step.
--continue

Resumes the installation from the last failing point.

When the installation failed and you have fixed the problems, you can use this option to resume the installation.

--help Displays help information about more options for running the script.

Installation logs

The following logs are generated during the installation:

  • ansible_installation.log ( logs produced by the script that installs Ansible )
  • env_config.log ( logs actions from the script that establishes secure connection to a target host and adds it to ansible_target file )
  • ansible.log ( logs all Ansible actions)
  • ansible_script.log (logs produced by the script that installs the Service Portal dependencies)

These logs are all combined into a unified log propel_install_{timestamp}.log located in the same directory as the installation script.