Chapter 4. Known Issues

The roles can run in an assert mode, in which case they do not modify managed nodes but report the compliance of a node with the applicable SAP notes. When running assert mode playbooks with previous versions (1.x or 2.x) of the roles, assert parameters are ignored, causing the roles to modify the managed nodes instead of only checking them. As roles can also be installed in other than the default locations (e.g. using git), it is recommended that you not only check if version 3 of package rhel-system-roles-sap is installed but also that the playbooks you are using are calling the roles in their correct, default locations, which is under /usr/share/ansible/roles.

In case there is no DNS domain set on the managed node, which is typically the case on cloud systems, the role sap-preconfigure will fail in task Verify that the DNS domain is set. To avoid this, set variable sap_domain in file /usr/share/ansible/roles/sap-preconfigure/defaults/main.yml or run the ansible-playbook command with line parameter -e "sap_domain=example.com" (with the domain name being example.com in this case - please replace it by your domain name).

(sap-preconfigure issue 32)

When running role sap-hana-preconfigure in assert mode against a x86_64 managed node, it might incorrectly report that the current status of the CPU Governor for performance is not as expected.

(sap-hana-preconfigure issue 180)