We wanted to patch RHEL server through RHEL Satellite 6 however in between the RHEL server and Satellite 6 server … Linux capsule server is present …
So I wanted to know whether its supported or not. Please find below log for the same
curl: (7) Failed connect to sr01lsatellite.XXX.local:80; Connection timed out
error: skipping http://sr01lsatellite.XX.local/pub/katello-ca-consumer-latest.noarch.rpm - transfer failed
Retrieving http://sr01lsatellite.sib.local/pub/katello-ca-consumer-latest.noarch.rpm
ERROR:dbus.proxies:Introspect error on :1.6734:/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.
ERROR:subscription_manager.dbus_interface: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.
Traceback (most recent call last):
If it is supported kindly let me know if any pre-requisites required if between BigFix Endpoint – Capsule – Satellite
@MattMangan@Sujay@Chandra This is becoming an important feature request to patch RHEL systems via repositories. We know that BigFix patching process consumes a lot of time when we do the plugin based approach. Repositories are faster and customers would like to exploit the Satellite setups including Capsule + Satellite servers (kind of similar to our Relay + Server).
I’m not familiar with Capsule myself, is that some sort of proxy to Satellite?
Which log displays this info? It looks like a connection was attempted to satellite.XXX.local:80 but the traffic may be blocked or that server is down.
I don’t recognize this as a BigFix message, it’s likely you have a configuration issue on the client or Capsule/Satellite server.
Satellite Capsule server is same like Bigfix Relay. Customer have multiple locations. Main satellite server is in DR location and rest of the locations Capsule server is there. In DR location we able to patch RHEL servers because they are directly connected to satellite server. But in other locations RHEL servers connected to Capsule server. When we try to patch them it is failing stating no repository found or configured.
Do you have any idea that Capsule repositories are supported or not. And If it is supported then any documentations you can provide to configure.
You’d probably need to open a Support Incident to get in touch with the Patch team. This is honestly the first I’ve heard of Capsule.
I would suspect that it’s just a matter of setting the client to use Capsule rather than the Satellite server directly, but I couldn’t tell you what that is. If you can give the configuration steps needed to connect the client to Capsule, I could help you determine how to do that “with BigFix”.
Because our “Patch with Custom Repo” tasks generally just use YUM or DNF commands to patch, I expect it could work but again have to do whatever is needed to point your client at Capsule (and possibly register/license it?)
Here is a link that points to the RHEL Satellite & Capsule architecture.
Red Hat Satellite Capsule Server acts as a proxy for some of the main Satellite functions including repository storage, DNS, DHCP, and Puppet Master configuration. Each Satellite Server also contains integrated Capsule Server services.
@JasonWalker please do provide us your valuable guidance