Bug 1235804
| Summary: | warning about multi_json | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Fred van Zwieten <fvzwieten> |
| Component: | Installation | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED NOTABUG | QA Contact: | Katello QA List <katello-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.1.0 | CC: | bbuckingham, jcallaha, mtenheuv, shetze, sreber, stbenjam |
| Target Milestone: | Unspecified | Keywords: | Reopened, Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-10-14 14:41:25 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release. I ran into this error while trying to verify #1218792.
[root@rhsm-qe-1 foreman-installer]# bin/foreman-installer -h
WARN: Unresolved specs during Gem::Specification.reset:
multi_json (>= 1.3.6)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
/usr/local/share/gems/gems/puppet-3.8.1/lib/puppet/context.rb:54:in `lookup': Could not parse for environment production: no 'environments' in {:current_environment=>#<Puppet::Node::Environment:0x00000002774730 @name=:"*root*", @modulepath=[], @manifest=:no_manifest, @config_version=nil, @watching=true>, :root_environment=>#<Puppet::Node::Environment:0x00000002774730 @name=:"*root*", @modulepath=[], @manifest=:no_manifest, @config_version=nil, @watching=true>} at top of [[0, nil, nil]] (Puppet::Error)
from /usr/local/share/gems/gems/puppet-3.8.1/lib/puppet.rb:236:in `lookup'
from /usr/local/share/gems/gems/puppet-3.8.1/lib/puppet.rb:267:in `future_parser?'
from /usr/local/share/gems/gems/puppet-3.8.1/lib/puppet/parser/parser_factory.rb:12:in `parser'
from /usr/local/share/gems/gems/puppet-3.8.1/lib/puppet/node/environment.rb:541:in `perform_initial_import'
from /usr/local/share/gems/gems/puppet-3.8.1/lib/puppet/node/environment.rb:276:in `known_resource_types'
from /usr/local/share/gems/gems/puppet-3.8.1/lib/puppet/resource/type_collection_helper.rb:5:in `known_resource_types'
from /usr/local/share/gems/gems/puppet-3.8.1/lib/puppet/parser/parser_support.rb:120:in `import'
from /usr/share/gems/gems/kafo_parsers-0.0.4.4/lib/kafo_parsers/puppet_module_parser.rb:38:in `initialize'
from /usr/share/gems/gems/kafo_parsers-0.0.4.4/lib/kafo_parsers/puppet_module_parser.rb:16:in `new'
from /usr/share/gems/gems/kafo_parsers-0.0.4.4/lib/kafo_parsers/puppet_module_parser.rb:16:in `parse'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/puppet_module.rb:44:in `parse'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/configuration.rb:85:in `block in modules'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/configuration.rb:85:in `map'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/configuration.rb:85:in `modules'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/kafo_configure.rb:173:in `modules'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/kafo_configure.rb:155:in `params'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/kafo_configure.rb:188:in `set_parameters'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/kafo_configure.rb:66:in `initialize'
from /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:125:in `new'
from /usr/share/gems/gems/clamp-0.6.2/lib/clamp/command.rb:125:in `run'
from /usr/local/share/gems/gems/kafo-0.6.11/lib/kafo/kafo_configure.rb:119:in `run'
from bin/foreman-installer:5:in `<main>'
Moving 6.2 bugs out to sat-backlog. Moving 6.2 bugs out to sat-backlog. Works for me on 6.2 GA: [root@sat-rhel7 foreman-installer]# capsule-certs-generate --capsule-fqdn cdcv492502.eu.rabonet.com --certs-tar ~/capsule.example.com-certs.tar Installing Done [100%] [...............................................................................................................................] Success! Reopening since there's been a few reports from customers that they see this problem. I see this warning on satellite-installer --scenario satellite --upgrade Further investigation shows more than one version of multi_json present on the system: gem list multi_json *** LOCAL GEMS *** multi_json (1.11.2, 1.8.2) While this fulfils the requirement (>= 1.3.6) it may be the check does not cope with the two versions installed.
Ah indeed. Thanks for that additional info.
This isn't a bug, at least for Satellite. The users have some how managed to run bundler/gem and install gems from source onto their Satellite server.
This can't be supported on Satellite, we have very particular gem requirements and using the gem/bundle tools directly always causes problems like this. You can reproduce it easily:
[root@sat-rhel7 ~]# gem install multi_json -v 1.11.2
[root@sat-rhel7 ~]# foreman-installer --help
WARN: Unresolved specs during Gem::Specification.reset:
multi_json (>= 1.3.6)
If you need some unpackaged/source ruby software: don't run it on the Satellite, package it as an RPM, or use some utility like RVM.
To fix the error, do 'gem uninstall multi_json -v 1.11.2' (or whatever version of the duplicate gem).
|
Description of problem: [root@bxtv492502 ~]# capsule-certs-generate --capsule-fqdn cdcv492502.eu.rabonet.com --certs-tar ~/capsule.example.com-certs.tar WARN: Unresolved specs during Gem::Specification.reset: multi_json (>= 1.3.6) WARN: Clearing out unresolved specs. Please report a bug if this causes problems. Installing Done [100%] [.....................................................] Success! Version-Release number of selected component (if applicable): 6.1.0 public beta How reproducible: Not sure. Have seen it on multiple installer runs. Above is just an example. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: