DSU Signature verification failed

Hello,

I'm not seeing any issue.

Can you download this:

downloads.dell.com/catalog/catalog.xml.gz

Also retry periodically in DSU to download in case there was intermittent issue.

Let me know and I may have to do more research.

I'm seeing this issue again as of 2025-02-10 11:52GMT.

# dsu
DELL System Update 2.1.1.0
Copyright (C) 2014 -- 2024 DELL Proprietary.
Downloading the Index catalog
Signature verification failed for CatalogIndex.gz
Progress report is available at: /usr/libexec/dell_dup/DSU_STATUS.json
Exiting DSU!

Note that I'm _also_seeing the following:

# yum update srvadmin*
Updating Subscription Management repositories.
Error:
 Problem: package srvadmin-isvc-snmp-11.1.0.0-5761.el8.x86_64 from @System requires srvadmin-hapi = 11.1.0.0, but none of the providers can be installed
  - cannot install both srvadmin-hapi-11.3.0.0-795.el8.x86_64 from dell-system-update_dependent and srvadmin-hapi-11.1.0.0-5761.el8.x86_64 from @System
  - cannot install both srvadmin-hapi-11.3.0.0-795.el8.x86_64 from dell-system-update_dependent and srvadmin-hapi-11.1.0.0-5761.el8.x86_64 from dell-system-update_dependent
  - cannot install the best update candidate for package srvadmin-isvc-snmp-11.1.0.0-5761.el8.x86_64
  - cannot install the best update candidate for package srvadmin-hapi-11.1.0.0-5761.el8.x86_64
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Is something also wrong with the RPM repos?  Is there an incomplete updating of the mirrors for 11.3.0.0-795 packages?

Hello,

thanks for the information, it seems there are some issue on the catalogue. Can you try to download it later?

Thanks

OK, as of 15:16 it looks like things are OK with the catalog download.

Can you tell me what's going on with the OMSA repos, please?  See above for details.  It looks like potentially your mirrors aren't synced?

BenArgyle,

Unfortunatly we don't have the ability to know when or if the OpenManage group change something, but it does look like they were updating things previously, so it may have just been an issue at the time.