-
Incident report
-
Resolution: Fixed
-
Minor
-
None
-
3.0.14
-
CentOS 7.4 x86_64
Steps to reproduce:
Run yum install zabbix-agent when using the following repo
[ zabbix ]
name=Zabbix Official Repository - $basearch
baseurl=http://repo.zabbix.com/zabbix/3.0/rhel/7/$basearch/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX
Result:
[~]$ sudo yum install zabbix-agent Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Resolving Dependencies --> Running transaction check ---> Package zabbix-agent.x86_64 0:3.0.14-1.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved =================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================== Installing: zabbix-agent x86_64 3.0.14-1.el7 zabbix 339 k Transaction Summary =================================================================================================================================================================================== Install 1 Package Total download size: 339 k Installed size: 1.3 M Is this ok [y/d/N]: y Downloading packages: zabbix-agent-3.0.14-1.el7.x86_ FAILED http://repo.zabbix.com/zabbix/3.0/rhel/7/x86_64/zabbix-agent-3.0.14-1.el7.x86_64.rpm: [Errno -1] Package does not match intended download. Suggestion: run yum --enablerepo=zabbix clean metadata Trying other mirror. Error downloading packages: zabbix-agent-3.0.14-1.el7.x86_64: [Errno 256] No more mirrors to try.
I've tried
yum --enablerepo=zabbix clean metadata
As well as several other things like disabling GPG. I'm not super versed with yum so this could be something on my end that's causing this, but we haven't changed any of the code on our zabbix-agent or aptcache puppet classes.
I can manually download that file directly from the repo using wget from the same node, so I'm not sure what the problem is.