View Issue Details

IDProjectCategoryView StatusLast Update
0000158AlmaLinux-8dnfpublic2021-11-23 19:06
Reporterjuliogonzalez Assigned Toalukoshko  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Summary0000158: Triplicate repository IDs at almalinux-resilientstorage.repo
DescriptionIt seems the file contains three repositories sharing the same ID `resilientstorage`.

The problem is that the source and debuginfo repositories did not get the right suffixes `-source` and `-debuginfo` for the ID, as it happens in other cases, such as as `powertools`

As a result, dnf considers only the last ID (debuginfos), if the three repositories are enabled. Also, some tools (such as salt) will exit with an error telling that there are duplicated IDs.
Steps To Reproduce[[email protected] yum.repos.d]# sed -i -e 's/enabled=0/enabled=1/g' /etc/yum.repos.d/almalinux-resilientstorage.repo

[[email protected] yum.repos.d]# dnf refresh
No such command: refresh. Please use /usr/bin/dnf --help
It could be a DNF plugin command, try: "dnf install 'dnf-command(refresh)'"
[[email protected] yum.repos.d]# dnf search resilient
AlmaLinux 8 - BaseOS 4.2 MB/s | 3.8 MB 00:00
AlmaLinux 8 - AppStream 8.5 MB/s | 8.2 MB 00:00
AlmaLinux 8 - Extras 19 kB/s | 12 kB 00:00
AlmaLinux 8 - ResilientStorage debuginfo 28 kB/s | 19 kB 00:00
No matches found
Additional InformationIf the IDs are fixed, dnf works as expected:

[[email protected] yum.repos.d]# cat /etc/yum.repos.d/almalinux-resilientstorage.repo
# almalinux-resilientstorage.repo

[resilientstorage]
name=AlmaLinux $releasever - ResilientStorage
mirrorlist=https://mirrors.almalinux.org/mirrorlist/$releasever/resilientstorage
# baseurl=https://repo.almalinux.org/almalinux/$releasever/ResilientStorage/$basearch/os/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux

## Sources
[resilientstorage-source]
name=AlmaLinux $releasever - ResilientStorage Source
mirrorlist=https://mirrors.almalinux.org/mirrorlist/$releasever/resilientstorage-source
# baseurl=https://repo.almalinux.org/almalinux/$releasever/ResilientStorage/Source/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux

## Debuginfo
[resilientstorage-debuginfo]
name=AlmaLinux $releasever - ResilientStorage debuginfo
mirrorlist=https://mirrors.almalinux.org/mirrorlist/$releasever/resilientstorage-debuginfo
# baseurl=https://repo.almalinux.org/almalinux/$releasever/ResilientStorage/debug/$basearch/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-AlmaLinux

[[email protected] yum.repos.d]# dnf search resilient
AlmaLinux 8 - BaseOS 4.0 MB/s | 3.8 MB 00:00
AlmaLinux 8 - AppStream 7.8 MB/s | 8.2 MB 00:01
AlmaLinux 8 - Extras 20 kB/s | 12 kB 00:00
AlmaLinux 8 - ResilientStorage 683 kB/s | 405 kB 00:00
AlmaLinux 8 - ResilientStorage Source 19 kB/s | 11 kB 00:00
AlmaLinux 8 - ResilientStorage debuginfo 32 kB/s | 19 kB 00:00
No matches found.
TagsNo tags attached.
abrt_hash
URL

Activities

juliogonzalez

2021-11-23 09:58

reporter   ~0000421

I was trying to create a fix myself. Assumed https://git.almalinux.org/rpms/almalinux-release is the right repository, but it seems the last commit there is for 8.4, while this problem started with 8.5

Is that the right repository, or should I be looking somewhere else?

alukoshko

2021-11-23 13:45

developer   ~0000422

Last edited: 2021-11-23 13:45

almalinux-release version 8.5-3 was released right after 8.5 release to fix this.
Please install updates first and then enable RS repo. Sorry for inconvenience.

juliogonzalez

2021-11-23 14:47

reporter   ~0000423

Thanks!

Right, that fixes it.

Seems that instance was installed from the official 8.5 ISO (which I guess doesn't contain the fix), and despite updates were enabled during the installation, maybe it was installed right before 8.5-3 was released.

The issue can be closed. Again, thanks for the hint.

alukoshko

2021-11-23 15:04

developer   ~0000424

Thanks for pointing to https://git.almalinux.org/rpms/almalinux-release.
Now it's in sync with package in repos.

Issue History

Date Modified Username Field Change
2021-11-23 09:27 juliogonzalez New Issue
2021-11-23 09:58 juliogonzalez Note Added: 0000421
2021-11-23 13:45 alukoshko Note Added: 0000422
2021-11-23 13:45 alukoshko Note Edited: 0000422
2021-11-23 14:47 juliogonzalez Note Added: 0000423
2021-11-23 15:04 alukoshko Note Added: 0000424
2021-11-23 19:06 alukoshko Assigned To => alukoshko
2021-11-23 19:06 alukoshko Status new => closed
2021-11-23 19:06 alukoshko Resolution open => fixed