generate updateinfo.xml using Generate_updateinfo.py and 2.I think the example given at is overly complicated. Of course this script relies on the great work done by “ ”) So it looks like Pulp is using PostgreSQL for repo metadata instead of MongoDB but pulp-admin is still using the MongoDB backend. Pulpcore=# select pulp_id, name from core_repository The singular repo I saw from pulp repo list is found in mongodb: tools]# mongoĪnd the actual Yum repos are stored in PostgreSQL: tools]# su - ~]$ psql pulpcore This does indeed look like a switch from MongoDB to PostgreSQL, probably as a result of the Pulp2 → Pulp3 update. I would expect “pulp-admin repo list” to list the yum repos I have already created and synced through the web ui or hammer. Pulp-admin is being authenticated through the $HOME/.pulp/nf configuration file.

I don’t know if that’s intented behaviour, but all of the online documentation I’ve found for importing CentOS errata into Foreman seem to expect “pulp-admin list repo” to actually list those repos.

Then, after I create and publish a content view “pulp-admin repo list” shows a single tools]# pulp-admin repo list I do however see them via “hammer repository list”

I don’t see any yum repos via “pulp-admin repo list” after creating a product for CentOS-7 and setting up the “base” and “updates” yum repos.

Postgresql yum repo