Description of problem: Content Hosts loses subscriptions after Vmotion and auto attach is unable to assigned the subscriptions if any other subscription is already attached to the host. Version-Release number of selected component (if applicable): 6.5 How reproducible: 100 % Steps to Reproduce: 1. Assign the SKU RH00152 (Red Hat Enterprise Linux with Smart Management for SAP Applications for Virtual Datacenters, Premium) to all the hypervisor and run auto attach on client to assign the guest SKU to the content host. 2. Once guest queue is attached to the content host, assign the MW0196814F3 (Red Hat JBoss Enterprise Application Platform, 16-Core Standard) SKU also to the content host. 3. Wait for the Vmotion. After Vmotion, auto attach is not working and guest SKU is not assigned to the content host. Actual results: Virtual datacenter subscription is not assinged to the content host and running auto attach command is also unable to assign the guest sku. Expected results: Guest SKU should be assigned to the content host even if any other subscription already attached on the content host. Additional info: If we remove the product cert 183.pem file to any other location, auto attach will work fine and Guest SKU will be attached to the content host. I have reproduce the issue with the SKU MW0150761 and RH00007
This is not a virt-who issue, as the host/guest relationship is properly established. Moving to Candlepin.
The issue appears to be between the mismatching SLAs of the SKUs in use. Auto-attach will not mix SLAs. You can mix SLAs by manually attaching subscriptions. So the first auto-attach for the guests prior to vMotion works because the SLA of the guest system is not yet established. After vMotion (and after candlepin is informed of the guest's movement), the original attachment to the premium host provided subscription is removed (because the guest is no longer on that host). An attempt is then made, using auto-attach, to fix the guest (which in the general case would attach the same guest pool provided by the new host). This does not pick up the guest pool of the new host because the only remaining attached subscription has the SLA "standard", hence the SLA of the system is viewed by auto-attach as "standard". For this to work properly you either need both of the subscriptions in use for the guest with the SLA "standard" or the SLA "premium".
Verified in Satellite 6.8 Snap 17 Followed the approximate steps in the description, substituting equvilant subscriptions. Host before auto-attach [root@guesthost ~]# subscription-manager list --consumed No consumed subscription pools to list Host after first auto-attach (Assigned guest subscription) [root@guesthost ~]# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Red Hat Enterprise Linux for Virtual Datacenters, Premium Provides: Red Hat Enterprise Linux Atomic Host ... Active: True Quantity Used: 1 Service Level: Premium Service Type: L1-L3 Status Details: Subscription is current Subscription Type: Standard Starts: 04/03/20 Ends: 04/02/21 System Type: Virtual Host after Adding self-support beta access subscription [root@guesthost ~]# subscription-manager list --consumed +-------------------------------------------+ Consumed Subscriptions +-------------------------------------------+ Subscription Name: Red Hat Enterprise Linux for Virtual Datacenters, Premium Provides: Red Hat Enterprise Linux Atomic Host ... Active: True Quantity Used: 1 Service Level: Premium Service Type: L1-L3 Status Details: Subscription is current Subscription Type: Standard Starts: 04/03/20 Ends: 04/02/21 System Type: Virtual Subscription Name: Red Hat Beta Access Provides: Red Hat Enterprise Linux for Power, little endian Beta ... Active: True Quantity Used: 1 Service Level: Self-Support Service Type: L1-L3 Status Details: Subscription is current Subscription Type: Standard Starts: 04/03/20 Ends: 04/02/21 System Type: Physical After updated report and even another sat-side auto-attach is the same as previous step. Additional client-side auto-attach retains guest subscription. [root@guesthost ~]# subscription-manager attach --auto All installed products are covered by valid entitlements. No need to update subscriptions at this time. Installed Product Current Status: Product Name: Red Hat Enterprise Linux Server Status: Subscribed
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Satellite 6.8 release), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2020:4366