Right after upgrading our Standalone Landscape Server (24.04.12) to 24.04.13 today, none of the clients that we try to register (post upgrade) are showing up in the web interface. The registration process on the client shows that the registration request was successful.
The clients are various versions of Ubuntu (20.04, 22.04, and 24.04) but all are showing the same result: Registration sent successfully, but nothing in the management console.
Has anyone else had issues with moving to 24.04.13?
The license signature verification may be failing due to some permission changes in /var/lib/landscape-server/gnupg. The following should fix that error.
sudo chown -R landscape:landscape /var/lib/landscape-server/gnupg/
sudo systemctl restart landscape-appserver
If your account has autoregistration enabled, then the clients may have silently failed to register due to the license error.
I would first confirm it in the server logs before changing more things: check /var/log/landscape-server/ and journalctl for landscape-appserver around one failed registration. If you see license/signature or GPG errors, Justin’s ownership fix is the likely one; if not, it may be a separate registration queue/API issue and the exact log line will matter.
Welcome to the Ubuntu Discourse @richardsloane
From what you’ve described, this doesn’t really look like a client-side problem or a general registration issue introduced by 24.04.13. The common denominator is the server upgrade itself, especially since 20.04, 22.04 and 24.04 clients all exhibit the exact same behaviour: registration appears successful on the client, but nothing ever reaches the web UI. I’d check the Landscape server logs before changing too much, particularly journalctl -u landscape-appserver and anything under /var/log/landscape-server/, using a fresh registration attempt as a reference point. If you see GPG, license verification or signature-related errors, @justinkim10 suggestion is probably the right fix. We’ve seen upgrades occasionally leave ownership in an unexpected state, and if /var/lib/landscape-server/gnupg is no longer accessible to the landscape user, autoregistration can fail quietly even though the client reports success. In that case, correcting the ownership and restarting landscape-appserver would be the logical next step. If the logs are clean, then I’d start looking at the registration queue or appserver/API side instead, but based on the symptoms so far, the GPG/license path seems like the most likely explanation.
The only thing I was able to find was on the client side. The machine would submit the registration request, and per the logs, would continue to try to submit it even though it had already reported that it was submitted successfully. At this time, I made the decision to roll back the server to a previous snapshot (we run our Landscape server as a VM) as I needed to get the system back up and running asap due to a security audit. But I am going to need to re-update the server again, next week, so I will follow up if the same thing happens again.
well, I concur with the suggestion replays above.
upon upgrading, the certs may have changed, so that would be the first thing I would check.
also, see if you can find the original certs and id the fingerprint of each to compare the diff, if any, just to make sure.