FAQ
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

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to puppet-users@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.

Search Discussions

  • Matthaus Owens at May 31, 2013 at 5:42 pm
    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
    On Fri, May 31, 2013 at 10:30 AM, Stuart Cracraft wrote:


    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

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • José Luis Navarro Lustres at Mar 2, 2014 at 8:34 pm
    fine, perfect


    El viernes, 31 de mayo de 2013 19:42:43 UTC+2, Matthaus Litteken escribió:
    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<http://yum.puppetlabs.com/el/6/dependencies/x86_64enabled=1gpgcheck=1gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabskeepalive=1>
    On Fri, May 31, 2013 at 10:30 AM, Stuart Cracraft wrote:


    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

    --
    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 <javascript:>.
    To post to this group, send email to puppet...@googlegroups.com<javascript:>.
    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%!
    --
    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+unsubscribe@googlegroups.com.
    To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/cbb3c181-7592-4c71-9101-9e043f643a91%40googlegroups.com.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Stuart Cracraft at May 31, 2013 at 5:59 pm
    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]#



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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 at May 31, 2013 at 6:50 pm
    Stuart,
    rubygems comes from the redhat optional repo, so you'll need to have
    that repo enabled to get the rubygems package.
    On Fri, May 31, 2013 at 10:59 AM, Stuart Cracraft wrote:
    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]#



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Stuart Cracraft at May 31, 2013 at 6:57 pm
    Can you copy/paste the repo entry which works for you in reply?
    On May 31, 2013, at 11:50 AM, Matthaus Owens wrote:

    Stuart,
    rubygems comes from the redhat optional repo, so you'll need to have
    that repo enabled to get the rubygems package.
    On Fri, May 31, 2013 at 10:59 AM, Stuart Cracraft wrote:
    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]#



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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 at May 31, 2013 at 7:23 pm
    I don't have a rhel box handy to enable that repo on, but here's the
    top google hit.

    https://access.redhat.com/site/documentation/en-US/Red_Hat_Subscription_Management/1.0/html/Subscription_Management_Guide/entitlements-and-yum.html
    On Fri, May 31, 2013 at 11:57 AM, Stuart Cracraft wrote:
    Can you copy/paste the repo entry which works for you in reply?
    On May 31, 2013, at 11:50 AM, Matthaus Owens wrote:

    Stuart,
    rubygems comes from the redhat optional repo, so you'll need to have
    that repo enabled to get the rubygems package.
    On Fri, May 31, 2013 at 10:59 AM, Stuart Cracraft wrote:
    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]#



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Stuart Cracraft at Jun 1, 2013 at 5:49 am
    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!!!!!


    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Yizhar A. at Jun 9, 2013 at 9:38 pm
    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Yizhar A. at Jun 10, 2013 at 12:51 pm
    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Stuart Cracraft at Jun 10, 2013 at 1:31 pm
    It's not that hard!

    You can do it!!!

    Also, you could buy some books on the subject!!!!!
    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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


    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
    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!!!!!



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Lab Yizhar at Jun 10, 2013 at 2:40 pm
    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!

    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Stuart Cracraft at Jun 10, 2013 at 3:12 pm
    You are most welcome.
    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:
    It's not that hard!

    You can do it!!!

    Also, you could buy some books on the subject!!!!!
    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:
    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Greg Chavez at Jun 11, 2013 at 9:37 pm
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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 at Jun 11, 2013 at 10:43 pm
    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.
    On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez wrote:
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Stuart Cracraft at Jun 12, 2013 at 1:41 am
    Why not make it easy on the community?

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

    --Stuart
    On Jun 11, 2013, at 3:43 PM, Matthaus Owens wrote:

    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.
    On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez wrote:
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Greg Chavez at Jun 12, 2013 at 12:52 pm
    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.
    On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens wrote:
    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.
    On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez wrote:
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.


    --
    \*..+.-
    --Greg Chavez
    +//..;};

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Stuart Cracraft at Jun 12, 2013 at 3:39 pm
    Right on brotha!

    --Stuart
    On Jun 12, 2013, at 5:52 AM, Greg Chavez 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.
    On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens wrote:
    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.
    On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez wrote:
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.


    --
    \*..+.-
    --Greg Chavez
    +//..;};

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
  • Michael Stahnke at Jun 15, 2013 at 2:13 am

    On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez 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.

    On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens wrote:
    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.
    On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez wrote:
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.


    --
    \*..+.-
    --Greg Chavez
    +//..;};

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Stuart Cracraft at Jun 15, 2013 at 2:44 am
    Boo!!! Hiss!!

    Be a One-Stop-Shop!

    It's YOUR collective after all!!!!

    --Stuart
    On Jun 14, 2013, at 7:13 PM, Michael Stahnke wrote:
    On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez 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.

    On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens wrote:
    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.
    On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez wrote:
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.


    --
    \*..+.-
    --Greg Chavez
    +//..;};

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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.
    To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Greg Chavez at Jun 15, 2013 at 7:15 pm
    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
    On Fri, Jun 14, 2013 at 10:44 PM, Stuart Cracraft wrote:
    Boo!!! Hiss!!

    Be a One-Stop-Shop!

    It's YOUR collective after all!!!!

    --Stuart
    On Jun 14, 2013, at 7:13 PM, Michael Stahnke wrote:
    On Wed, Jun 12, 2013 at 5:52 AM, Greg Chavez 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.

    On Tue, Jun 11, 2013 at 6:43 PM, Matthaus Owens wrote:
    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.
    On Tue, Jun 11, 2013 at 2:37 PM, Greg Chavez wrote:
    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
    On Mon, Jun 10, 2013 at 11:12 AM, Stuart Cracraft wrote:
    You are most welcome.

    On Jun 10, 2013, at 7:40 AM, Lab Yizhar wrote:

    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...
    On Mon, Jun 10, 2013 at 4:31 PM, Stuart Cracraft wrote:

    It's not that hard!

    You can do it!!!

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

    On Jun 10, 2013, at 5:51 AM, Yizhar A. wrote:

    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

    On Saturday, June 1, 2013 8:49:16 AM UTC+3, Stuart Cracraft wrote:

    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!!!!!
    --
    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+unsubscribe@googlegroups.com.

    To post to this group, send email to puppet-users@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.




    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.



    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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%!

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.


    --
    \*..+.-
    --Greg Chavez
    +//..;};

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@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.
    --
    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.
    To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.


    --
    \*..+.-
    --Greg Chavez
    +//..;};

    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Jcbollinger at Jun 17, 2013 at 2:27 pm

    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


    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Stuart Cracraft at Jun 17, 2013 at 2:50 pm
    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"...
    On Jun 17, 2013, at 10:27 AM, jcbollinger wrote:



    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


    --
    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.
    To unsubscribe from this group and all its topics, send an email to puppet-users+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.
  • Yizhar A. at Jun 18, 2013 at 8:33 am
    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
    *<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:
    # wget *
    ftp://mirror.switch.ch/pool/3/mirror/centos/6.4/os/x86_64/Packages/rubygems-1.3.7-1.el6.noarch.rpm
    *<ftp://mirror.switch.ch/pool/3/mirror/centos/6.4/os/x86_64/Packages/rubygems-1.3.7-1.el6.noarch.rpm>

    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"
    On Monday, June 17, 2013 5:27:00 PM UTC+3, jcbollinger wrote:


    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
    --
    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+unsubscribe@googlegroups.com.
    To post to this group, send email to puppet-users@googlegroups.com.
    Visit this group at http://groups.google.com/group/puppet-users.
    For more options, visit https://groups.google.com/groups/opt_out.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppuppet-users @
categoriespuppet
postedMay 31, '13 at 5:30p
activeMar 2, '14 at 8:34p
posts24
users8
websitepuppetlabs.com

People

Translate

site design / logo © 2022 Grokbase