sap_hana_preconfigure: Be less restrictive with new RHEL versions #511
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solves issue #500.
The new behavior if a system is running a RHEL version which is not in the list
sap_hana_preconfigure_supported_rhel_minor_releases
is as follows:role running in normal mode:
a.
sap_hana_preconfigure_min_rhel_release_check: false
(default)The debug task
Report if the system is running a RHEL release which is supported for SAP HANA
displays a warning message.b.
sap_hana_preconfigure_min_rhel_release_check: true
The assert task
Fail if the system is running a RHEL release which may not be supported for SAP HANA
fails with a failure message.role running in assert mode,
sap_hana_preconfigure_assert: true
:a.
sap_hana_preconfigure_min_rhel_release_check: false
(default)The assert task
Report if the RHEL release is supported for SAP HANA
displays a warning message but the warning(error) is always ignored, so the playbook continues.b.
sap_hana_preconfigure_min_rhel_release_check: true
The assert task
Assert that the system is running a RHEL release which is supported for SAP HANA
fails with a failure message.