[foreman-users] Katello and Errata updates

2017-03-02 Thread Lachlan Musicman 
Hola,

When one ticks off an Errata, a minor version of the Content View is
created (see att image).

How are they stored on the filesystem? Is it ok to delete any of the
versions an just keep the most recent?

For eg, if I make version 3.0 and then over a month there are 4 errata
updates, taking us to 3.4.

Can I delete the versions 3.1, 3.2 and 3.3? Can I delete version 3.0?

Are minor versions stored as a diff or as a snapshot of the whole CV?

cheers
L.
--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] CentOS foreman 1.12.4 puppet 3.7.x best Upgrade Procedure to puppet 4.x

2017-03-02 Thread Lachlan Musicman 
The recommended steps in the docs are what I followed

https://theforeman.org/plugins/katello/3.2/upgrade/puppet.html


cheers
L.

--
The most dangerous phrase in the language is, "We've always done it this
way."

- Grace Hopper

On 2 March 2017 at 22:53, Karsten Horsmann  wrote:

> Hello List,
>
> i prepare my upgrade path to Puppet 4.x and i figure out the following
> steps:
>
> * Fresh new CentOS 7 Installation (because CentOS 6 is not longer
> supported by foreman)
> * Get my data from my old Installation to the new one
> * Get to the latest puppet 3.8.x version, enable future parse and see
> whats broken
> * Upgrade to the latest Foreman Version
> * Switch from passenger to puppet-server (java based) 1.xx in puppet 3.8.x
>
> Is there anybody out there, that can me hint to an good ressource for best
> upgrade/migrate strategy
> from 3.x to 4.x with an Foreman Setup? Would be a huge help in that kind
> of setup.
>
> And to make it even worst, i use puppetdb also.
>
> Kind Regards
> Karsten Horsmann
>
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Compatibility vmware 6.5

2017-03-02 Thread Robert Foreman 
Did you ever get an answer to this question? We are about to do the same 
thing. It looks like everything should work. We have the new vcsa 
configured as a new compute resource, but until we actually make the esx 
cut-over and see how things end up I'm still a little nervous. I am 
assuming we'll just need to re-associate the VM's.

On Wednesday, January 11, 2017 at 4:21:30 AM UTC-5, Vainqueur Tony-greg 
wrote:
>
> We are currently using foreman for vm provisioning on our vmware infra which 
> is in version 6.0.
> My question is: Is there an impact or things to change if we upgrade the 
> infra vmware to 6.5 (vcenter + esxi)?
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Recommendations for products with discovered repositories and subscriptions for content hosts

2017-03-02 Thread Tomas Hajek 
Andrew,
  I did read over you post in that thread and it was very helpful. I think
even though we only have a couple hundred servers there are very few that
are actually alike I think your methodology probably fits fairly well but I
also like Rich's suggestion of using multiple activation keys.  I was
wondering about the shear number of activation keys that we would wind up
with and I suppose automating that might help, that appears to be what you
did base on your note about building the Activation Keys pragmatically.  Do
you use multiple activation keys, I'm somewhat assuming not based on you
example of AK__ and AK___?
thanks again,
 -Tomas

On Wed, Mar 1, 2017 at 9:24 PM, Andrew Schofield 
wrote:

> Tomas - I'd read that whole thread. I have a post in there too which
> explains my view of the world - it works well for our (large (20k+), multi
> region, multi user) setup and takes a very structured approach. Its
> probably overkill for a few hundred servers.
>
> On Monday, February 27, 2017 at 11:54:16 AM UTC-5, Jason B. Nance wrote:
>>
>> Hi Tomas,
>>
>> Check out my reply in the following thread:
>>
>> https://groups.google.com/d/msg/foreman-users/q_Qr9sg2PJs/XU
>> N8YEeMDAAJ
>>
>> It includes my reasoning for using CVs and a bit of insight into why I
>> structured how I did.
>>
>> If you have further questions don't hesitate to ask.
>>
>> j
>>
>>
>>
>> --
>> *From: *"Tomas Hajek" 
>> *To: *"Foreman Users" 
>> *Sent: *Monday, February 27, 2017 10:41:46 AM
>> *Subject: *Re: [foreman-users] Recommendations for products with
>> discovered repositories and subscriptions for content hosts
>>
>> Good question.
>>I'm not actively trying to avoid using Content Views just thought I
>> could get a particular issue resolved without them.  I am still trying to
>> wrap my head around all of the various organizational structures (Products,
>> Content Views, Activation Keys, Host Groups, Host Collections, Config
>> Groups, etc.) and determine what fits best for various use cases and how
>> best to structure them for our environment.
>>Based on training I am going through right now (RH403 Satellite 6
>> Administration) I thought one of my use cases would be fairly simple and
>> straight forward to accomplish.  Basically, I have about 200 RHEL 6 systems
>> that I need to transition from RHN Classic subscriptions to
>> subscription-manager but with the caveat that most of these systems pull in
>> non-Red Hat repositories and I wanted to get them into Satellite instead of
>> sending each system out through a Squid proxy.  So, Instead of going from
>> RHN Classic to RHSM and then to Satellite I thought I would setup the
>> existing repositories that we use as products in Satellite, unregister from
>> RHN Classic, and register with Satellite as Content Hosts and basically be
>> done (without having to deal with Life Cycle Environments and promoting
>> Content Views, etc. as that brings a whole additional level of complexity).
>>   If my use case was to only use Red Hat repositories then I think this
>> would work as demonstrated in the training course but as with most things
>> it got complicated quickly.  It seemed like Products and repositories were
>> the basic unit set to work with so I wanted to start there.  I kind of
>> thought that the discovery mechanism and resultant exposure to clients
>> would work similar to the .repo files with $releasever and $basearch but
>> it's obviously more complicated than that.
>>
>> Would you mind sharing generally how you organized your products and
>> content views (or any other structures) to work with non-Red Hat
>> repositories?  Are there any good references that you found on how to
>> organize a Satellite installation?  I've gone through a number of youTube
>> videos and some presentations, I thought that the following (
>> https://www.youtube.com/watch?v=9i9Fem9f_I0 - Managing your content with
>> Red Hat Satellite 6) was somewhat helpful but I'd like a little more
>> detail.  The RH training is somewhat useful but only if you already have a
>> good idea of how you want to structure and lay everything out and just want
>> to know what commands to execute.
>>
>> Thanks again and I really appreciate all the feedback!
>>
>> On Mon, Feb 27, 2017 at 9:19 AM, 'Jason B. Nance' via Foreman users <
>> forema...@googlegroups.com> wrote:
>>
>>> Tomas,
>>>
>>> Are you trying to avoid using Content Views?  That is how I deal with
>>> this situation.  My products are divvied up by vendor but my Content Views
>>> are EL version-specific.
>>>
>>> Regards,
>>>
>>> j
>>>
>>>
>>> --
>>> *From: *"Tomas Hajek" 
>>> *To: *"Foreman Users" 
>>> *Sent: *Friday, February 24, 2017 6:25:37 PM
>>> *Subject: *[foreman-users] Recommendations for products with discovered
>>> repositories and subscriptions for content hosts
>>>

[foreman-users] ldap:refresh_usergroups is taking more time

2017-03-02 Thread Unnikrishnan K 
Hello,

I have configured LDAP (Active directory) in Foreman and authentication is
working fine. User is automatically created in Foreman once authenticated
by LDAP but it is taking long time (nearly 2 hrs) to get the user is added
to the user group, which is mapped to LDAP external group.

* Please find the log details below*


*2017-01-05T13:16:56 [app] [I] Started PUT
"/external_usergroups/Prod_Users/refresh" for 172.16.11.8 at 2017-01-05
13:16:56 +*

*2017-01-05T13:16:56 [app] [I] Processing by
ExternalUsergroupsController#refresh as HTML*

*2017-01-05T13:16:56** [app] [I]   Parameters:
{"authenticity_token"=>"r+/ltjhwdQk13RP/N8tt45gj5n4drrVXSddwe/aaoyE=",
"id"=>"Prod_Users"}*

*2017-01-05T15:01:47** [app] [I] Completed 302 Found in 7162113ms
(ActiveRecord: 49.9ms)*

Foreman version is 1.11

Could you please suggest?

Best Regards,
Unnikrishnan K

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Re: Katello 3.2 > 3.3 upgrade with custom signed ssl certs breaks pulp

2017-03-02 Thread Edward Clay 
I ended up restoring from backup to the previous version 3.2 and things are 
working.  I would like very much to figure out how to revert back to self 
signed ssl certs and do away with using the 3rd party signed ones.  Since I 
ran foreman-installer with some options to use the 3rd party signed ssl 
certs you would think this would be a simple task.

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Foreman 1.14.2 bug fix release

2017-03-02 Thread Dominic Cleal 
Foreman 1.14.2 is now out with bug fixes for some provisioning features,
API responses and for Puppet class imports, among others.

Please see the release notes for the full list of changes:
https://theforeman.org/manuals/1.14/index.html#Releasenotesfor1.14.2


Information
===
For installation or upgrade instructions, see:

Installation quick start:
https://theforeman.org/manuals/1.14/quickstart_guide.html

Upgrade instructions:
https://theforeman.org/manuals/1.14/index.html#3.6Upgrade

Release notes:
https://theforeman.org/manuals/1.14/index.html#Releasenotesfor1.14

Do take note of the upgrade warnings and deprecations in this release:
https://theforeman.org/manuals/1.14/index.html#Upgradewarnings


Downloads
=
Packages may be found in the 1.14 directories on both deb.foreman.org
and yum.theforeman.org, and tarballs are on downloads.theforeman.org.

The GPG key used for RPMs and tarballs has the following fingerprint:
  AF74 2A91 BF76 6333 E9FF 5EAA BFE5 1511 F06D 8950
  (https://theforeman.org/security.html#GPGkeys)


Bug reporting
=
If you come across a bug, please file it and note the version of Foreman
that you're using in the report.

Foreman: http://projects.theforeman.org/projects/foreman/issues/new
Proxy: http://projects.theforeman.org/projects/smart-proxy/issues/new
Installer: http://projects.theforeman.org/projects/puppet-foreman/issues/new

-- 
Dominic Cleal
domi...@cleal.org


-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: [foreman-users] Officially Unofficial Foreman 1.13 on EL6 Now Available

2017-03-02 Thread James Denton 
Hi Ohad

Yes I had that package and ive removed it - the error has now gone! Can I 
ask why? 

On Thursday, March 2, 2017 at 2:33:36 PM UTC, ohad wrote:
>
>
>
> On Thu, Mar 2, 2017 at 4:29 PM, James Denton  > wrote:
>
>> Hi Ohad
>>
>> I dont have a Foreman-setup package, there is the foreman-installer 
>> package though...
>>
>
> how about tfm-rubygem-foreman_setup ?
>
>>
>> On Thursday, March 2, 2017 at 2:03:37 PM UTC, ohad wrote:
>>>
>>>
>>>
>>> On Wed, Mar 1, 2017 at 1:27 PM, James Denton  wrote:
>>>
 Hi All

 I have attempted to update Foreman from 1.12 to 1.13 with the repos 
 provided by Eric/Greg however I get the following error after install:

 can you try removing the foreman-setup package? 
>>>
>>> Ohad 
>>>
 ForemanSetup::Provisioner is using attr_accessible so must either be 
 converted to strong parameters, or add the protected_attributes gem 
 (RuntimeError)
   /usr/share/foreman/config/initializers/active_record_extensions.rb:21:in 
 `attr_accessible'
   
 /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:8:in
  `'
   
 /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:4:in
  `'
   
 /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:3:in
  `'
   
 /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
  `require'
   
 /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
  `require'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
  `block in require'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:240:in
  `load_dependency'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
  `require'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:360:in
  `require_or_load'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:317:in
  `depend_on'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:233:in
  `require_dependency'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:472:in
  `block (2 levels) in eager_load!'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
  `each'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
  `block in eager_load!'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
  `each'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
  `eager_load!'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:346:in
  `eager_load!'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
  `each'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
  `block in '
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
  `instance_exec'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
  `run'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
  `block in run_initializers'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:226:in `block in 
 tsort_each'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:348:in `block (2 levels) 
 in each_strongly_connected_component'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:429:in 
 `each_strongly_connected_component_from'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:347:in `block in 
 each_strongly_connected_component'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `each'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `call'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in 
 `each_strongly_connected_component'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:224:in `tsort_each'
   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:203:in `tsort_each'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
  `run_initializers'
   
 /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in

Re: [foreman-users] Officially Unofficial Foreman 1.13 on EL6 Now Available

2017-03-02 Thread Ohad Levy 
On Thu, Mar 2, 2017 at 4:29 PM, James Denton  wrote:

> Hi Ohad
>
> I dont have a Foreman-setup package, there is the foreman-installer
> package though...
>

how about tfm-rubygem-foreman_setup ?

>
> On Thursday, March 2, 2017 at 2:03:37 PM UTC, ohad wrote:
>>
>>
>>
>> On Wed, Mar 1, 2017 at 1:27 PM, James Denton  wrote:
>>
>>> Hi All
>>>
>>> I have attempted to update Foreman from 1.12 to 1.13 with the repos
>>> provided by Eric/Greg however I get the following error after install:
>>>
>>> can you try removing the foreman-setup package?
>>
>> Ohad
>>
>>> ForemanSetup::Provisioner is using attr_accessible so must either be 
>>> converted to strong parameters, or add the protected_attributes gem 
>>> (RuntimeError)
>>>   /usr/share/foreman/config/initializers/active_record_extensions.rb:21:in 
>>> `attr_accessible'
>>>   
>>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:8:in
>>>  `'
>>>   
>>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:4:in
>>>  `'
>>>   
>>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:3:in
>>>  `'
>>>   
>>> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>>>  `require'
>>>   
>>> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>>>  `require'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>>>  `block in require'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:240:in
>>>  `load_dependency'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>>>  `require'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:360:in
>>>  `require_or_load'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:317:in
>>>  `depend_on'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:233:in
>>>  `require_dependency'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:472:in
>>>  `block (2 levels) in eager_load!'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>>>  `each'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>>>  `block in eager_load!'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>>>  `each'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>>>  `eager_load!'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:346:in
>>>  `eager_load!'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>>>  `each'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>>>  `block in '
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>>>  `instance_exec'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>>>  `run'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
>>>  `block in run_initializers'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:226:in `block in 
>>> tsort_each'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:348:in `block (2 levels) 
>>> in each_strongly_connected_component'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:429:in 
>>> `each_strongly_connected_component_from'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:347:in `block in 
>>> each_strongly_connected_component'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `each'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `call'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in 
>>> `each_strongly_connected_component'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:224:in `tsort_each'
>>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:203:in `tsort_each'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
>>>  `run_initializers'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in
>>>  `initialize!'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>>>  `public_send'
>>>   
>>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>>>  `method_missing'
>>>

Re: [foreman-users] Officially Unofficial Foreman 1.13 on EL6 Now Available

2017-03-02 Thread James Denton 
Hi Ohad

I dont have a Foreman-setup package, there is the foreman-installer package 
though...

On Thursday, March 2, 2017 at 2:03:37 PM UTC, ohad wrote:
>
>
>
> On Wed, Mar 1, 2017 at 1:27 PM, James Denton  > wrote:
>
>> Hi All
>>
>> I have attempted to update Foreman from 1.12 to 1.13 with the repos 
>> provided by Eric/Greg however I get the following error after install:
>>
>> can you try removing the foreman-setup package? 
>
> Ohad 
>
>> ForemanSetup::Provisioner is using attr_accessible so must either be 
>> converted to strong parameters, or add the protected_attributes gem 
>> (RuntimeError)
>>   /usr/share/foreman/config/initializers/active_record_extensions.rb:21:in 
>> `attr_accessible'
>>   
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:8:in
>>  `'
>>   
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:4:in
>>  `'
>>   
>> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:3:in
>>  `'
>>   
>> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>>  `require'
>>   
>> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>>  `require'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>>  `block in require'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:240:in
>>  `load_dependency'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>>  `require'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:360:in
>>  `require_or_load'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:317:in
>>  `depend_on'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:233:in
>>  `require_dependency'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:472:in
>>  `block (2 levels) in eager_load!'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>>  `each'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>>  `block in eager_load!'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>>  `each'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>>  `eager_load!'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:346:in
>>  `eager_load!'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>>  `each'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>>  `block in '
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>>  `instance_exec'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>>  `run'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
>>  `block in run_initializers'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:226:in `block in tsort_each'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:348:in `block (2 levels) in 
>> each_strongly_connected_component'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:429:in 
>> `each_strongly_connected_component_from'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:347:in `block in 
>> each_strongly_connected_component'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `each'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `call'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in 
>> `each_strongly_connected_component'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:224:in `tsort_each'
>>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:203:in `tsort_each'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
>>  `run_initializers'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in
>>  `initialize!'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>>  `public_send'
>>   
>> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>>  `method_missing'
>>   /usr/share/foreman/config/environment.rb:5:in `'
>>   
>> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>>  `require'
>>   
>> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>>

[foreman-users] Re: Puppet 4 and foreman

2017-03-02 Thread anothermailbox49 
I think I was not able to present the question in right manner. I already 
had Puppet server running (Puppet 4). I did that with foreman-installer 
command. However, the foreman Puppet module was missing. It was my 
understanding that the Puppet module comes from foreman-installer itself. 
Apparently that is not the case. 

I installed it with 'puppet module install theforeman-foreman' and then 
things started to work. 

The error was:

Error: Could not retrieve catalog from remote server: Error 500 on SERVER: 
Server Error: Evaluation Error: Error while evaluating a Function Call, 
Could not find class ::foreman for  at 
/etc/puppetlabs/code/environments/production/custom/profiles/manifests/puppetserver.pp:2:3
 
on node 

Thanks for the help everybody!

On Wednesday, March 1, 2017 at 8:27:38 PM UTC+5:30, anotherm...@gmail.com 
wrote:
>
>
> Hi all, 
>
> With Puppet 3, the way I used to implement Puppet+foreman is to install 
> the foreman repository and using foreman-installer, which installed the 
> Puppet server. I am wondering what is the best practice of using foreman 
> and Puppet 4. Do you suggest installing foreman with foreman-installer or 
> using Puppet modules? 
>
> Sorry if this is a vague question but I am trying to understand whether 
> there is any best practice recommendations on installing/maintaining 
> foreman with Puppet? 
>
> Thanks, 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] Officially Unofficial Foreman 1.13 on EL6 Now Available

2017-03-02 Thread Ohad Levy 
On Wed, Mar 1, 2017 at 1:27 PM, James Denton  wrote:

> Hi All
>
> I have attempted to update Foreman from 1.12 to 1.13 with the repos
> provided by Eric/Greg however I get the following error after install:
>
> can you try removing the foreman-setup package?

Ohad

> ForemanSetup::Provisioner is using attr_accessible so must either be 
> converted to strong parameters, or add the protected_attributes gem 
> (RuntimeError)
>   /usr/share/foreman/config/initializers/active_record_extensions.rb:21:in 
> `attr_accessible'
>   
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:8:in
>  `'
>   
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:4:in
>  `'
>   
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:3:in
>  `'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>  `block in require'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:240:in
>  `load_dependency'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>  `require'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:360:in
>  `require_or_load'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:317:in
>  `depend_on'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:233:in
>  `require_dependency'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:472:in
>  `block (2 levels) in eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>  `each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>  `block in eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>  `each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>  `eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:346:in
>  `eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>  `each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>  `block in '
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>  `instance_exec'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>  `run'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
>  `block in run_initializers'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:226:in `block in tsort_each'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:348:in `block (2 levels) in 
> each_strongly_connected_component'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:429:in 
> `each_strongly_connected_component_from'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:347:in `block in 
> each_strongly_connected_component'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `each'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `call'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in 
> `each_strongly_connected_component'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:224:in `tsort_each'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:203:in `tsort_each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
>  `run_initializers'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in
>  `initialize!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>  `public_send'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>  `method_missing'
>   /usr/share/foreman/config/environment.rb:5:in `'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   config.ru:3:in `block in '
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/rack-1.6.2/lib/rack/builder.rb:55:in
>  `instance_eval'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/rack-1.6.2/lib/rack/builder.rb:55:in
>  `initialize'
>   config.ru:1:in `new'
>

Re: [foreman-users] Officially Unofficial Foreman 1.13 on EL6 Now Available

2017-03-02 Thread James Denton 
Can anyone assist with this or perhaps had a similar error?

On Wednesday, March 1, 2017 at 11:27:20 AM UTC, James Denton wrote:
>
> Hi All
>
> I have attempted to update Foreman from 1.12 to 1.13 with the repos 
> provided by Eric/Greg however I get the following error after install:
>
> ForemanSetup::Provisioner is using attr_accessible so must either be 
> converted to strong parameters, or add the protected_attributes gem 
> (RuntimeError)
>   /usr/share/foreman/config/initializers/active_record_extensions.rb:21:in 
> `attr_accessible'
>   
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:8:in
>  `'
>   
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:4:in
>  `'
>   
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_setup-4.0.0/app/models/foreman_setup/provisioner.rb:3:in
>  `'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>  `block in require'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:240:in
>  `load_dependency'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:274:in
>  `require'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:360:in
>  `require_or_load'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:317:in
>  `depend_on'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:233:in
>  `require_dependency'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:472:in
>  `block (2 levels) in eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>  `each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:471:in
>  `block in eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>  `each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:469:in
>  `eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:346:in
>  `eager_load!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>  `each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application/finisher.rb:56:in
>  `block in '
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>  `instance_exec'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:30:in
>  `run'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:55:in
>  `block in run_initializers'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:226:in `block in tsort_each'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:348:in `block (2 levels) in 
> each_strongly_connected_component'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:429:in 
> `each_strongly_connected_component_from'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:347:in `block in 
> each_strongly_connected_component'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `each'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in `call'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:345:in 
> `each_strongly_connected_component'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:224:in `tsort_each'
>   /opt/rh/rh-ruby22/root/usr/share/ruby/tsort.rb:203:in `tsort_each'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/initializable.rb:54:in
>  `run_initializers'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/application.rb:352:in
>  `initialize!'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>  `public_send'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/railtie.rb:194:in
>  `method_missing'
>   /usr/share/foreman/config/environment.rb:5:in `'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   
> /opt/rh/rh-ruby22/root/usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in
>  `require'
>   config.ru:3:in `block in '
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/rack-1.6.2/lib/rack/builder.rb:55:in
>  `instance_eval'
>   
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/rack-1.6.2/lib/rack/builder.rb:55:in
>  `initialize'
>   config.ru:1:in `new'
>

[foreman-users] CentOS foreman 1.12.4 puppet 3.7.x best Upgrade Procedure to puppet 4.x

2017-03-02 Thread Karsten Horsmann 
Hello List,

i prepare my upgrade path to Puppet 4.x and i figure out the following 
steps:

* Fresh new CentOS 7 Installation (because CentOS 6 is not longer supported 
by foreman)
* Get my data from my old Installation to the new one
* Get to the latest puppet 3.8.x version, enable future parse and see whats 
broken
* Upgrade to the latest Foreman Version
* Switch from passenger to puppet-server (java based) 1.xx in puppet 3.8.x

Is there anybody out there, that can me hint to an good ressource for best 
upgrade/migrate strategy
from 3.x to 4.x with an Foreman Setup? Would be a huge help in that kind of 
setup.

And to make it even worst, i use puppetdb also.

Kind Regards
Karsten Horsmann



-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

[foreman-users] Foreman Discovery 8.0.1 release

2017-03-02 Thread Lukas Zapletal 
Hello,

better later then never, I am finally announcing 8.0.1 bugfix minor
release which contains two important changes:

Fixes #18106 - Attribute Error when provisioning with Katello plugin installed
Fixes #16890 - Prevent discovery of managed hosts

It took a little bit longer to release this due to various things
namely FOSDEM, recovery and my struggle with building process. I
highly recommend to update to all of users because the #16890 bug is
causing discovered hosts in undeletable state and maintainance task
must be performed to delete them (it only happens if MAC address is
already used as managed host - re-discovery).

-- 
Later,
  Lukas @lzap Zapletal

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

Re: [foreman-users] katello 3.3 search doesn't work?

2017-03-02 Thread Cristian Falcas 
The machine has 32 GB.

We run here tomcat (candlepin), puppetdb, foreman and postgresql db.

On Thu, Mar 2, 2017 at 12:24 AM, John Mitsch  wrote:

> Cristian,
>
> how much memory do you have on the machine you are running katello/foreman
> on?
>
> -John
>
> John Mitsch
> Red Hat Engineering
> (860)-967-7285
> irc: jomitsch
>
> On Wed, Mar 1, 2017 at 7:02 AM, Cristian Falcas 
> wrote:
>
>> Hi,
>>
>> I'm trying to see the hosts in Error state from the Dashboard.
>>
>> When I click the Error from Host Configuration Chart, the new page never
>> loads (the same happens with Active hosts).
>>
>> This is the url that it's executed is:
>>
>> https://puppet.company.net/hosts?utf8=%E2%9C%93=last_
>> report+%3E+%2214405+minutes+ago%22+and+%28status.failed+%
>> 3E+0+or+status.failed_restarts+%3E+0%29+and+status.enabled+%3D+true
>>
>> Eventually foreman is killed by the kernel oom:
>>
>> 2017-03-01T06:59:05.768945-05:00 puppet.company.net kernel: Out of
>> memory: Kill process 14812 (ruby) score 300 or sacrifice child
>>
>> There should be ~ 30 hosts in Error and ~ 200 in Active.
>> "Out Of Sync" hosts is working, but we have only 2 hosts in this status.
>>
>> Are there any known issues about this?
>>
>> Thank you,
>> Cristian
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Foreman users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to foreman-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/foreman-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to foreman-users+unsubscr...@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.