ruby issue

1087 views
Skip to first unread message

Stuart Cracraft

unread,
May 31, 2013, 1:30:46 PM5/31/13
to puppet...@googlegroups.com

 

Hi,

 

I am having problems installing Puppet Server.

 

My gem list follows and then the attempt to install puppet-server.

 

The specific errors are:

 

Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

           Requires: ruby-augeas

Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs)

           Requires: rubygem-json

Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

           Requires: ruby-rgen

Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

           Requires: ruby-shadow

 

I do not know where to get nor how to install the above.

 

Console Log

 

[root@ca-sna-pm01 rubygems-1.8.25]# gem list

 

*** LOCAL GEMS ***

 

actionmailer (3.2.13)

actionpack (3.2.13)

activemodel (3.2.13)

activerecord (3.2.13)

activeresource (3.2.13)

activesupport (3.2.13)

archive-tar-minitar (0.5.2)

arel (3.0.2)

builder (3.0.4)

bundler (1.3.5)

cgi_multipart_eof_fix (2.5.0)

columnize (0.3.6)

daemons (1.1.9)

erubis (2.7.0)

fastthread (1.0.7)

gem_plugin (0.2.3)

hike (1.2.2)

i18n (0.6.1)

journey (1.0.4)

json (1.8.0)

mail (2.5.4)

mime-types (1.23)

mongrel (1.1.5)

multi_json (1.7.4)

polyglot (0.3.3)

rack (1.4.5)

rack-cache (1.2)

rack-ssl (1.3.3)

rack-test (0.6.2)

rails (3.2.13)

railties (3.2.13)

rake (10.0.4)

rdoc (3.12.2)

rgen (0.6.2)

ruby-json (1.1.2)

ruby-shadow (2.2.0)

ruby_core_source (0.1.5)

shadow (1.1)

sprockets (2.2.2)

thor (0.18.1)

tilt (1.4.1)

treetop (1.4.12)

tzinfo (0.3.37)

[root@ca-sna-pm01 rubygems-1.8.25]# yum install puppet-server Loaded plugins: product-id, rhnplugin, security, subscription-manager This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

This system is receiving updates from RHN Classic or RHN Satellite.

Setting up Install Process

Resolving Dependencies

--> Running transaction check

---> Package puppet-server.noarch 0:3.2.1-1.el6 will be installed

--> Processing Dependency: puppet = 3.2.1-1.el6 for package:

--> puppet-server-3.2.1-1.el6.noarch Running transaction check

---> Package puppet.noarch 0:3.2.1-1.el6 will be installed

--> Processing Dependency: facter >= 1.6.11 for package:

--> puppet-3.2.1-1.el6.noarch Processing Dependency: hiera >= 1.0.0 for

--> package: puppet-3.2.1-1.el6.noarch Processing Dependency:

--> ruby(selinux) for package: puppet-3.2.1-1.el6.noarch Processing

--> Dependency: ruby-augeas for package: puppet-3.2.1-1.el6.noarch

--> Processing Dependency: ruby-rgen for package:

--> puppet-3.2.1-1.el6.noarch Processing Dependency: ruby-shadow for

--> package: puppet-3.2.1-1.el6.noarch Running transaction check

---> Package facter.i386 1:1.7.1-1.el6 will be installed Package

---> hiera.noarch 0:1.2.1-1.el6 will be installed

--> Processing Dependency: rubygem-json for package:

--> hiera-1.2.1-1.el6.noarch

---> Package libselinux-ruby.x86_64 0:2.0.94-5.3.el6_4.1 will be

---> installed

--> Processing Dependency: libselinux = 2.0.94-5.3.el6_4.1 for package:

--> libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64

---> Package puppet.noarch 0:3.2.1-1.el6 will be installed

--> Processing Dependency: ruby-augeas for package:

--> puppet-3.2.1-1.el6.noarch Processing Dependency: ruby-rgen for

--> package: puppet-3.2.1-1.el6.noarch Processing Dependency:

--> ruby-shadow for package: puppet-3.2.1-1.el6.noarch Running

--> transaction check

---> Package hiera.noarch 0:1.2.1-1.el6 will be installed

--> Processing Dependency: rubygem-json for package:

--> hiera-1.2.1-1.el6.noarch

---> Package libselinux.x86_64 0:2.0.94-5.3.el6 will be updated

--> Processing Dependency: libselinux = 2.0.94-5.3.el6 for package:

--> libselinux-utils-2.0.94-5.3.el6.x86_64

---> Package libselinux.x86_64 0:2.0.94-5.3.el6_4.1 will be an update

---> Package puppet.noarch 0:3.2.1-1.el6 will be installed

--> Processing Dependency: ruby-augeas for package:

--> puppet-3.2.1-1.el6.noarch Processing Dependency: ruby-rgen for

--> package: puppet-3.2.1-1.el6.noarch Processing Dependency:

--> ruby-shadow for package: puppet-3.2.1-1.el6.noarch Running

--> transaction check

---> Package hiera.noarch 0:1.2.1-1.el6 will be installed

--> Processing Dependency: rubygem-json for package:

--> hiera-1.2.1-1.el6.noarch

---> Package libselinux-utils.x86_64 0:2.0.94-5.3.el6 will be updated

---> Package libselinux-utils.x86_64 0:2.0.94-5.3.el6_4.1 will be an

---> update Package puppet.noarch 0:3.2.1-1.el6 will be installed

--> Processing Dependency: ruby-augeas for package:

--> puppet-3.2.1-1.el6.noarch Processing Dependency: ruby-rgen for

--> package: puppet-3.2.1-1.el6.noarch Processing Dependency:

--> ruby-shadow for package: puppet-3.2.1-1.el6.noarch Finished

--> Dependency Resolution

Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

           Requires: ruby-augeas

Error: Package: hiera-1.2.1-1.el6.noarch (puppetlabs)

           Requires: rubygem-json

Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

           Requires: ruby-rgen

Error: Package: puppet-3.2.1-1.el6.noarch (puppetlabs)

           Requires: ruby-shadow

 You could try using --skip-broken to work around the problem  You could try running: rpm -Va --nofiles --nodigest

[root@ca-sna-pm01 rubygems-1.8.25]#

 

--Stuart

Matthaus Owens

unread,
May 31, 2013, 1:42:43 PM5/31/13
to puppet...@googlegroups.com
Stuart,
You need to have either EPEL or our dependencies repo enabled to get
ruby-augeas, rubygem-json, and ruby-shadow. ruby-rgen is only
available in our dependencies repo currently.

The dependencies repo can be added to yum with the following repo
definition (assuming you have the gpg key installed already, which you
likely do if using our products repo):

[puppetlabs-deps]
name=Puppet Labs Dependencies EL 6 - x86_64
baseurl=http://yum.puppetlabs.com/el/6/dependencies/x86_64
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
keepalive=1
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users...@googlegroups.com.
> To post to this group, send email to puppet...@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>



--
Matthaus Owens
Release Manager, Puppet Labs

Join us at PuppetConf 2013, August 22-23 in San Francisco -
http://bit.ly/pupconf13
Register now and take advantage of the Early Bird discount - save 25%!

Stuart Cracraft

unread,
May 31, 2013, 1:59:38 PM5/31/13
to puppet...@googlegroups.com
Okay, things are better but I am getting this error for json and rubygems.
 

[root@ca-sna-pm01 augeas-1.0.0]# gem install json

Building native extensions.  This could take a while...

Successfully installed json-1.8.0

1 gem installed

Installing ri documentation for json-1.8.0...

Installing RDoc documentation for json-1.8.0...

[root@ca-sna-pm01 augeas-1.0.0]# yum install puppet-server

Loaded plugins: product-id, rhnplugin, security, subscription-manager

This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.

This system is receiving updates from RHN Classic or RHN Satellite.

Setting up Install Process

Resolving Dependencies

--> Running transaction check

---> Package puppet-server.noarch 0:3.2.1-1.el6 will be installed

--> Processing Dependency: puppet = 3.2.1-1.el6 for package: puppet-server-3.2.1-1.el6.noarch

--> Running transaction check

---> Package puppet.noarch 0:3.2.1-1.el6 will be installed

--> Processing Dependency: facter >= 1.6.11 for package: puppet-3.2.1-1.el6.noarch

--> Processing Dependency: hiera >= 1.0.0 for package: puppet-3.2.1-1.el6.noarch

--> Processing Dependency: ruby(selinux) for package: puppet-3.2.1-1.el6.noarch

--> Processing Dependency: ruby-augeas for package: puppet-3.2.1-1.el6.noarch

--> Processing Dependency: ruby-rgen for package: puppet-3.2.1-1.el6.noarch

--> Processing Dependency: ruby-shadow for package: puppet-3.2.1-1.el6.noarch

--> Running transaction check

---> Package facter.i386 1:1.7.1-1.el6 will be installed

---> Package hiera.noarch 0:1.2.1-1.el6 will be installed

--> Processing Dependency: rubygem-json for package: hiera-1.2.1-1.el6.noarch

---> Package libselinux-ruby.x86_64 0:2.0.94-5.3.el6_4.1 will be installed

--> Processing Dependency: libselinux = 2.0.94-5.3.el6_4.1 for package: libselinux-ruby-2.0.94-5.3.el6_4.1.x86_64

---> Package ruby-augeas.x86_64 0:0.4.1-1.el6 will be installed

---> Package ruby-rgen.noarch 0:0.6.2-1.el6 will be installed

---> Package ruby-shadow.x86_64 0:1.4.1-13.el6 will be installed

--> Running transaction check

---> Package libselinux.x86_64 0:2.0.94-5.3.el6 will be updated

--> Processing Dependency: libselinux = 2.0.94-5.3.el6 for package: libselinux-utils-2.0.94-5.3.el6.x86_64

---> Package libselinux.x86_64 0:2.0.94-5.3.el6_4.1 will be an update

---> Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed

--> Processing Dependency: rubygems for package: rubygem-json-1.5.5-1.el6.x86_64

--> Running transaction check

---> Package libselinux-utils.x86_64 0:2.0.94-5.3.el6 will be updated

---> Package libselinux-utils.x86_64 0:2.0.94-5.3.el6_4.1 will be an update

---> Package rubygem-json.x86_64 0:1.5.5-1.el6 will be installed

--> Processing Dependency: rubygems for package: rubygem-json-1.5.5-1.el6.x86_64

--> Finished Dependency Resolution

Error: Package: rubygem-json-1.5.5-1.el6.x86_64 (puppetlabs-deps)

           Requires: rubygems

You could try using --skip-broken to work around the problem

You could try running: rpm -Va --nofiles --nodigest

[root@ca-sna-pm01 augeas-1.0.0]#

 

Matthaus Owens

unread,
May 31, 2013, 2:50:20 PM5/31/13
to puppet...@googlegroups.com
Stuart,
rubygems comes from the redhat optional repo, so you'll need to have
that repo enabled to get the rubygems package.

Stuart Cracraft

unread,
May 31, 2013, 2:57:41 PM5/31/13
to puppet...@googlegroups.com
Can you copy/paste the repo entry which works for you in reply?
> You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe?hl=en.
> To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.

Matthaus Owens

unread,
May 31, 2013, 3:23:19 PM5/31/13
to puppet...@googlegroups.com

Stuart Cracraft

unread,
Jun 1, 2013, 1:49:16 AM6/1/13
to puppet...@googlegroups.com
Hey, good news.

All is well.

Ruby & related are good. Puppet too. And Red Hat.

Also, I've documented/wiki'd the Puppet Master + Client install with respect
to bare metal to delivered system for all related aspects and transmitted, fully,
disclosed entirely, to staff.

Next week, I will be tuning the configuration file on master and agents and
writing many more puppet patterns plus training staff.

As it is their only hope!

--Stuart

P.S. The firm's personnel have had heart attacks, strokes and other major maladies amongst
staff in the past year due to the LACK OF AUTOMATION!!!!!!!

Puppet is the Cure!!!!

Kick Chef and CF Engine's non-collective butts!!!!!


Message has been deleted

Yizhar A.

unread,
Jun 10, 2013, 8:51:02 AM6/10/13
to puppet...@googlegroups.com
Hi,
 
Finish my things on this issue for now as the last one in this chain talented enough to be asking for pay for answering this....
 
I'll update when I'll figure it out else. 
 
Stay tuned,
 
Yizhar 
 
"Don't ask what the community can contribute to you ? ask what I can contribute the community"
On Sunday, June 9, 2013 3:06:48 PM UTC+3, Yizhar A. wrote:
Dear Stuart,
 
Kind of my first steps into puppet on RHEL 6 and I wonder how you manage to solve the rubygems issue.
 
Since I'm using RHEL 6.4 (.x86_64) in my test env. with only puppetlabs repo I can't see from where I can get the rubygems missing package.
 
As you after wiki'd it :) can you give me a piece of advise in here or attached your docs to help me through ?
 
Thanks,
 
--Yizhar

Stuart Cracraft

unread,
Jun 10, 2013, 9:31:37 AM6/10/13
to puppet...@googlegroups.com
It's not that hard!

You can do it!!!

Also, you could buy some books on the subject!!!!!

Lab Yizhar

unread,
Jun 10, 2013, 10:40:20 AM6/10/13
to puppet...@googlegroups.com
Thanks m8 for the mental support :)
 
As you already know, as an open source believer ,I'm kind of into it and the solution is there, But I want to do it without RHN subscription that will used on our production env.
 
Couple of humps and I'll be there this way or the offical other...
 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

Stuart Cracraft

unread,
Jun 10, 2013, 11:12:39 AM6/10/13
to puppet...@googlegroups.com
You are most welcome. 

Greg Chavez

unread,
Jun 11, 2013, 5:37:42 PM6/11/13
to puppet...@googlegroups.com
The rubygems package is available from here:

https://yum.puppetlabs.com/el/5/dependencies/x86_64/

So why wouldn't it be available from 6? I'm pretty sure it used to be
there since I've kicked several rhel 6 systems that had no problem
installing puppet from puppetlabs. Was it mistakenly dropped from the
puppetlabs rhel 6 repo?

Thanks
--Greg Chavez

Matthaus Owens

unread,
Jun 11, 2013, 6:43:21 PM6/11/13
to puppet...@googlegroups.com
We supply rubygems for rhel 5 because it is not available in centos or
rhel 5 core (it is in EPEL). In rhel6 and cent6, it is widely and
easily available (in cent6 base, and in rhel6 optional repos), so we
don't supply it for el6.

Stuart Cracraft

unread,
Jun 11, 2013, 9:40:46 PM6/11/13
to puppet...@googlegroups.com

Why not make it easy on the community?

Include all dependencies just
as you do with pe...

--Stuart

Greg Chavez

unread,
Jun 12, 2013, 8:52:48 AM6/12/13
to puppet...@googlegroups.com
Which is just fine if your company has the Optional subscription.
Mine doesn't. So I'm screwed unless I write a script to manually pull
updates from Fedora or CentOS into a custom mrepo repository. Bit of a
pain, that is.
\*..+.-
--Greg Chavez
+//..;};

Stuart Cracraft

unread,
Jun 12, 2013, 11:39:23 AM6/12/13
to puppet...@googlegroups.com
Right on brotha!

--Stuart

Michael Stahnke

unread,
Jun 14, 2013, 10:13:19 PM6/14/13
to puppet...@googlegroups.com
On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez <greg....@gmail.com> wrote:
> Which is just fine if your company has the Optional subscription.
> Mine doesn't. So I'm screwed unless I write a script to manually pull
> updates from Fedora or CentOS into a custom mrepo repository. Bit of a
> pain, that is.

The optional repo is free from what I can tell. It's included with a
RHEL subscription. Puppet Labs doesn't try to replace packages in
provided by the upstream OS vendor. Therefore, we don't supply
packages that replace things in the RHEL repo since they work just
fine with Puppet et al.

Stuart Cracraft

unread,
Jun 14, 2013, 10:44:00 PM6/14/13
to puppet...@googlegroups.com
Boo!!! Hiss!!

Be a One-Stop-Shop!

It's YOUR collective after all!!!!

--Stuart
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/puppet-users/ghDZsdkC3C0/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
> To post to this group, send email to puppet...@googlegroups.com.
> Visit this group at http://groups.google.com/group/puppet-users.

Greg Chavez

unread,
Jun 15, 2013, 3:15:33 PM6/15/13
to puppet...@googlegroups.com
I don't have access to the Optional repo, full stop, so I can't mirror
it. However, I do have access to its constituent packages, so what
you can do is search for "rubgems" at RHN under Downloads -> Packages
and download the rpm. I then dropped it into a one-file mrepo, added
the mrepo info to my puppetlabs yum.repo file that I instantiate with
Cobbler and then control with puppet, and viola, my kicks and spins
come up with a working puppet client. Easy enough to do this every
time I upgrade puppet.

I think Puppet is making a mistake here too, but there are worse
things. My problem will be solved in total when my company
transitions to CentOS later this year.

Cheers.

--Greg Chavez

jcbollinger

unread,
Jun 17, 2013, 10:27:00 AM6/17/13
to puppet...@googlegroups.com


On Friday, June 14, 2013 9:13:19 PM UTC-5, Michael Stanhke wrote:
Puppet Labs doesn't try to replace packages in
provided by the upstream OS vendor.

Yay!  Thank you!  PL has no business replacing vendor-supplied OS components.  It especially has no business configuring repositories such that there is a risk of users installing such replacement components without realizing they are doing so.  WTG, PL.


John
 

Stuart Cracraft

unread,
Jun 17, 2013, 10:50:28 AM6/17/13
to puppet...@googlegroups.com
Don't replace them.

Just PROVIDE them.

One-stop shop for yum downloads for non PE people.

The analogy is PE Enterprise for the normal "rank-and-file".

What you like to call "the Collective"...

--
You received this message because you are subscribed to a topic in the Google Groups "Puppet Users" group.

To unsubscribe from this group and all its topics, send an email to puppet-users...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.

Yizhar A.

unread,
Jun 18, 2013, 4:33:12 AM6/18/13
to puppet...@googlegroups.com
Hi,
 
Back with some Sweet goooood news :)  and found the missing part.  As mention I tried to install on RHEL 6.4 testing server and failed on rubygems.
 
Few days ago I had a remote session with one of my valuable friends that guess what, also had this issue and it's all was around rubygem installation.  
 
After trying to install it from rubygems official site using setup.rb I discovered it was just not the the same cup of tea my RHEL server likes.
 
So, as I don't want to activate my RHN subscription, I downloaded it from CentOS free rpm online repository, that was suitable for my version (RHEL 6.4 - 64bit) at:
http://rpm.pbone.net/index.php3/stat/4/idpl/20348086/dir/centos_6/com/rubygems-1.3.7-1.el6.noarch.rpm.html (Strange thing its from 2010 but fits the ryby of RHEL 6.4 that in ver 1.8.7)
 
OR better if already got Internet connection you can use:
 
After this using the yum command: yum localinstall rubygems-1.3.7-1.el6.noarch.rpm and Viola' the "yum install puppet puppet-server" (ver. 3.2.1) from puppet repo went just smooth.
 
Thanks Yev for helping me out on this and for the community I'm attaching a full quick installation doc that help those novice out there :)
 
My final thought/suggestion regards this issue: If you are already using Internet connection and you want to leave in the free world use CentOS.
I could do it quicker and I think better using yum to solved all the issue I confront.
 
I'll try to post the whole installation in few days as attached text file in here or in general issue.
 
Good luck Puppeteers wherever U R !
 
Yizhar 
 
"Don't ask what the community can contribute to you ? ask what you can contribute to the community"

José Luis Navarro Lustres

unread,
Mar 2, 2014, 3:15:16 PM3/2/14
to puppet...@googlegroups.com
fine, perfect
Reply all
Reply to author
Forward
0 new messages