Make AWS/GCP HANA cluster playbook follow best practices #323
+27
−19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alvarocarvajald
force-pushed
the
aws-cluster-wait
branch
from
615a096 to
187a45d
Compare
alvarocarvajald
changed the title
In some scenarios, playbooks to configure HANA resources in a cluster are failing to deploy a healthy HanaSR cluster in AWS. This could be either due to a race condition, or to not configuring the clone resource into the cluster in maintenance mode as specified in the best practices. This commits adds into the `cluster-hana.yaml` task calls to `cs_wait_for_idle` after commands which modify the cluster configuration, as well as modifying the cluster configuration so the SAPHana resource clone is added in maintenance mode. Also calls were added to remove the maintenance flag from this resource later in the playbook.
alvarocarvajald
force-pushed
the
aws-cluster-wait
branch
from
9fc484b to
23f7d29
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In some scenarios, playbooks to configure HANA resources in a cluster are failing to deploy a healthy HanaSR cluster in AWS. This could be either due to a race condition, or to not configuring the clone resource into the cluster in maintenance mode as specified in the best practices. This commits adds into the
cluster-hana.yamltask calls tocs_wait_for_idleafter commands which modify the cluster configuration, as well as modifying the cluster configuration so the SAPHana resource clone is added in maintenance mode. Also calls were added to remove the maintenance flag from this resource later in the playbook.Ticket: https://jira.suse.com/browse/TEAM-10107
Verification Runs:
Both failures are in
registercloudgueststep registering LTSS, which is unrelated to this PR.