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

Puppet 5.3 Zabbix 2.4 json conflict #502

Closed
swmadmsys opened this issue May 22, 2018 · 0 comments
Closed

Puppet 5.3 Zabbix 2.4 json conflict #502

swmadmsys opened this issue May 22, 2018 · 0 comments

Comments

@swmadmsys
Copy link

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet:
    puppet agent --version
    5.3.2

  • Ruby:

#ruby -v 
ruby 2.0.0p648 (2015-12-16) [x86_64-linux]
#/opt/puppetlabs/puppet/bin/ruby -v 
ruby 2.4.1p111 (2017-03-22 revision 58053) [x86_64-linux]
  • Distribution:
    CentOS 7

  • Module version: 6.3.1

  • Zabbix : 2.4.6

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

Each time using external ressource

What are you seeing

#puppet agent --test 
[...]
Error: Could not run: Unable to activate zabbixapi-2.4.9, because json-2.0.2 conflicts with json (>= 1.6.0, ~> 1.6)

What behaviour did you expect instead

Creating host via API

Output log

Any additional information you'd like to impart

/opt/puppetlabs/puppet/bin/gem list

*** LOCAL GEMS ***

bigdecimal (default: 1.3.0)
bundler (1.16.2)
deep_merge (1.0.1)
did_you_mean (1.1.0)
facter (3.9.2)
fast_gettext (1.1.0)
gettext (3.2.2)
gettext-setup (0.28)
hiera (3.4.2)
hocon (1.2.5)
io-console (default: 0.4.6)
json (default: 2.0.2, 1.8.6)
locale (2.1.2)
minitest (5.10.1)
net-ssh (4.1.0)
net-telnet (0.1.1)
openssl (default: 2.0.3)
power_assert (0.4.1)
psych (default: 2.2.2)
puppet (5.3.2)
rake (12.0.0)
rdoc (default: 5.0.0)
semantic_puppet (0.1.2)
stomp (1.3.3)
test-unit (3.2.3)
text (1.3.1)
xmlrpc (0.2.1)
zabbixapi (2.4.9, 2.4.4)
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

No branches or pull requests

1 participant