Upgrade Issues to 3.0.1

[tomtomclub]

Hi,

I'm running Zabbix 2.0.9 and trying to upgrade to 3.0.1, which according to the installation instructions is possible as a direct upgrade. So, I followed the instructions to install the 3.0 repo by running:

rpm -ivh http://repo.zabbix.com/zabbix/3.0/rh...el6.noarch.rpm

When I then try and update zabbix I get errors like this:

Error: Package: zabbix-server-mysql-2.0.9-1.el6.x86_64 (@zabbix)
Requires: zabbix = 2.0.9-1.el6
Removing: zabbix-2.0.9-1.el6.x86_64 (@zabbix)
zabbix = 2.0.9-1.el6
Obsoleted By: zabbix-proxy-mysql-3.0.1-1.el6.x86_64 (zabbix)
Not found
Available: zabbix-1.8.22-1.el6.x86_64 (epel)
zabbix = 1.8.22-1.el6
Available: zabbix22-2.2.11-1.el6.x86_64 (epel)
zabbix = 2.2.11-1.el6

My /etc/yum.repos.d/zabbix.repo file has the right info:

[zabbix]
name=Zabbix Official Repository - $basearch
baseurl=http://repo.zabbix.com/zabbix/3.0/rhel/6/x86_64/
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-ZABBIX

So it seems like I'm in a weird place where 2.0 is installed

Installed Packages
zabbix.x86_64 2.0.9-1.el6 @zabbix

and instead of seeing the 3.0 repo files the upgrade process sees the files available in the epel repo for Zabbix

repoquery -qi zabbix

Name : zabbix
Version : 1.8.22
Release : 1.el6
Architecture: x86_64
Size : 316692
Packager : Fedora Project
Group : Applications/Internet
URL : http://www.zabbix.com
Repository : epel
Summary : Open-source monitoring solution for your IT infrastructure
Source : zabbix-1.8.22-1.el6.src.rpm

and not the new zabbix.repo file I have, even if I disable the epel repo

yum --disablerepo="*" --enablerepo="zabbix" list zabbix
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
* base: mirror.es.its.nyu.edu
* extras: mirror.es.its.nyu.edu
* updates: centos.mirror.nac.net
Installed Packages
zabbix.x86_64 2.0.9-1.el6 @zabbix

I appear to be in some sort of repo hell, and the core issue seems to be that I can't get yum to see the new zabbix.repo file. Can anyone provide assistance, point me in the right direction, etc.?

[jan.garaj]

Try to clean your os package cache (yum clean all is not sufficient command in some cases).