#1799 AMF : csiName and csiFlags are not properly populated, during assignment removal ( proxy)

[Srikanth R]

Changeset : 7436
Setup :2N redmodel with both proxy and proxied hosted on the same node.

• Initially the proxy and proxied are in fully assigned state.
• Now perform lock operation on proxy SU, for which quiesced callback and csi removal callback is populating the csiFlags as SA_AMF_CSI_TARGET_ALL and csiName is populated as NULL. But the proxy component is having active assignments , which is to be removed according to the callback . Similar is for lock operation is on proxied SU.

So expectation is that for lock operation on either proxy / proxied SU ,csiFlags should be populated as SA_AMF_CSI_TARGET_ONE with the corresponding csi.

[Nagendra Kumar]

Performing lock on Su will result in "csiFlags value SA_AMF_TARGET_ALL in the callback". Please refer to Spec page 405:
"The Availability Management Framework should use the csiFlags value SA_AMF_TARGET_ALL in the callback of step 5 to guarantee that 2N semantics are
honored."

[Praveen]

In csi_remove callback, the argument "compName" contains the name of the component for which this callback is meant irrespective of value csi flag to be TARGET_ONE or TARTGET_ALL. In case of lock of proxy SU, compNmae should contain proxy comp name and in case of lock of Proxied SU compName should contain proxied comp name irrespective the value of csiflag(csiflag value depends on red model). If comp name is wrong wrt to name of locked SU then that is the issue.