[Spacewalk-list] [EXTERNAL EMAIL] Packages listed as available to update, but no update done (Appstream/module issue for redhat8?)

[Simon Avery]

Hello Kent

We too have encountered several rounds of difficulties with Centos 8 since 8.1 was released, despite not having specifically used modules on any of the target systems.

Summary:
8.0 repo fails with various module related issues (since master repo updated this to link to 8.1/). Additionally, manual yum update on clients whose repos were managed by spwk fails.
8.1 Repo worked for a bit when added explicitly (rather than /8/ whose symlinked changed on the master repo), but has since triggered other issues (earlier reported in here)

Our current workaround is to remove Centos 8 clients from Spacewalk repos by assigning them the channel 'None' and for regular patching, I'm using spacecmd to schedule the remote command "yum -y update".

Cons: We don't get to see patches/errata before they're applied. We're using more bandwidth through not using spacewalk's local mirror. (Although it's off peak so impact is low)

Pros: We do get some post-update logs via spacewalk through the event histories per machine, which is useful.

I echo Stefan's suggestion that someone please fix spacewalk to deal with modules properly. (Sadly I don't have these skills myself!)  I'm not ready to leave Spacewalk behind...

S


From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> On Behalf Of Brodie, Kent
Sent: 19 February 2020 16:19
To: spacewalk-list at redhat.com
Subject: [EXTERNAL EMAIL] [Spacewalk-list] Packages listed as available to update, but no update done (Appstream/module issue for redhat8?)

Hi- I am testing a couple of version 8 clients for spacewalk (One redhat8, one centos8).

I have a server for each OS doing a full reposync, then I sync the repositories into spacewalk.
No problems so far.

Everything pretty much works great EXCEPT for each of those 2 clients, I have about 16 packages that are listed in Spacewalk as being new versions that can be updated.

But when I try to update those clients, nothing. "No updates available".

I am pretty sure this is related to the new redhat appstream/module functionality.  And I'm guessing that those 16 packages can't actually be upgraded YET because of a module version limitation of something installed on those clients.    (I confirmed this more or less by eliminating spacewalk....   And just using centos/redhat repos.   Same answer:  no updates available).

BUT...  my question is this:     How can I tweak spacewalk (or my repos) so that the Spacewalk doesn't show update packages that I actually can't install?   In other words, those 2 clients should NOT show any updates available to install.......

Is this spacewalk essentially not knowing how to handle modules/appstreams yet?

Thanks for any tips/pointers

-kcb
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20200220/f11e7699/attachment.htm>