Collect and verify role flavors.
This validation checks the flavors assigned to roles exist and have the correct capabilities set.
Role documentation
RHEL8.x kernel flag for Compute nodes validation.
RHEL-8.3 kernel disabled the Intel TSX (Transactional Synchronization Extensions) feature by default as a preemptive security measure, but it breaks live migration from RHEL-7.9 (or even RHEL-8.1 or RHEL-8.2) to RHEL-8.3.
Operators are expected to explicitly define the TSX flag in their KernelArgs for the compute role to prevent live-migration issues during the upgrade process.
This also impacts upstream CentOS systems.
Role documentation
Ensure container status.
Detect failed containers and raise an error.
Role documentation
Verify docker containers are up and ports are open.
Ensure relevant docker containers are up and running, with ports open to listen. We iterate through a list of container names and ports provided in defaults, and ensure the system has those available.
Role documentation
Verify image-serve service is working and answering.
Ensures image-serve vhost is configured and httpd is running.
Role documentation
Check Ironic boot configuration.
Check if baremetal boot configuration is correct.
Role documentation
Node health check.
Check if all overcloud nodes can be connected to before starting a scale-up or an upgrade.
Role documentation
Check correctness of installed nova-libvirt version.
Detect if installed nova-libvirt satisfies constraints.
Role documentation
Nova Status Upgrade Check.
Performs a release-specific readiness check before restarting services with new code. This command expects to have complete configuration and access to databases and services within a cell. For example, this check may query the Nova API database and one or more cell databases. It may also make requests to other services such as the Placement REST API via the Keystone service catalog The nova-status upgrade check command has three standard return codes: 0 -> All upgrade readiness checks passed successfully and there is nothing to do. 1 -> At least one check encountered an issue and requires further investigation. This is considered a warning but the upgrade may be OK. 2 -> There was an upgrade status check failure that needs to be investigated. This should be considered something that stops an upgrade.
Role documentation
Check connectivity to various OpenStack services.
This validation gets the PublicVip address from the deployment and tries to access Horizon and get a Keystone token.
Role documentation
Check correctness of current repositories.
Detect whether the repositories listed in yum repolist can be connected to and that there is at least one repo configured. Detect if there are any unwanted repositories (such as EPEL) enabled.
Role documentation
Stack Health Check.
Check if all stack resources are in a ‘COMPLETE’ state before starting an upgrade.
Role documentation
System encoding.
Ensure the local is unicode
Role documentation
Check if latest version of TripleO packages is installed.
Make sure a list of TripleO packages are at its latest version before starting an upgrade.
Role documentation
Verify undercloud services state before running update or upgrade.
Check undercloud status before running a stack update - especially minor update and major upgrade.
Role documentation
Verify undercloud fits the disk space requirements to perform an upgrade.
Make sure that the root partition on the undercloud node has enough free space before starting an upgrade http://tripleo.org/install/environments/baremetal.html#minimum-system-requirements
Role documentation
Verify heat-manage purge_deleted is enabled in crontab.
Without a purge_deleted crontab enabled, the heat database can grow very large. This validation checks that the purge_deleted crontab has been set up.
Role documentation
Verify that the IPA server has the right permissions and ACI.
This validation is relevant for systems where TLS Everywhere is enabled.
A new ACI is needed on the FreeIPA server to ensure that certificates with IP SANs can be issued. This ACI will be delivered by default from FreeIPA 4.8.5.
In addition, a new permission is needed to add DNS zones for tripleo-ipa. This permission is an addition to the current permissions for the Nova Host Manager role.
This validation confirms that the new permission and ACI are present.
https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/features/tls-introduction.html
Role documentation
Verify undercloud services state before running update or upgrade.
Check undercloud status before running a stack update - especially minor update and major upgrade.
Role documentation
Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License. See all OpenStack Legal Documents.