Description of problem:
Version-Release number of selected component (if applicable):
How reproducible: Follow the below link
Actual results: At step 4.6.2 there is an addition of a colocation constraint only
[root]# pcs constraint colocation add vip_RH2_02 with master SAPHana_RH2_02-master 2000
Expected results as mentioned by the customer: There should also be an additional order constraint to ensure that the virtual IP address is only activated after the HANA database instance is up and running again.
After a takeover, the virtual IP address should only be activated again after the database is operational again.
Similarly, when performing a takeover and the source system is still up and running, the first action should be to deactivate the virtual IP address before starting the HANA takeover operation.
Additional info: The RFE is opened for the engineering team to check if it would be OK to modify the document with the addtion of the appropriate order constraint for the VIP.
Fabio, does this sound correct?
Closing this bug, since the support case that led to its creation has been closed and there was never any feedback from the original requestor on the support case for the additional information we asked for.