on_demand sync does not populate checksums

[PaulUrwin]

Version
pulp-rpm 3.19.0
pulpcore 3.21.0

Describe the bug
After creating an rpm repository, a remote, and syncing the repository with the remote using on_demand policy, the repository content can be queried, but all the checksums are null:

{"pulp_href": "/pulp/api/v3/content/rpm/packages/fcffe954-8a73-4723-ab94-c719b60092cf/", "pulp_created": "2023-05-09T15:02:51.426326Z", "md5": null, "sha1": null, "sha224": null, "sha256": null, "sha384": null, "sha512": null, "artifact": null, "name": "zlib", "epoch": "0", "version": "1.2.11", "release": "39.el9", "arch": "i686", "pkgId": "d203e542464610e4298730c0dab5a381fd65385dc72700a0ac9d82dcd6ade387", "checksum_type": "sha256", "summary": "Compression and decompression library", "description": "Zlib is a general-purpose, patent-free, lossless data compression\nlibrary which is used by many different programs.", "url": "https://www.zlib.net/", etc etc

If you sync with an immediate policy sync, the checksums appear.

To Reproduce
Steps to reproduce the behavior:

1. create a rpm remote with on_demand policy
2. create a rpm repo
3. sync the repo using the remote
4. when the sync is complete, you will see checksums missing for packages if you query the repo content.

Expected behavior
The checksums are populated

[dralley]

It would be impossible to populate all of the checksums without downloading the content, since the metadata only contains one type of checksum. But it might be reasonable to ensure that that one checksum shows up.

Does that satisfy your needs?

[PaulUrwin]

yes that would be a reasonable solution 👍

[dralley]

Note that pkgId and checksum_type represent that very same checksum, if that is all you need.

[PaulUrwin]

Oh that is good to know.