So I have decided to give Foreman a try.

Yet, the following occurred when I tried to install It.

Ruby enthusiasts, any thoughts?

The rest-client installed is 1.6.7 but the foreman installer install 
doesn't see it.

 # gem list | grep rest

rest-client (1.6.7)

# yum -y install foreman-installer

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

              : versionlock

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 foreman-installer.noarch 1:1.3.1-1.el6 will be installed

--> Processing Dependency: rubygem-foreman_api >= 0.1.4 for package: 
1:foreman-installer-1.3.1-1.el6.noarch

--> Processing Dependency: rubygem-kafo for package: 
1:foreman-installer-1.3.1-1.el6.noarch

--> Processing Dependency: rubygem-highline for package: 
1:foreman-installer-1.3.1-1.el6.noarch

--> Running transaction check

---> Package rubygem-foreman_api.noarch 0:0.1.9-1.el6 will be installed

--> Processing Dependency: rubygem(rest-client) >= 1.6.1 for package: 
rubygem-foreman_api-0.1.9-1.el6.noarch

--> Processing Dependency: rubygem(oauth) for package: 
rubygem-foreman_api-0.1.9-1.el6.noarch

---> Package rubygem-highline.noarch 0:1.4.0-2.el6 will be installed

---> Package rubygem-kafo.noarch 0:0.2.2-1.el6 will be installed

--> Processing Dependency: rubygem(rdoc) for package: 
rubygem-kafo-0.2.2-1.el6.noarch

--> Processing Dependency: rubygem(powerbar) for package: 
rubygem-kafo-0.2.2-1.el6.noarch

--> Processing Dependency: rubygem(logging) for package: 
rubygem-kafo-0.2.2-1.el6.noarch

--> Processing Dependency: rubygem(clamp) for package: 
rubygem-kafo-0.2.2-1.el6.noarch

--> Running transaction check

---> Package rubygem-clamp.noarch 0:0.6.1-9.el6 will be installed

---> Package rubygem-foreman_api.noarch 0:0.1.9-1.el6 will be installed

--> Processing Dependency: rubygem(rest-client) >= 1.6.1 for package: 
rubygem-foreman_api-0.1.9-1.el6.noarch

---> Package rubygem-logging.noarch 0:1.8.1-25.el6 will be installed

--> Processing Dependency: rubygem(multi_json) >= 1.3.6 for package: 
rubygem-logging-1.8.1-25.el6.noarch

--> Processing Dependency: rubygem(little-plugger) >= 1.1.3 for package: 
rubygem-logging-1.8.1-25.el6.noarch

---> Package rubygem-oauth.noarch 0:0.4.7-5.el6 will be installed

---> Package rubygem-powerbar.noarch 0:1.0.11-7.el6 will be installed

--> Processing Dependency: rubygem(hashie) >= 1.1.0 for package: 
rubygem-powerbar-1.0.11-7.el6.noarch

--> Processing Dependency: rubygem(ansi) >= 1.4.0 for package: 
rubygem-powerbar-1.0.11-7.el6.noarch

---> Package rubygem-rdoc.x86_64 0:3.12-12.el6 will be installed

--> Running transaction check

---> Package rubygem-ansi.noarch 0:1.4.3-0.el6 will be installed

---> Package rubygem-foreman_api.noarch 0:0.1.9-1.el6 will be installed

--> Processing Dependency: rubygem(rest-client) >= 1.6.1 for package: 
rubygem-foreman_api-0.1.9-1.el6.noarch

---> Package rubygem-hashie.noarch 0:2.0.5-0.el6 will be installed

---> Package rubygem-little-plugger.noarch 0:1.1.3-17.el6 will be installed

---> Package rubygem-multi_json.noarch 0:1.3.6-11.el6 will be installed

--> Finished Dependency Resolution

Error: Package: rubygem-foreman_api-0.1.9-1.el6.noarch (foreman)

           Requires: rubygem(rest-client) >= 1.6.1

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

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

#


On Monday, December 30, 2013 3:22:07 PM UTC-8, Stuart Cracraft wrote:

> I would take any reasonable console 
> as long as it has a very visual operation and is trivial to install. 
>
> Dashboard definitely is not the latter 
> in my 'umble opinion. 
>
> On Dec 30, 2013, at 3:17 PM, Felix Frank <[email protected]> 
> wrote: 
>
> >>> 3. What can you rule out as possible causes by now? 
> >> 
> >> ++ While I appreciate this approach, I don't think it will help. I 
> followed as much 
> >> ++ as possible with: 
> >> 
> >>  http://docs.puppetlabs.com/dashboard/manual/1.2/bootstrapping.html 
> >> 
> >> but it blows up at Preparing Schema. 
> > 
> > That sounds like useful info. I hope someone can help you from there - 
> > never played with dashboard myself. 
> > 
> >>> There may be other aspects that don't spring to my mind right now. I 
> >>> recommend reviewing the community guideline. 
> >> 
> >> ++ Be glad to. Where is it posted? 
> > 
> > http://docs.puppetlabs.com/community/community_guidelines.html 
> > 
> > Regards 
> > 
> > -- 
> > 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/XYf9pNGRVmY/unsubscribe. 
> > To unsubscribe from this group and all its topics, send an email to 
> [email protected]. 
> > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/puppet-users/52C1FF22.8000308%40Alumni.TU-Berlin.de.
>  
>
> > 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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/538cbfc4-234c-42d7-a6d2-00635a16d931%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to