Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Zabbix rpm feed not working correctly
-
Hello. I have an issue similar to the problem with an rpm feed in this topic https://forums.inedo.com/topic/5584/rocky-linux-rpm-feed-not-working?_=1770287422508
This time, it's with zabbix repository with a conetor to this repo: https://repo.zabbix.com/zabbix/7.0/rocky/9/x86_64/
Same as on my other post, I need to cache the packages I want in proget. If not, the installation/upgrade of the package fails.
-
Hi @Sigve-opedal_6476 ,
Could you give some tips/guidance on how to repro the error? Ideally, it's something we can see only in ProGet :)
It's probably some quirk in how they implement things, but I wanted to make sure we're looking at the right things before starting.
Thanks,
Alana
-
When I try to run dnf upgrade, I get the following error:
[MIRROR] zabbix-sql-scripts-7.0.22-release.1.el.9.noarch.rpm: Status code: 404 for https://[PROGET_FEED_URL]/packages/noarch/zabbix-sql-scripts/zabbix-sql-scripts-7.0.22-release.1.el.9.noarch.rpm (IP: [my.proget.ip.address])If I search for the package using "Search Packages" on the feed in proget, I find the package. And if I download the package to my computer directly from proget, so that it gets cached n proget, I can run dnf upgrade just fine, and the package is updated. As I said in my original post, it looks very similar as an issue I had with Rocky Linux feeds in the past, wich you resolved
-
Hi @Sigve-opedal_6476 , we're currently investigating and will let you know more later this week
-
I haven't been able to reproduce this in a Rocky 9 test environment. After setting up the feed and connector in ProGet I ran
dnf install zabbix-sql-scripts, and then repeated the test a few times with different versions and variations on formatting the versions. I also tried with cached and uncached packages. I was able to get a 404 to happen one time, but it was due to the upstream repo returning a 404 at the correct URL - which then worked the next time it was tried.Is this happening consistently for you?
