I suspect that the cause for the generation of the second sub-pool occurred when the host system made two seperate bind transactions either on the same multi-entitlement physical instance-based pool or a second bind on a second physical instance-based pool.

Is this what happened?

Configured facts for 22 socket and autosubscribed , so its consumed quantity from both the "instanced based subscription pool "

(In reply to comment #2)
> Configured facts for 22 socket and autosubscribed , so its consumed quantity
> from both the "instanced based subscription pool "

for above comment i am using physical6.4 machine

There's a lot to consider here.

If this was two separate entitlements from one pool, you would probably incorrectly get two sub-pools. There should be only one, but of course if we skip the bonus pool when the second bind is done, and then the first entitlement is revoked, there will be no bonus pool, despite the second entitlement existing. That might be a reasonable side effect though, the workaround being you just remove the entitlement and re-attach to get your sub-pool back.

If however as Sachin is stating in comment #2 these came from *two separate pools*, then I'm not even sure what should happen. If you're crossing subscriptions, should there be two sub-pools? Will take this question to PM.

*** Bug 964121 has been marked as a duplicate of this bug. ***

We need a new sub-pool implementation, one sub-pool per stack, disappears when the last ent in the stack is gone. Moved to backlog, will be a pretty substantial change.

This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Not a client bug, re-aligning to Sat 6 + Candlepin and SAM 1.3 tracker, as we need this for 1.3 release.

moving to NEW to get it looked at.

This has been addressed as part of the One Sub Pool Per Stack implementation.

It is available in:
  candlepin-0.8.21-1

GitHub Pull Request: https://github.com/candlepin/candlepin/pull/345

Commit: feca66fcecadd5248fc6ab06411b7927cec01f2d

Lates build (Snap4) should contain these fixes. Please test on Snap4.

Moving this to be tested during MDP3, not critical for MDP2 success story

please provide verification steps

Quite tricky to describe this one but here we go.

Essentially you need to locate at least one pool with product attributes virt_limit and stacking_id. Ideally you would find two separate pools with the same stacking_id, but one will do so long as it has some quantity available. (more than 1)

Here is how I lookup pools and their attributes:

Lookup my production owner ID:

curl -k -u rhn-engineering-dgoodwin:password https://subscription.rhn.redhat.com/subscription/users/rhn-engineering-dgoodwin/owners

Now lookup all pools for my owner ID:

curl -k -u rhn-engineering-dgoodwin:password https://subscription.rhn.redhat.com/subscription/owners/5894300/pools | python -mjson.tool | less

In this list, look for pools with productAttributes virt_limit and stacking_id. Once found, these are the pools you need to add to your distributor/subscription-management application and export a manifest for. Export quantity 10 or so to be safe.

Import the manifest in Satellite. Now we need to register a virt host, and assign it *two separate entitlements*. If you exported just one pool, give the host two separate entitlements from that pool, i.e. quantity 5 and quantity 5.

Now you need a guest, running on that host. There are ways to fake this if needed just let us know.

Register the guest, make sure the virt host/guest mapping is established, and list available pools for the guest. You should see *just one* virtual sub-pool, even though we gave the host two separate entitlements.

Moving to 6.0.4 for verification

VERIFIED

a  single virtual sub-pool seen even if two separate entitlements
to host is assigned

This was delivered with Satellite 6.0 which was released on 10 September 2014.