Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1235804 - warning about multi_json
Summary: warning about multi_json
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-25 19:04 UTC by Fred van Zwieten
Modified: 2024-06-13 20:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-14 14:41:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Fred van Zwieten 2015-06-25 19:04:38 UTC 
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:
Comment 1 RHEL Program Management 2015-06-25 19:22:39 UTC 
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.
Comment 3 jcallaha 2015-07-23 18:22:16 UTC 
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>'
Comment 4 Bryan Kearney 2016-07-26 15:25:24 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 5 Bryan Kearney 2016-07-26 15:43:43 UTC 
Moving 6.2 bugs out to sat-backlog.
Comment 7 Stephen Benjamin 2016-08-23 16:28:55 UTC 
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!
Comment 8 Stephen Benjamin 2016-09-16 11:53:32 UTC 
Reopening since there's been a few reports from customers that they see this problem.
Comment 10 Sebastian Hetze 2016-09-28 08:27:18 UTC 
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.
Comment 11 Stephen Benjamin 2016-10-14 14:41:25 UTC 
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).
Note You need to log in before you can comment on or make changes to this bug.