Ayushija/logic app stop fix #100
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
CHANGES IN LOGIC APP FOR SCHEDULED START-STOP
-- Problem: -- When we stop the VIS with infra operations first, as the underlying CS VMs are in deallocated state, the HnS shows DB as unavailable. This causes Db Stop to fail with SapDbOpsNotInExpected State
-- When Infrastructure operations are set to true for stop scenario - we are first stopping at the instance level and then will stop all the VMs
-- This is to stop the underlying CS VMs only after database instance is stopped.