RMT: Unknown repository type

SUSE Linux Enterprise Server
1

Hi,

I am currently trying to revive a RMT server. I have a valid subscription, the server registered successfully against SCC. I already started from scratch, setting up rmt completely fresh, but rmt-cli mirror all results in these error messages:

W, [2025-08-07T09:30:33.282928 #12531] WARN -- : Repository 'SLE-Product-SLES15-SP6-Updates' (6298): Unknown repository type.
W, [2025-08-07T09:30:33.283110 #12531] WARN -- : Repository 'SLE-Product-SLES15-SP6-Pool' (6301): Unknown repository type.
W, [2025-08-07T09:30:33.283284 #12531] WARN -- : Repository 'SLE-Module-Basesystem15-SP6-Updates' (6345): Unknown repository type.
W, [2025-08-07T09:30:33.283569 #12531] WARN -- : Repository 'SLE-Module-Basesystem15-SP6-Pool' (6347): Unknown repository type.
W, [2025-08-07T09:30:33.283772 #12531] WARN -- : Repository 'SLE-Module-Server-Applications15-SP6-Updates' (6385): Unknown repository type.
W, [2025-08-07T09:30:33.283942 #12531] WARN -- : Repository 'SLE-Module-Server-Applications15-SP6-Pool' (6387): Unknown repository type.

The only repo getting successfully mirrored is the installer-updates repo:

I, [2025-08-07T09:28:22.514174 #12353] INFO -- : Repository SLE15-SP6-Installer-Updates wird in /usr/share/rmt/public/repo/SUSE/Updates/SLE-INSTALLER/15-SP6/x86_64/update/ gespiegelt
I, [2025-08-07T09:28:22.623953 #12353] INFO -- : → repomd.xml
I, [2025-08-07T09:28:22.839088 #12353] INFO -- : → repomd.xml.asc
I, [2025-08-07T09:28:22.839782 #12353] INFO -- : → repomd.xml.key
I, [2025-08-07T09:28:22.981950 #12353] INFO -- : ↓ e9aa8ee6f4521e4a310177883bf9ead853ad79d4fbfef41501e333342274bee1-other.xml.gz
I, [2025-08-07T09:28:22.996515 #12353] INFO -- : ↓ 83e60dc9ba574af79103fb071343b856608be6e5c30221975122f2adb140cf13-deltainfo.xml.gz
I, [2025-08-07T09:28:23.000307 #12353] INFO -- : ↓ bbe418fa355de2457f35ac272d33eb7328ed39f64e618ec99a59edb805ac0ed6-primary.xml.gz
I, [2025-08-07T09:28:23.002107 #12353] INFO -- : ↓ 4342b01536d4216240ad3e347e4ee37e9922c7c1f131354de70f0cd4b3dce2ed-filelists.xml.gz
I, [2025-08-07T09:28:23.019964 #12353] INFO -- : ↓ ae9a4837a7667f1b0133e09ecd33f86e5afc9b8043c26f5825bbbdeacff82fc4-susedata.xml.gz
I, [2025-08-07T09:28:23.029478 #12353] INFO -- : ↓ ed83148796c9db380ae82f715008389d5d36a457e5899e7405e7dc34c3d64df4-updateinfo.xml.gz

This server is behind a proxy, so I have that configured properly (otherwise the installer repo wouldn’t succeed). What else could it be? I’ve tried it in three different os versions (SP5, SP6, SP7), always the same result.

I’d appreciate any pointers!

2

“RMT: Unknown repository type” means the repo type isn’t supported or is incorrect. Check the repo type and URL.

3

How do I check the repo type that RMT is setting up on its own? I only enable a product and the corresponding repos are added automatically. I don’t even see an option to display a repo type.

4

I might have found at least a clue what might be going on here. I set up the rmt server again from scratch (purging the entire mysql DB, removing all rmt configs). The system is still successfully registered in SCC according to SUSEConnect status.
Then I finish up the rmt wizard successfully. Running rmt-cli sync -d (and a couple of debug settings in rmt.conf) reveal:

I, [2025-08-20T13:06:58.883753 #32762] INFO -- : Response: [{"id":4199508,"regcode":"{SOME_REG_CODE}","name":"{SOME_NAME}","type":"internal","status":"EXPIRED","starts_at":"2019-03-05T10:23:45.793Z","expires_at":"2023-11-03T00:00:00.000Z","system_limit":100,"systems_count":19,
…

and this contains all the old repos/information this rmt-server used to store. I must assume that the “internal” type is not supported (anymore), but this is old information anyway. Is there any way to clean this up? Apparently, this response comes from the SCC, but how can I clean that up?

5

I think I found the root cause. This system used to be registered in a different organization in SCC. After the expiration of its own subscription, I registered it with a new subscription, but this belongs to a different organization. Changing the credentials in the rmt wizard seems to be enough, I could enable a product and it currently mirrors the packages.

This thread can be considered as resolved.