You're mostly correct in your assumptions. I'll answer each one separately below.
> gofer is only used to install/update/remove remote packages (on clients) and is not involved at all
Correct. Although gofer is also used in capsule syncs.
> katello-agent is uploading the list of rpms installed to katello
That is accomplished by katello-package-upload.
>katello is pulling pulp repos periodically (by magic?) and gets the errata for that repo
This only happens periodically if a sync plan has been created. The updates to the repos (i.e. new errata) happens only when the repo is synced either manually or by a sync plan.
If you registered your system and then added the subscription in the UI you will also need to do this on the client:
> katello is comparing the errata with consumer packages
Correct.
Please let me know if you have any other questions.
Thanks,
Walden
···
----- Original Message -----
From: "Cristian Falcas"
To: foreman-users@googlegroups.com
Sent: Tuesday, September 1, 2015 6:34:20 AM
Subject: [foreman-users] How is errata generated in katello?
Hello,
I’m trying to understand how katello-agent, client gofer, pulp and katello
are connected in order to generate the “Installable Errata” tab.
What I presume is happening:
gofer is only used to install/update/remove remote packages (on clients)
and is not involved at all
katello-agent is uploading the list of rpms installed to katello
katello is pulling pulp repos periodically (by magic?) and gets the
errata for that repo
katello is comparing the errata with consumer packages
Can someone give me some more information about the flow?
You're mostly correct in your assumptions. I'll answer each one separately
below.
> gofer is only used to install/update/remove remote packages (on clients)
and is not involved at all
Correct. Although gofer is also used in capsule syncs.
> katello-agent is uploading the list of rpms installed to katello
That is accomplished by katello-package-upload.
>katello is pulling pulp repos periodically (by magic?) and gets the errata
for that repo
This only happens periodically if a sync plan has been created. The
updates to the repos (i.e. new errata) happens only when the repo is synced
either manually or by a sync plan.
If you registered your system and then added the subscription in the UI you
will also need to do this on the client:
> katello is comparing the errata with consumer packages
Correct.
Please let me know if you have any other questions.
Thanks,
Walden
···
On Tuesday, September 1, 2015 at 6:34:42 AM UTC-4, Cristian Falcas wrote:
>
> Hello,
>
> I'm trying to understand how katello-agent, client gofer, pulp and katello
> are connected in order to generate the "Installable Errata" tab.
>
> What I presume is happening:
> - gofer is only used to install/update/remove remote packages (on clients)
> and is not involved at all
> - katello-agent is uploading the list of rpms installed to katello
> - katello is pulling pulp repos periodically (by magic?) and gets the
> errata for that repo
> - katello is comparing the errata with consumer packages
>
> Can someone give me some more information about the flow?
>
> Thank you,
> Cristian Falcas
>
>
I recently started using Katello and "pushing" updates with katello-agent
and have a few follow-on questions:
a) How does Katello "tell" the content host to perform its update? The only
firewall configuration is on the Katello server which implies the
katello-agent/gofer is actually checking in at some regular interval,
correct? Where is this interval defined?
b) I performed an update through the Katello console but then rolled the
yum transaction back locally on the content host. Now the Katello console
shows the errata as having been applied and no longer applicable. How do I
"re-scan" so that Katello is aware that the updates are no longer applied
to the system and need to show as such?
···
On Tuesday, September 1, 2015 at 5:34:42 AM UTC-5, Cristian Falcas wrote:
>
> Hello,
>
> I'm trying to understand how katello-agent, client gofer, pulp and katello
> are connected in order to generate the "Installable Errata" tab.
>
> What I presume is happening:
> - gofer is only used to install/update/remove remote packages (on clients)
> and is not involved at all
> - katello-agent is uploading the list of rpms installed to katello
> - katello is pulling pulp repos periodically (by magic?) and gets the
> errata for that repo
> - katello is comparing the errata with consumer packages
>
> Can someone give me some more information about the flow?
>
> Thank you,
> Cristian Falcas
>
>
>
> Hey Cristian,
>
> You're mostly correct in your assumptions. I'll answer each one
separately below.
>
>
> > gofer is only used to install/update/remove remote packages (on
clients) and is not involved at all
>
> Correct. Although gofer is also used in capsule syncs.
>
>
> > katello-agent is uploading the list of rpms installed to katello
>
> That is accomplished by katello-package-upload.
>
>
> >katello is pulling pulp repos periodically (by magic?) and gets the
errata for that repo
Some clarification, Katello does not pull repositories from Pulp. Katello
can initiate a sync of external repositories that are pulled down into
Pulp. Along the way, Katello will index in its database the content (e.g.
errata, packages) but not all attributes.
>
> This only happens periodically if a sync plan has been created. The
updates to the repos (i.e. new errata) happens only when the repo is synced
either manually or by a sync plan.
>
> If you registered your system and then added the subscription in the UI
you will also need to do this on the client:
>
> sudo subscription-manager refresh; sudo yum repolist; sudo
katello-package-upload
>
>
> > katello is comparing the errata with consumer packages
>
> Correct.
>
> Please let me know if you have any other questions.
>
> Thanks,
> Walden
>
>
>
>>
>> Hello,
>>
>> I'm trying to understand how katello-agent, client gofer, pulp and
katello are connected in order to generate the "Installable Errata" tab.
>>
>> What I presume is happening:
>> - gofer is only used to install/update/remove remote packages (on
clients) and is not involved at all
>> - katello-agent is uploading the list of rpms installed to katello
>> - katello is pulling pulp repos periodically (by magic?) and gets the
errata for that repo
>> - katello is comparing the errata with consumer packages
All errata applicability calculations are handled by Pulp. Katello
determines installability by determining if an applicable errata is present
in the content view and environment that the host is attached to.
Eric
>>
>> Can someone give me some more information about the flow?
>>
>> Thank you,
>> Cristian Falcas
>>
> –
> You received this message because you are subscribed to the Google Groups
"Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
···
On Sep 2, 2015 1:23 PM, wrote:
> On Tuesday, September 1, 2015 at 6:34:42 AM UTC-4, Cristian Falcas wrote:
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
> I recently started using Katello and "pushing" updates with
> katello-agent and have a few follow-on questions:
> a) How does Katello "tell" the content host to perform its update? The
> only firewall configuration is on the Katello server which implies the
> katello-agent/gofer is actually checking in at some regular interval,
> correct? Where is this interval defined?
Today, the message is sent over ampq. The gofer agent polls the broker
to get the command. Ideally, long term, this would be replaced by remote
execution.
> b) I performed an update through the Katello console but then rolled the
> yum transaction back locally on the content host. Now the Katello
> console shows the errata as having been applied and no longer
> applicable. How do I "re-scan" so that Katello is aware that the updates
> are no longer applied to the system and need to show as such?
Was the package profile sent back up from the system to katello?
Regarding point a: goferis connected to qpid from where it takes the
commands. So you don't have to open any ports.
···
On Thu, Nov 5, 2015 at 9:49 PM, Lesley Kimmel wrote:
I recently started using Katello and “pushing” updates with katello-agent
and have a few follow-on questions:
a) How does Katello “tell” the content host to perform its update? The
only firewall configuration is on the Katello server which implies the
katello-agent/gofer is actually checking in at some regular interval,
correct? Where is this interval defined?
b) I performed an update through the Katello console but then rolled the
yum transaction back locally on the content host. Now the Katello console
shows the errata as having been applied and no longer applicable. How do I
"re-scan" so that Katello is aware that the updates are no longer applied
to the system and need to show as such?
On Tuesday, September 1, 2015 at 5:34:42 AM UTC-5, Cristian Falcas wrote:
Hello,
I’m trying to understand how katello-agent, client gofer, pulp and
katello are connected in order to generate the “Installable Errata” tab.
What I presume is happening:
gofer is only used to install/update/remove remote packages (on
clients) and is not involved at all
katello-agent is uploading the list of rpms installed to katello
katello is pulling pulp repos periodically (by magic?) and gets the
errata for that repo
katello is comparing the errata with consumer packages
Can someone give me some more information about the flow?
Thanks for your reply. Regarding your question: "Was the package profile
sent back up from the system to katello?" It doesn't appear so, that's what
I'm trying to figure out is how to trigger that action manually (if
possible). This seems like something akin to the rhn_check utility.
···
On Fri, Nov 6, 2015 at 7:13 AM, Bryan Kearney wrote:
On 11/05/2015 02:49 PM, Lesley Kimmel wrote:
I recently started using Katello and “pushing” updates with
katello-agent and have a few follow-on questions:
a) How does Katello “tell” the content host to perform its update? The
only firewall configuration is on the Katello server which implies the
katello-agent/gofer is actually checking in at some regular interval,
correct? Where is this interval defined?
Today, the message is sent over ampq. The gofer agent polls the broker to
get the command. Ideally, long term, this would be replaced by remote
execution.
b) I performed an update through the Katello console but then rolled the
yum transaction back locally on the content host. Now the Katello
console shows the errata as having been applied and no longer
applicable. How do I “re-scan” so that Katello is aware that the updates
are no longer applied to the system and need to show as such?
Was the package profile sent back up from the system to katello?
