-
Problem report
-
Resolution: Fixed
-
Trivial
-
None
-
None
-
Sprint candidates
-
1
Changes in 7.2 repo
Starting with 7.2 release cycle, some changes were made to the repository structure at the https://repo.zabbix.com/ page.
The zabbix directory contains directories for each Zabbix version.
We used to put unstable pre-release packages into version directories that ended with odd numbers, i.e 6.3 for 6.4 unstable packages, 6.5 for 7.0 unstable packages etc.
Each of the version directories contained sub-directories based on the OS name.
Stable and unstable repos had their own separate zabbix-release packages, that were put together with the rest of the packages in each respective OS repo.
The new 7.2 directory shall contain three sub-directories:
- release - contains just the zabbix-release packages
- stable - contains stable packages (For versions that have no alphatag.)
- unstable - contains unstable package, for both major pre-release alpha, beta, rc versions, as well as for minor rc versions.
A single set of zabbix-release packages, stored in release sub-directory now serves both stable and unstable versions. Repo files shipped by zabbix-release package have been split into separate smaller ones. Specifically stable and unstable repos are configured in separate files.
During the pre-release cycle unstable repos are enabled by default. With the stable 7.2.0 release, an update to zabbix-release packge is to be shipped, containing stable repo files.
Changes to non-supported / third-party repo
We shipped certain dependency packages missing form official repos of rhel and its derivatives ourselves in the non-supported repo. For 7.2+ a new set of repos called thrird-party have been added. This was done because certain necessary changes like updating the repo keys was difficult due possibility of breaking existing old installations. The new improved third-party repo shall replace the old non-supported repo from 7.2 onwards.
Changes to the keys
A new B5333005 is used to sign everything in 7.2+, except for zabbix-tools repo, which has its own deciated zabbix-tools key.
Package structure changes
Frontend
Frontend files have been moved into /usr/share/zabbix/ui directory to be more compliant with linux filesystem hierarchy standart. (ZBX-24272) This will require manual intervention during upgrade to 7.2+ from older version. Specifically the web-server configuration files shipped by 7.2 zabbix-(apache/nginx)-conf packages will not be override existing file from previous versions. Therefore these will have to be updated manually. Either install the new conf file shipped with 7.2 and then re-add your configuration there. Or repace /usr/share/zabbix to /usr/share/zabbix/ui in the old conf file. I recommend the former option.
Agent2 plugins
Agent2 plugins are not stored in /usr/libexec directory. Simliar to the frontend case, the plugin configuration files may need to be updated if you had some changes in them. (DEV-3991)