We have an unusual behavior on our Landscape On Premises “23.03 (installed)”, and since I don’t have any error messages, I can’t locate the problem either.
I followed the instructions at https://ubuntu.com/landscape/docs/repositories, which are also published in the first post here.
Roughly:
Created the gpg key and then:
landscape-api import-gpg-key mirror-key mirror-key.asc --json
landscape-api create-distribution ubuntu
landscape-api create-series jammy ubuntu --pockets security --components main --architectures amd64 --gpg-key mirror-key --mirror-uri http://archive.ubuntu.com/ubuntu/
landscape-api sync-mirror-pocket security jammy ubuntu
… all of this worked without errors, and after hours, the “download” was finished. I could then also update test clients using this repository. After a project break, weeks later, I wanted to add “restricted” to “main” and executed:
landscape-api edit-pocket security jammy ubuntu --components main,restricted --mirror-suite jammy
landscape-api sync-mirror-pocket security jammy ubuntu
Here there was a longer loading process. But then, after the sync was completed, I wanted to update the test client again, but the test client reported “All packages are up to date” after an “apt update”.
This surprised me, as weeks had passed, the repository was freshly synchronized, and “unattended upgrades” was deactivated on the test client. I would have expected updates to be found.
Again weeks later, I repeated this:
landscape-api sync-mirror-pocket security jammy ubuntu
And noticed that there was no real loading process, the status went from ‘“progress”: 0’ to ‘“progress”: 100’ and ‘“activity_status”: “succeeded”’ in seconds, and the test client again had the output “All packages are up to date” after an “apt update”. Here’s the complete output from sync-mirror-pocket via “landscape-api get-activities”:
[
{
"id": 378,
"creation_time": "2024-05-17T08:54:01Z",
"creator": {
"name": "xxx",
"email": "xxx@xxx.xxx",
"id": 1
},
"type": "SyncPocketRequest",
"summary": "Sync pocket 'security' of series 'jammy' in distribution 'ubuntu'",
"result_text": "Repository sync completed",
"pocket_id": 1,
"pocket_name": "security",
"progress": 100,
"parent_id": 377,
"modification_time": "2024-05-17T08:54:03Z",
"completion_time": "2024-05-17T08:54:03Z",
"schedule_before_time": null,
"schedule_after_time": null,
"result_code": 0,
"activity_status": "succeeded",
"children": []
}
]
I have the same behavior with the “focal” series. Did I misunderstand something? Does “sync-mirror-pocket” not cause an update of the repository? I don’t get any errors, and all sync attempts are also green (activity finished successfully) under “https://mydomain.com/account/standalone/activities”. What could be the cause? In which exact logs could I look?
Note:
The goal of this on-premises repository is to be able to provide our Ubuntu hosts with security updates.