Installable errata is not updated

Hi all,

I just migrate to a katello instance to install errata (previously we just
used it as a repository.
Within content host view, I can install errata correctly. Tasks tab
indicate task as finished with success, package tab is correctly updated,
but within errata tab it is still indicated as installable …

Is that a normal behavior ? If not, how should I investigate this issue ?

Regards
Yannig Rousseau

OS= Oracle Linux 6.7
package version : katello-2.4.0-7 / pulp-server-2.6.4-1 / foreman-1.10.2-1

Hi all,

In case anyone is interested.
The task which recalculate "installable errata" depending on installed
package is :
Generate applicability {"services_checked"=>…
<https://pebinvnuxapp02/foreman_tasks/tasks/727c9a0c-730e-4e62-a027-9d62a958a95c>

This task seems to be automatically launched at the end of an successfull
"Install erratum" task or when installing / removing package on
content-host manually, but it will update only for the installed / removed
package.

On my instance those task were correctly generated but failed with error

Trying to use logger katello/pulp_rest which has not been configured.

With an update of my server + a reboot, pulp seems to function better now
but I don't know what was originally the issue. If I resume one of the
failed task, it does finish correctly & update the installable errata list.

My issue now is : How to update massively for all package / content-host
(other than manually restarting "Generate applicability" tasks) ??

Regards

··· On Wednesday, 7 December 2016 11:36:03 UTC+1, yannig rousseau wrote: > > Hi all, > > I just migrate to a katello instance to install errata (previously we just > used it as a repository. > Within content host view, I can install errata correctly. Tasks tab > indicate task as finished with success, package tab is correctly updated, > but within errata tab it is still indicated as installable ... > > Is that a normal behavior ? If not, how should I investigate this issue ? > > Regards > Yannig Rousseau > > OS= Oracle Linux 6.7 > package version : katello-2.4.0-7 / pulp-server-2.6.4-1 / foreman-1.10.2-1 > > > >

What version of Katello are you running?

··· On Dec 8, 2016 5:47 AM, "yannig rousseau" wrote:

Hi all,

In case anyone is interested.
The task which recalculate “installable errata” depending on installed
package is :
Generate applicability {“services_checked”=>…
https://pebinvnuxapp02/foreman_tasks/tasks/727c9a0c-730e-4e62-a027-9d62a958a95c

This task seems to be automatically launched at the end of an successfull
"Install erratum" task or when installing / removing package on
content-host manually, but it will update only for the installed / removed
package.

On my instance those task were correctly generated but failed with error

Trying to use logger katello/pulp_rest which has not been configured.

With an update of my server + a reboot, pulp seems to function better now
but I don’t know what was originally the issue. If I resume one of the
failed task, it does finish correctly & update the installable errata list.

My issue now is : How to update massively for all package / content-host
(other than manually restarting “Generate applicability” tasks) ??

Regards

On Wednesday, 7 December 2016 11:36:03 UTC+1, yannig rousseau wrote:

Hi all,

I just migrate to a katello instance to install errata (previously we
just used it as a repository.
Within content host view, I can install errata correctly. Tasks tab
indicate task as finished with success, package tab is correctly updated,
but within errata tab it is still indicated as installable …

Is that a normal behavior ? If not, how should I investigate this issue ?

Regards
Yannig Rousseau

OS= Oracle Linux 6.7
package version : katello-2.4.0-7 / pulp-server-2.6.4-1 / foreman-1.10.2-1


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.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

The upgrade was from version 2.4.0-7 to 2.4.1-1

··· On Thursday, 8 December 2016 14:04:22 UTC+1, Eric Helms wrote: > > What version of Katello are you running? > > On Dec 8, 2016 5:47 AM, "yannig rousseau" > wrote: > >> Hi all, >> >> In case anyone is interested. >> The task which recalculate "installable errata" depending on installed >> package is : >> *Generate applicability {"services_checked"=>... >> * >> This task seems to be automatically launched at the end of an successfull >> "Install erratum" task or when installing / removing package on >> content-host manually, but it will update only for the installed / removed >> package. >> >> On my instance those task were correctly generated but failed with error >> >> Trying to use logger katello/pulp_rest which has not been configured. >> >> >> With an update of my server + a reboot, pulp seems to function better now >> but I don't know what was originally the issue. If I resume one of the >> failed task, it does finish correctly & update the installable errata list. >> >> My issue now is : How to update massively for all package / content-host >> (other than manually restarting "Generate applicability" tasks) ?? >> >> Regards >> >> On Wednesday, 7 December 2016 11:36:03 UTC+1, yannig rousseau wrote: >>> >>> Hi all, >>> >>> I just migrate to a katello instance to install errata (previously we >>> just used it as a repository. >>> Within content host view, I can install errata correctly. Tasks tab >>> indicate task as finished with success, package tab is correctly updated, >>> but within errata tab it is still indicated as installable ... >>> >>> Is that a normal behavior ? If not, how should I investigate this issue ? >>> >>> Regards >>> Yannig Rousseau >>> >>> OS= Oracle Linux 6.7 >>> package version : katello-2.4.0-7 / pulp-server-2.6.4-1 / >>> foreman-1.10.2-1 >>> >>> >>> >>> -- >> 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-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/d/optout. >> >