After  those changes you suggested for changing the machine-id of cloned VMs and enabling the repo signing, we’ve now added a few servers as clients, gone through two package patching cycles, and have noticed that the package list for at least some clients doesn’t appear to be updating. 

I currently have nine Ubuntu 20.04 clients registered with Uyuni. Two show outstanding package updates (even though they’ve been updated from the client side with apt-get upgrade) and apt-get upgrade command shows no outstanding patches. Some of the others show no outstanding upgrades/patches from the Uyuni client pages, but an apt-get upgrade shows multiple outstanding packages.

The clients appear to be updating some info though. None show up in the Inactive systems list, and the last reboot parameter appears to be updated.
For the two where Uyuni shows updatable packages and apt reports none, the UUID in the System Info is the same for both systems. However since the Web UI reference documentation doesn’t say much about the UUID field  (beyond “The universally unique identifier”) it’s hard to tell if that’s an internal Uyuni number, or something like the machine-id  that hasn’t been properly updated .

I tried looking at the possibly relevant Troubleshooting guides but didn’t find anything that appeared relevant.  /var/log/rhn/rhn_taskomatic_daemon.log has some 401 and 403 errors that appear to be for the SLES for SAP product/channels that we haven’t started using yet. mgr-sync list credentials reports a primary credentials entry but there’s this error in the taskomatic log file
2021-02-01 00:26:08,950 [DefaultQuartzScheduler_Worker-12] WARN  com.redhat.rhn.manager.content.ContentSyncManager - Error reading UUID: /etc/zypp/credentials.d/SCCcredentials (No such file or directory)

While I don’t think that ‘s relevant to the Ubuntu package list, it’s something I’ll have to figure out fairly soon.

Cheers,

Paul-Andre

Well, it’s a definite improvement. I’ve rolled that into the template customization scripts and I can now see more than 1 system registered. Thank you.

I’m now seeing a different problem.

W: Failed to fetch https://myuniserver.mydomain:443/rhn/manager/download/dists/ubuntu-2004-amd64-main-security-uyuni/InRelease  Undetermined Error [IP: AA.BB.CC.DD 443]

If I try to go to that URL from a browser, I get

You need a token to access /manager/download/ubuntu-2004-amd64-main-security-uyuni/repodata/InRelease

The only reference I’ve found in google for that appears to be in Spanish and CentOS related on a capa9.net forum.