Sample Pre-Check Output

The pre-check script will return output that is similar to that shown in the following table. The Error Resolution column of the table lists the most common errors encountered by each check, along with diagnosis/remediation instructions. The pre-check script will also generate the files described in Pre-Check Generated Files.

NOTE This table displays all of the tests that could be run assuming that all of the options described in Using the Pre-Check Script are used. Your output will probably not contain all of the information presented below; this is normal behavior.
NOTE The totals displayed on this page will vary by operating system and configuration.
Option Expected Result Error Resolution 
Hardware properties
 
Checking CPU count:
 
PASSED
 The host must have at least eight (8) physical CPU cores. There is no other way to remediate this issue. 
Checking memory capacity:
 
PASSED
 The host must have least 64GB of RAM. There is no other way to remediate this issue. 
Checking number of disks available:
 
PASSED
 Raw disks with no filesystem, logical volumes, or partitions are required. Use the lsblk command to verify the state of the disks before proceeding. If needed, use the --force option to install on non-raw disks. 
Total: 3 -- Failed: 0 -- Warning: 0 -- Forced(success): 0
 
Network configuration
Network port availability PASSED The script checks a number of ports. See Port Requirements and Kubernetes Port Requirements for the ports that must be available for the deployment. 
Checking primary IP address:
Using eth<number>:<ip_address> as primary interface
 
PASSED
 You may see errors if there is more than one network interface (NIC) with an assigned IP address. To resolve this, ensure that there is only one NIC with an assigned IP address. If this is not possible, add the option --controller-public-if to specify the NIC to use. 
Checking FQDN of the host:
 
PASSED

The hostname must be a Fully Qualified Domain Name (FQDN) that includes at least one "dot" (.) To fix this problem, specify a valid FQDN using the hostnamectl set-hostname command.

There is no need to reboot the Controller host; however, you will need to open a new SSH session by logging out and back in for the change take to effect.

 
Checking default gateway settings:
 
PASSED
 Use the command route -n to verify that there is only one internal gateway, which is indicated with the notation UG in the Flags column of the table returned by this command.
Checking Proxy settings PASSED Checks for environment and shell variables. 
Checking internet access:
 
PASSED
 To fix internet access problems, ensure that the proxy URL in the --proxy option is properly formatted. If needed, use the --force option to run the installer without specifying a proxy. 
Total: 5 -- Failed: 0 -- Warning: 0 -- Forced(success): 0
 
Operating system configuration
 
Checking OS type:
 
PASSED
 See Operating System Requirements. 
Checking OS Language:
 
PASSED
 The system locale must be set to US English with UTF-8 encoding. See Configuration Requirements.
Checking OS Family: PASSED See Operating System Requirements. 
Checking RHEL subscription:
 
PASSED

This test is not performed on CentOS or SLES systems, and the Total at the bottom of this section will read 11 instead of 12.

If the host is running RHEL, then a valid subscription must exist to the server RPM, the server optional RPM and the HA for server RPM channels. For example for RHEL 7, you must subscribe to the following: rhel-7-server-rpms, rhel-7-server-optional-rpms, and rhel-ha-for-rhel-7-server-rpms. If needed, use the --force option if you have either a satellite server or access to RHEL OS rpms by any other means.

 
Checking running kernel version:
 
PASSED
 The kernel version must greater or equal to the minimum version listed in OS Support. If needed, upgrade the kernel and then reboot the host. 
Checking CONFIG_SECCOMP enabled in kernel
 PASSED rhel 
Checking compatible DOCKER version
 PASSED rhel 
Checking SELinux enforcement:
 
PASSED
 SELinux is disabled does not affect HPE Ezmeral Runtime Enterprise functionality. However, if installation occurs with SELinux disabled, then you must leave SELinux disabled in order for the deployment to continue to function. Do not alter the SELinux configuration after installation. See Configuration Requirements.
Checking SELINUX policy: targeted SLES only. 
Checking IPtables/Firewalld configuration:
 
PASSED
 IPtables is disabled is a warning only. Do not change this setting after installing HPE Ezmeral Runtime Enterprise. 
Checking automount configuration:
 
PASSED
 Ensure that /etc/auto.master has only one -hosts line. If this line exists, it be the same on the Controller and all Worker hosts. 
Checking SSHD configuration:
 
PASSED

This test is not performed on RHEL systems.

  • SSHD not found: Install both openssh-server and openssh-client.
  • SSHD must be configured at boot: Ensure that SSHD starts at bootup using chkconfig.
  • SSHD must allow root login: If installing as the root user, ensure that PermitRootLogin=Yes in /etc/ssh/sshd_config.
 
Checking rsyslog setting:
 
PASSED
 Ensure that /etc/rsyslog.conf parses all /etc/rsyslog.d/*.config files, and that imuxsock is loaded in /etc/rsyslog.conf. 
Checking user and group specified:
 
PASSED
 You must specify an already available user and group when using the --user and --group options. 
Checking for krb5.keytab:
 
PASSED
 This is a warning only; however, do not kerberize the tenant storage while installing the Controller host using the web interface as described in Platform Controller Setup. Doing so will destroy any configuration you may have already done.
Checking cgconfig kernel params: PASSED
Checking compatible python version: PASSED
Checking for presence of erlang cookie PASSED 
Checking SSL server certificate and private key:
 
PASSED
 The paths specified for both the certificate and private key must be absolute paths. 
Total: 16 -- Failed: 0 -- Warning: 0 -- Forced(success): 0
 
Filesystem free space checks
 
Checking freespace on /
 
PASSED

If you are using a logical volume for the root filesystem, expand the volume and execute the resizefs command. If needed, use the --force option to ignore this failure.

CAUTION

Forcing the installation to continue might cause HPE Ezmeral Runtime Enterpriseto be unusable. 

Checking freespace on /srv:
 
PASSED

If you are using a logical volume, expand the volume and execute the resizefs command. Alternatively, you may provision another disk and use it to create a mountpoint at either /srv or /srv/HPE.

 
Checking freespace on /var:
 
PASSED

If you are using a logical volume, expand the volume and execute the resizefs command. Alternatively, you may provision another disk and use it to create a mountpoint at either /var, /var/lib or /var/lib/docker.

 
Checking freespace on /opt:
 
PASSED

If you are using a logical volume, expand the volume and execute the resizefs command. Alternatively, you may provision another disk and use it to create a mountpoint at either /opt or /opt/HPE.

 
Checking configured swap size
 
PASSED
 This is a warning only. HPE recommends a swap size that is at least 20% of Host RAM.
Checking docker storage PASSED Checks node storage. 
Total: 6 -- Failed: 0 -- Warning: 0 -- Forced(success): 0
 

***************************************************************************
     Aggregate tests summary:
        Total:           56
        Failed:           0
        Warning:          0    
        Forced(success):  0 
Additional information for debugging is written to 
/tmp/bd_prechecks.14962.log
***************************************************************************

Once you are satisfied that the pre-check has completed correctly, you may proceed to install the Controller using either of the following methods:

See Pre-Check Generated Files to view the files that are generated by the pre-check script.