Pool Member Nodes: Different Partitions, Same IP Address

Unfortunately, that is by design. A given IP address can only belong to one node in one route domain (across all partitions).

Further, a pool in one partition cannot reference a node in another (this is also true of most types of objects). The exception is the Common partition: objects in any custom partition may reference any of the objects in Common.

This means you need to move the node to Common and have your pools in WEB and APP partitions both reference the one node in the Common partition.

The supported way to do this is to delete the node from the custom partition, and recreate it again in Common. Of course, that means deleting it from all pools first, and adding it back in again afterwards. That could be quite disruptive.

A less disruptive way is to use the "experimental" mv command in tmsh. First, note the warnings on the manpage about this being an experimental command. Then enable it using the database key described on the manpage. Then, you can move your node while retaining pool memberships with, e.g.:

mv /APP/pcf-prod-gorouter1 /Common/pcf-prod-gorouter1

I have found the mv command generally reliable for node moves, except once or twice in an older version where statistics stopped updating until config reload.

In your case (loading config with the merge option) you may also need to update the config you are merging so that the pool members reference Common nodes.