22.214.171.124.26 ApiChangeResourceGroup (Opnum 25)
(Protocol Version 2) The ApiChangeResourceGroup method moves the designated resource and all the resources in its dependency tree out of its current group and into the designated group. The nonvolatile cluster state is updated to reflect this change.
The server MUST fail this method if the resource is already a member of the group designated by hGroup. In this event, the server MUST return ERROR_ALREADY_EXISTS.
The server MUST fail this method by using error ERROR_HOST_NODE_NOT_GROUP_OWNER if the group containing hResource and the destination group are not hosted on the same node.
The resource state sequence number MUST be monotonically incremented when the resource is transferred to another group.
The server MUST accept an ApiChangeResourceGroup request for processing only if it is in the read/write state, as specified in section 3.1.1.
error_status_t ApiChangeResourceGroup( [in] HRES_RPC hResource, [in] HGROUP_RPC hGroup );
Return Values: The method MUST return the following error codes for the specified conditions.
Return value/code Description
Either the hResource parameter does not represent a valid HRES_RPC context handle or the hGroup parameter does not represent a valid HGROUP_RPC context handle.
See the preceding text for when this error can occur.
The resource represented by the hResource parameter no longer exists in the nonvolatile cluster state.
The group represented by the hGroup parameter no longer exists in the nonvolatile cluster state.
See the preceding text for details of when this error can occur.
For any other condition, the server MUST set Status to a value that is not one of the values listed in the preceding table. The client MUST treat all values that are not listed in the preceding table the same, except as specified in section 126.96.36.199.