can't see any ubuntu errata #8134
Comments
|
Hey @fritz0011 |
Here.... 2024/01/10 22:30:29 +02:00 Sync of channel started. For whatever reasons , the errata is not linked to the channels/packages (see above attached screenshots) |
|
more about /var/log/rhn/rhn_taskomatic_daemon-2.log:2024-01-10 22:32:08,756 [DefaultQuartzScheduler_Worker-5] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 4591-1 took 0.010669691 seconds. However....
/var/log/rhn/rhn_taskomatic_daemon-2.log:2024-01-10 22:38:59,352 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 2533-1 took 0.005662967 seconds. /var/log/rhn/rhn_taskomatic_daemon-2.log:2024-01-11 04:36:00,434 [DefaultQuartzScheduler_Worker-15] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - No deb packages to process in channels: |
|
new update: https://usn.ubuntu.com/usn-db/database.json Have a look at those 2 patches:: Patch: 4658-2 (this patch does not affect jammy, still uyuni dld this errata)
|
|
I can confirm the same behavior on Uyuni version 2024.01 |
|
I second that.
But in GUI [Software->ChannelList->All ] the 'Patches' number is always zero. It used to work in correctly in previous version . |
|
I can also confirm that it was working as of Uyuni version 2023.09. I made the jump from 2023.09 to 2024.01, so I cannot say when it broke exactly. @gabira2003 can you comment on what version it was last working for you? |
For us errata/patches feature used to work just fine in 2023.10. |
|
Okay, thanks @gabira2003, so @fritz0011 initially reported the issue on 2023.12, so it could? be safe to assume that something pushed or changed in 2023.11 may have caused the issue. My environment is mostly ubuntu 22.04 with some RHEL. I can say that the RHEL errata seems to still be working in 2024.01 |
Release 2023.11 does not exists. |
|
Correct , version 2023.12 and 2024.1 are plagued by this issue, RHEL/ORACLE are working flawless... |
|
Trying to help move this along by possibly identifying changes made to anything related to errata between Uyuni releases 2023.10 and 2023.12, as this is where the issue seems to have been introduced. 'try to download compressed ubuntu usn database' <-- looks promising 'filter errata without package matches': 'fix errata search' |
|
Any logs available? |
|
@mcalmer Could you suggest where else to look? |
|
The tomcat log config could also be in |
|
@mcalmer I see nothing in my logs (turned all the way up to debug) that indicates to me an issue with errata import failing. [DefaultQuartzScheduler_Worker-15] INFO com.redhat.rhn.taskomatic.task.ReportDbUpdateTask - Refreshing table SystemErrata took 0.002507251 seconds. But alas, no patches of any kind show (This uyuni instance has nothing but ubuntu 22.04 clients)
|
|
You need to set the UbuntuErrataManager to info loglevel. after the The job should be triggered from the reposync job when the ubuntu channel is mirrored. |
|
Thank you @mcalmer, after doing so and starting a reposync, in the /var/log/rhn/rhn_taskomatic_daemon.log I see several iterations of this as it goes through all of the errata
For fun I turned it up to debug, and caught more of the same, but no errors to report:
|
|
Maybe you just have no errata which are relevant to your system? Do you see errata when you select "All" in the left sidebar? |
I did a clean install of everything and registered a new ubuntu22 client machine |
+1 to this, as we also rely on this functionality for the same purpose |
|
For what it's worth, since this issue began we also stopped receiving Uyuni Patch Alert emails for any relevant errata. I suspect changes in 98accf1 seem to have something to do with this |
|
A fix is merged in git. Should be available with the next Uyuni release. |
|
When will a patch that fixes this problem be available? |
|
The plan is somewhen this month. |
|
This is great news, |
|
Updated to the latest release 2024.03, nothing has changed, Ubuntu patches are still not mapped to Ubuntu channels. What needs to be done to correct the situation? |
I can also confirm this, perhaps @mcalmer could comment? |
Still not working |
|
based on the feedback, I am re-opening the issue. |
|
I don't think we have a bug. Maybe it is a missunderstanding how things work. On our reference server I can mirror the channels and it also show patches available in these channels. It is correct, that these patches list binaries for Ubuntu 22. A patch will only be created in Uyuni when the packages, which fix the bug, are available. Maybe these package might be available when you mirror universe or multiverse or another not default repository. When I check what patches I have, I can see: as the latest in "Ubuntu 22.04 LTS AMD64 Main Updates for Uyuni"
I am not sure if Ubuntu remove packages when they are obsoleted by a newer version. Please check your installation and when you miss a patch, check the packages which are listed to fix the problem. |
|
The problem is that not some patches are missing, but all of them. After updating to 2023.03, all patches stopped being associated with the packages related to them. |
|
@mcalmer , maybe it helps to identify the issue ? spacecmd {SSM:0}> package_details linux-image-5.15.0-92-generic-5.15.0-92.102 File: linux-image-5.15.0-92-generic-5.15.0-92.102.amd64-deb.deb Installed Systems: 1 DescriptionSigned kernel image generic A kernel image for generic. This version Available From Channelsubuntu-2204-amd64-main-security-uyuni spacecmd {SSM:0}> repo_details "External - Ubuntu 22.04 LTS AMD64 Main Security for Uyuni" spacecmd {SSM:0}> repo_details "External - Ubuntu 22.04 LTS AMD64 Main Updates for Uyuni" According to patch database:: package size/md5sum matches in Uyuni, but still no patch associate with that package !! |
|
I updated to 2024.3 yesterday and since today at around 4 am 38 patches are shown as applicable for my old, not updated Ubuntu 20.04 machine. |
|
I think this is fixed. Remember not all updates are security updates and have an USN. |
|
Fixed after i removed all OS repos and recreated it again. |
Problem description
after the ubuntu22 channel has been defined:
errata seems to be imported , but still, no patches visible in web interface
satellite:~ # grep 6572-1 /var/log/rhn/rhn_taskomatic_daemon.log
2024-01-10 22:32:08,040 [DefaultQuartzScheduler_Worker-5] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 6572-1 took 0.002263735 seconds.
2024-01-10 22:38:34,947 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 6572-1 took 0.00213575 seconds.
Steps to reproduce
...
Uyuni version
Uyuni proxy version (if used)
No response
Useful logs
/usr/share/rhn/classes/log4j2.xml updated as following... <Logger name="com.redhat.rhn.taskomatic.SchedulerKernel" level="info" /> <Logger name="com.redhat.rhn.taskomatic.task" level="debug" /> snip <!-- this silences ehcache on Fedoras complaining about using default values --> <Logger name="org.hibernate.cache.ehcache.AbstractEhcacheRegionFactory" level="error" /> <Logger name="com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager" level="debug" /> 2024-01-10 22:38:59,291 [DefaultQuartzScheduler_Worker-13] DEBUG com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - Skipping errata without matching packages: 4714-1 2024-01-10 22:38:59,294 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 4126-1 took 0.00263124 seconds. 2024-01-10 22:38:59,321 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 4126-2 took 0.00230444 seconds. 2024-01-10 22:38:59,352 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 2533-1 took 0.005662967 seconds. 2024-01-10 22:38:59,379 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 6001-1 took 0.001427489 seconds. 2024-01-10 22:38:59,405 [DefaultQuartzScheduler_Worker-13] DEBUG com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - Skipping errata without matching packages: 3957-3 2024-01-10 22:38:59,410 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - matching packages for 3858-1 took 0.0046029 seconds. 2024-01-10 22:38:59,440 [DefaultQuartzScheduler_Worker-13] INFO com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - writing erratas to db took 64.959239509 seconds. 2024-01-10 22:38:59,499 [DefaultQuartzScheduler_Worker-13] DEBUG com.redhat.rhn.manager.content.ubuntu.UbuntuErrataManager - process Ubuntu Errata finished - done, totalMemory:998244352, freeMemory:144422432 2024-01-10 22:39:00,011 [DefaultQuartzScheduler_Worker-20] DEBUG com.redhat.rhn.taskomatic.task.SSHService - Starting run 67869 2024-01-10 22:39:00,012 [DefaultQuartzScheduler_Worker-20] DEBUG com.redhat.rhn.taskomatic.task.SSHService - Queue size (before run): 0 2024-01-10 22:39:00,016 [DefaultQuartzScheduler_Worker-2] DEBUG com.redhat.rhn.taskomatic.task.SystemOverviewUpdateQueue - Starting run 67870 2024-01-10 22:39:00,016 [DefaultQuartzScheduler_Worker-2] DEBUG com.redhat.rhn.taskomatic.task.SystemOverviewUpdateQueue - Queue size (before run): 0 2024-01-10 22:39:00,018 [DefaultQuartzScheduler_Worker-2] DEBUG com.redhat.rhn.taskomatic.task.SystemOverviewUpdateQueue - Finishing run 67870Additional information
No response
The text was updated successfully, but these errors were encountered: