If we create two activation keys with the same pool ids, the RHSM shows:

This consumer is already subscribed to the product matching pool with id 'XXXXX'

The system gets registered to one of the activation keys.

If our intention is to ignore one of the pool ids and subscribe only once, but assign the system to both keys, we should handle this properly in the backend code.


Steps to Reproduce:
1. create ak1 and ak2
2. assign them both a same pool id
3. register with both

$K activation_key create --name ak --environment testing --template t
$K activation_key create --name ak2 --environment testing --template t
POOLID=$($K org subscriptions --name ACME_Corporation | grep Id: | awk '{print $2}')
$K activation_key update --name ak --add_subscription $POOLID
$K activation_key update --name ak2 --add_subscription $POOLID

subscription-manager register --force --activationkey=ak,ak2 --org ACME_Corporation