Hi,
Thanks for clearifying then I don’t need to feel that guilty for asking about Satellite 6.
Before we switched to hypervisor based subscriptions in our vmware setup the playbook worked with the same configuration as remix_tj suggests but we didn’t use the “force_register: yes” part.
Now we have a few different vmware clusters and all of the hypervisors in every cluster have valid subscriptions to Red Hat (Red Hat Enterprise Linux with Smart Virtualization and Management, Premium (2-sockets)).
There is a green check mark in Satellite 6 GUI for all hypervisors. Virt-who is set up according to Red Hat documentation.
The playbook that worked for “fixed” subscriptions now fails with error something like “Not valid subscription for all installed products”.
Today we manually registered five servers all following the same steps as below:
- rpm -Uvh https:///pub/katello-ca-consumer-latest.noarch.rpm
- subscription-manager register --org="<Customer Org" --activationkey=“AK-RHEL8”
- subscription-manager attach --auto
** (Possibly related error message pasted below)
Now when running “subscription-manager status” we get:
[root@rhel8_clientname ~]# subscription-manager status
±------------------------------------------+
System Status Details
±------------------------------------------+
Overall Status: Insufficient
Red Hat Enterprise Linux with Smart Virtualization and Management, Premium (2-sockets):
System Purpose Status: Not Specified
-
At Satellite 6 server: “systemctl restart virt-who”
-
Back at client: subscription-manager attach --auto
[root@rhel8_clientname ~]# subscription-manager status
±------------------------------------------+
System Status Details
±------------------------------------------+
Overall Status: Current
System Purpose Status: Not Specified
Now client is registered and got a green check box in Satellite 6 GUI. After step 3) it has orange exclamation mark saying something like “Invalid”
Question is. How can I do these steps from ansible or can someone help me figure out if there is some misconfiguration on my part. The Activation key for example. What subscriptions should I add to that? Not the “Red Hat Enterprise Linux with Smart Virtualization and Management, Premium (2-sockets) 45 of 87” since that is for hypervisors. There is also the option to add one of several similar subscriptions saying something like “Red Hat Enterprise Linux with Smart Virtualization and Management, Premium (2-sockets) 2 of Unlimited” but that must be one per hypervisor I guess and I don’t know what hypervisor my host will end up on when running my vmware_guest module agains the vCenter API.
** There is also a strange error message when trying the first “subscription-manager attach --auto” in step 3) above. Don’t remember if it came at all five servers but at least at more than one:
ERROR:dbus.proxies:Introspect error on :1.302:/EntitlementStatus: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken
Could this indicate that there are some firewall or SElinux related issues to consider or how do I configure the message bus security policy?
(I can add that the redhat_subscription module in the playbook was before some security patches applied later in the playbook but for these five servers we commented out the satellite registration to do it manually after the playbook was run. So it’s possible that the security tasks in the playbook (not written by me, just included) tweaks something with message bus config. Then the dbus policy will be tweaked after the registration once I get the registration done as planned.)
As before, grateful for any help.
Regards,
/Fredrik