Description of problem: Guest auto attach a subpool on original host, the bonus pool still exist after it has been migrated to destination host. Version-Release number of selected component (if applicable): virt-who-0.14-8.el7.noarch subscription-manager-1.15.9-10.el7.x86_64 python-rhsm-1.15.4-5.el7.x86_64 Satellite-6.1.0-RHEL-7-20150828.0 How reproducible: Always Steps to Reproduce: 1. Register orig host, dst host and guest(on orig host) to Satellite 2. Make virt-who run at kvm mode on orig host and dst host 3. Orig host subscribe "Red Hat Enterprise Linux for Virtual Datacenters, Standard" 4. Guest auto subscribe the bonus pool which generate by Datacenter pool 5. Migrate guest to dst host. 6. Check the virt-who's log, virt-who has show the guest on dst host, meanwhile, it has removed from orig host 7. On Satellite web UI, Go to Hosts-->Content host-->Guest name --> Detail, it show guest's Virtual host is dst host 8. On Satellite web UI, Go to Hosts-->Content host-->Guest name --> Subscriptions--> List/Remove Actual results: Guest still subscribed the previous bonus pool which generate by orig host. Please see the screenshot in attachment Expected results: The bonus pool should revoke since guest has been migrated to another host. Additional info: If manual attach the same bonus pool, it hasn't this problem, the bonus pool can be removed after migration
Created attachment 1074683 [details] Guest_bonus_pool_on_satellite
Shouldn't this bug be assigned to Satellite 6 instead of virt-who? It looks like virt-who is sending correct information to the Satellite.
Ok, I think so, move it to satellite6, thanks.(In reply to Radek Novacek from comment #2) > Shouldn't this bug be assigned to Satellite 6 instead of virt-who? It looks > like virt-who is sending correct information to the Satellite.
It still exist on Satellite-6.1.0-RHEL-7-20160107.0.
Tom, Have you been able to determine if this is a Katello or Candlepin issue?
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.