Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

the install action for zabbix 5.0 on centos/redhat 7 is wrong #731

Closed
taleintervenor opened this issue Dec 15, 2020 · 1 comment · Fixed by #743
Closed

the install action for zabbix 5.0 on centos/redhat 7 is wrong #731

taleintervenor opened this issue Dec 15, 2020 · 1 comment · Fixed by #743

Comments

@taleintervenor
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: puppet5-release-5.0.0-7
  • Ruby:
  • Distribution: CentOS Linux release 7.7.1908
  • Module version: 8.0.0

How to reproduce (e.g Puppet code you use)

class { 'zabbix':
zabbix_version => $version,
}
set $version = 5.0

What are you seeing

puppet zabbix module try to install zabbix-web-mysql

What behaviour did you expect instead

according to zabbix official install instruction, only on centos/redhat 8 can find the zabbix-web-mysql package. when it is centos7, you need to install centos-release-scl and then install zabbix-web-mysql-scl package from the scl repo.

Output log

Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install zabbix-web-mysql' returned 1: Error: Nothing to do
Error: /Stage[main]/Zabbix::Web/Package[zabbix-web-mysql]/ensure: change from 'purged' to 'latest' failed: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install zabbix-web-mysql' returned 1: Error: Nothing to do (corrective)

Any additional information you'd like to impart

@jameskirsop
Copy link
Contributor

This is a duplicate of #689 and the particular concern is being addressed in the open issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants