Re: [foreman-users] Import Puppet Classes giving No Method Error

2016-11-15 Thread Tomer Brisker 
Hi Amrit,

It looks like one of the database migrations did not run correctly, please
execute 'foreman-rake db:migrate' on the server and try again.

On Wed, Nov 16, 2016 at 9:04 AM, Amrit Atmajit 
wrote:

> Hi,
>
> I am using Puppet version 4.7.0 and Foreman version 1.12.4.
> After immediate installation of foreman-installer, on-click of Configure
> -> Puppet Classes I am getting the following error and not allowing me
> import puppet classes through foreman UI.
>
> 
> =
>
> *Oops, we're sorry but something went wrong *undefined method
> `total_hosts' for #
> --
> Back 
>  Documentation
> 
>
> *NoMethodError*
> *undefined method `total_hosts' for #*
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activemodel-4.
> 2.5.1/lib/active_model/attribute_methods.rb:433:in `method_missing'
> /usr/share/foreman/app/views/puppetclasses/index.html.erb:28:in `block in
> _app_views_puppetclasses_index_html_erb___2314841949541106154_
> 70133877292380'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-
> 4.2.5.1/lib/active_record/relation/delegation.rb:46:in `each'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-
> 4.2.5.1/lib/active_record/relation/delegation.rb:46:in `each'
> /usr/share/foreman/app/views/puppetclasses/index.html.erb:19:in
> `_app_views_puppetclasses_index_html_erb___2314841949541106154_
> 70133877292380'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/template.rb:145:in `block in render'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/notifications.rb:166:in `instrument'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/template.rb:333:in `instrument'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/template.rb:143:in `render'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/template_renderer.rb:54:in `block (2
> levels) in render_template'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/abstract_renderer.rb:39:in `block in
> instrument'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/notifications.rb:164:in `block in instrument'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/notifications/instrumenter.rb:20:in
> `instrument'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/notifications.rb:164:in `instrument'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/abstract_renderer.rb:39:in `instrument'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/template_renderer.rb:53:in `block in
> render_template'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/template_renderer.rb:61:in
> `render_with_layout'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/template_renderer.rb:52:in
> `render_template'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/template_renderer.rb:14:in `render'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/renderer.rb:46:in `render_template'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/renderer/renderer.rb:27:in `render'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/rendering.rb:100:in `_render_template'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.
> 2.5.1/lib/action_controller/metal/streaming.rb:217:in `_render_template'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.
> 2.5.1/lib/action_view/rendering.rb:83:in `render_to_body'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.
> 2.5.1/lib/action_controller/metal/rendering.rb:32:in `render_to_body'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.
> 2.5.1/lib/action_controller/metal/renderers.rb:37:in `render_to_body'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.
> 2.5.1/lib/abstract_controller/rendering.rb:25:in `render'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.
> 2.5.1/lib/action_controller/metal/rendering.rb:16:in `render'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.
> 2.5.1/lib/action_controller/metal/instrumentation.rb:44:in `block (2
> levels) in render'
> /opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-
> 4.2.5.1/lib/active_support/core_ext/benchmark.rb:12:in `block in ms'
> /opt/rh/rh-ruby22/root/usr/share/ruby/benchmark.rb:303:in `realtime'
> 
> 
> ==

[foreman-users] Import Puppet Classes giving No Method Error

2016-11-15 Thread Amrit Atmajit 
Hi,

I am using Puppet version 4.7.0 and Foreman version 1.12.4. 
After immediate installation of foreman-installer, on-click of Configure -> 
Puppet Classes I am getting the following error and not allowing me import 
puppet classes through foreman UI.

=

*Oops, we're sorry but something went wrong *undefined method `total_hosts' 
for #
--
Back 
 Documentation 


*NoMethodError*
*undefined method `total_hosts' for #*
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activemodel-4.2.5.1/lib/active_model/attribute_methods.rb:433:in
 
`method_missing'
/usr/share/foreman/app/views/puppetclasses/index.html.erb:28:in `block in 
_app_views_puppetclasses_index_html_erb___2314841949541106154_70133877292380'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/relation/delegation.rb:46:in
 
`each'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/relation/delegation.rb:46:in
 
`each'
/usr/share/foreman/app/views/puppetclasses/index.html.erb:19:in 
`_app_views_puppetclasses_index_html_erb___2314841949541106154_70133877292380'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/template.rb:145:in
 
`block in render'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:166:in
 
`instrument'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/template.rb:333:in
 
`instrument'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/template.rb:143:in
 
`render'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/template_renderer.rb:54:in
 
`block (2 levels) in render_template'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/abstract_renderer.rb:39:in
 
`block in instrument'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in
 
`block in instrument'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/notifications/instrumenter.rb:20:in
 
`instrument'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in
 
`instrument'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/abstract_renderer.rb:39:in
 
`instrument'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/template_renderer.rb:53:in
 
`block in render_template'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/template_renderer.rb:61:in
 
`render_with_layout'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/template_renderer.rb:52:in
 
`render_template'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/template_renderer.rb:14:in
 
`render'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/renderer.rb:46:in
 
`render_template'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/renderer.rb:27:in
 
`render'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/rendering.rb:100:in
 
`_render_template'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_controller/metal/streaming.rb:217:in
 
`_render_template'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/rendering.rb:83:in
 
`render_to_body'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_controller/metal/rendering.rb:32:in
 
`render_to_body'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_controller/metal/renderers.rb:37:in
 
`render_to_body'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/abstract_controller/rendering.rb:25:in
 
`render'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_controller/metal/rendering.rb:16:in
 
`render'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionpack-4.2.5.1/lib/action_controller/metal/instrumentation.rb:44:in
 
`block (2 levels) in render'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/core_ext/benchmark.rb:12:in
 
`block in ms'
/opt/rh/rh-ruby22/root/usr/share/ruby/benchmark.rb:303:in `realtime'


=

Can anyone help me to resolve this issue?

Thanks and Regards,
Amrit

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

[foreman-users] Re: [Katello] How should RedHat products be accessed behind Corporate firewalls & w/ a proxy?

2016-11-15 Thread Andrew Schofield 
We are using Satellite 6.2 behind our proxy servers without issue. The 
settings which Sean mentions should get you out of trouble.

-- 
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: [Foreman] Branding foreman

2016-11-15 Thread Michael Griffin 
Take a look at this plugin. It might be what you're looking for:

https://github.com/jcmcken/foreman_custom_banner

On Tuesday, November 15, 2016 at 5:37:46 PM UTC-5, Alan Evans wrote:
>
> A little googling around shows some "branding" tickets around 
> katello/satellite but I wonder if there is a way to brand it with my 
> company?  My company is big on splashing our logo over products we use. 
>  Some have ways to add images or custom text or the like.  I can't see a 
> good way to do that w/ foreman.
>
> I _could_ go in and replace files in /var/lib/foreman/public/assets but 
> that is not very upgrade friendly.  I was looking at 
> views/home/_topbar.html.erb and the rails image_tag looks to be the guy I 
> need.  Is there a way in rails to specify multiple locations to look for 
> assets?  Maybe assets/custom/ then in assets?
>
> Also would anyone be interested in a feature to customize the branding 
> text?  In particular?
>
> 
> <%= link_to "Foreman", main_app.root_path %>
>
> Maybe add a setting branding_title and change the erb.
>
> 
> <%= link_to Setting[:branding_title] || "Foreman", 
> main_app.root_path %>
>
> Would this be useful for anyone?
>
> Regards,
> -Alan
>
>

-- 
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] Branding foreman

2016-11-15 Thread Alan Evans 
A little googling around shows some "branding" tickets around 
katello/satellite but I wonder if there is a way to brand it with my 
company?  My company is big on splashing our logo over products we use. 
 Some have ways to add images or custom text or the like.  I can't see a 
good way to do that w/ foreman.

I _could_ go in and replace files in /var/lib/foreman/public/assets but 
that is not very upgrade friendly.  I was looking at 
views/home/_topbar.html.erb and the rails image_tag looks to be the guy I 
need.  Is there a way in rails to specify multiple locations to look for 
assets?  Maybe assets/custom/ then in assets?

Also would anyone be interested in a feature to customize the branding 
text?  In particular?


<%= link_to "Foreman", main_app.root_path %>

Maybe add a setting branding_title and change the erb.


<%= link_to Setting[:branding_title] || "Foreman", 
main_app.root_path %>

Would this be useful for anyone?

Regards,
-Alan

-- 
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] Unable to view details for content host(s)

2016-11-15 Thread Sean O'Keeffe 
Is tomcat running? Check "katello-service status".

Sean

On Tue, 15 Nov 2016 at 14:56,  wrote:

> When I go to view details on a content host (ie, /content_hosts/:id/info),
> I get the following stack trace in the logs, and an error message saying
> "Something went wrong when retrieving the resource"
>
> Is there anything I can do to debug why this is happening?
>
> https://gist.github.com/NeilHanlon/204ff19d2803a8ff0a939cf437280bea
>
> --
> 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] Katello 3.2 (Malt Liquor) released

2016-11-15 Thread John Mitsch 
We are happy to announce the release of Katello 3.2 (Malt Liquor).

One notable change in 3.2 is the support of Puppet 4. More info about
upgrading to Puppet 4 can be found here:

http://www.katello.org/docs/nightly/upgrade/puppet.html

A list of the changes in Katello 3.2 is in our release notes:
http://www.katello.org/docs/3.2/release_notes/release_notes.html

There is one notable issue with capsule installs in 3.2 documented here:
http://projects.theforeman.org/issues/16653
The work around is to re-run the capsule installer. We are working on a
permanent fix and decided to not let this bug delay the release.

Installation or Upgrade
==

For installation, please see the instructions at:

  Server:  http://www.katello.org/docs/3.2/installation/index.html
  Capsule:  http://www.katello.org/docs/3.2/installation/capsule.html

For those testing upgrades, please use the instructions below and file
any issues you encounter. Please note that there are separate upgrade
instructions for the Katello server and Capsules:

  Server:  http://www.katello.org/docs/3.2/upgrade/index.html
  Capsule:  http://www.katello.org/docs/3.2/upgrade/capsule.html

Bug reporting
===
If you come across a bug in your testing, please file it and note the
version of Katello that you're using in the report and set the release
to 3.2.0.

  http://projects.theforeman.org/projects/katello/issues/new

John Mitsch
Red Hat Engineering
(860)-967-7285
irc: jomitsch

-- 
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] How should RedHat products be accessed behind Corporate firewalls & w/ a proxy?

2016-11-15 Thread Sean O'Keeffe 
Have you set these options using foreman-installer?

--katello-proxy-password  Proxy password for authentication
(default: nil)
--katello-proxy-port  Port the proxy is running on (default:
nil)
--katello-proxy-url   URL of the proxy server (default: nil)
--katello-proxy-username  Proxy username for authentication
(default: nil)

On Tue, Nov 15, 2016 at 10:23 AM, JC  wrote:

> I have previously imported (the manifest) and used Red Hat products in
> Katello 2.4.*.  I've recently built a Katello 3.1 server and would like to
> do the same.
>
> The manifest imports, but trying to select products returns:
>
> getaddrinfo: Temporary failure in name resolution
>
> I've seen this before (and in fact asked
> 
> about it before), but I think it just 'went away'.
>
> Both Katello servers sit behind Corporate firewalls and use a Corporate
> proxy.  The local DNS source doesn't know about public domains (so can't
> help with cdn.redhat.com).
>
> When syncing the existing 2.4 Red Hat repositories, all requests
> successfully use the details provided in:
>
> /etc/pulp/server/plugins.conf.d/yum_importer.json
>
> But browsing the Red Hat product list now returns the same cdn.redhat.com
> lookup failure as the 3.1 server.
>
> I've tried creating a host file entry for one of the public IPs for that
> site, but that naturally returns:
>
> Connection refused - connect(2)
>
> As that address is not reachable; this is prevented by the firewalls.
>
> I've tried setting the host file entry for cdn.redhat.com to the IP of
> the proxy, then added a redirect rule in iptables to send the TCP443
> request to the correct port of the proxy, but then I get an SSL error, as
> Katello is expecting a different conversation to the one the proxy wants to
> have.
>
> From what I can tell, there wouldn't be a problem if there wasn't the
> initial DNS lookup and this part solely used the json file.
>
> Can anyone help please?
>
> Cheers.
>
> --
> 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: Puppet agent 4.x upgrade/ installation.

2016-11-15 Thread Akash Kaveti 
Apologies,
Ubuntu Xenial.

On Tuesday, November 15, 2016 at 5:11:35 PM UTC+1, Akash Kaveti wrote:
>
> Hello,
>
> I have foreman 1.12.3 with pupper servers puppet version 4.7.0, but with 
> my current setup, puppet agent 3.8.5 is installing.
> How do I make the new clients installations from foreman should install 
> puppet agent 4.x? 
> I have checked in puppet_setup snippet, but didnt work out.
>
>
> Thank you.
>

-- 
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] Puppet agent 4.x upgrade/ installation.

2016-11-15 Thread Chris Duryee 


On 11/15/2016 11:11 AM, Akash Kaveti wrote:
> Hello,
> 
> I have foreman 1.12.3 with pupper servers puppet version 4.7.0, but with my 
> current setup, puppet agent 3.8.5 is installing.
> How do I make the new clients installations from foreman should install 
> puppet agent 4.x? 
> I have checked in puppet_setup snippet, but didnt work out.
> 
> 
> Thank you.
> 

what OS are the clients?

-- 
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] Puppet agent 4.x upgrade/ installation.

2016-11-15 Thread Akash Kaveti 
Hello,

I have foreman 1.12.3 with pupper servers puppet version 4.7.0, but with my 
current setup, puppet agent 3.8.5 is installing.
How do I make the new clients installations from foreman should install 
puppet agent 4.x? 
I have checked in puppet_setup snippet, but didnt work out.


Thank you.

-- 
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] [Katello] Unable to view details for content host(s)

2016-11-15 Thread nhanlon 
When I go to view details on a content host (ie, /content_hosts/:id/info), 
I get the following stack trace in the logs, and an error message saying 
"Something went wrong when retrieving the resource"

Is there anything I can do to debug why this is happening?

https://gist.github.com/NeilHanlon/204ff19d2803a8ff0a939cf437280bea

-- 
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] OEL 6 hardcoded yum repo

2016-11-15 Thread 'Jason B. Nance' via Foreman users 
Thanks for the info, Klaas!  I wonder if defining an empty UEK4 repo in the 
kickstart would work (like the old MySQL workaround you linked me to).  I'll 
have to give that a try.

j


- Original Message -
From: "Klaas Demter" 
To: foreman-users@googlegroups.com
Sent: Tuesday, November 15, 2016 1:59:45 AM
Subject: Re: [foreman-users] OEL 6 hardcoded yum repo

Hey,
the current community templates should work for oracle linux 
(https://github.com/theforeman/community-templates). I'm not sure about the 
uek4 repository but the way to get rid of the mysql repository during kickstart 
is in this commit: 
https://github.com/theforeman/community-templates/commit/9ec2d99f1de16e4f0640883aeb18a29a2015853e
maybe something simmilar to this will also work for the uek repo. also note 
that there is a disable-uek parameter now: 
https://github.com/theforeman/community-templates/commit/4d62c9bf7f4af989e9f115fa76f8cf7839a62de8


Greetings
Klaas

- Ursprüngliche Mail -
Von: "'Jason B. Nance' via Foreman users" 
An: foreman-users@googlegroups.com
Gesendet: Montag, 14. November 2016 22:25:12
Betreff: [foreman-users] OEL 6 hardcoded yum repo

Hello Everyone,

I've been attempting to kickstart an OEL 6 server off my Katello environment 
and kept getting an error about failing to add a UEK4 repository.  Since there 
is no such repository definition in my provisioning templates / kickstart this 
was very perplexing to me.  After banging my head against the wall for a bit I 
finally mounted the OEL 6 "install.img" and did a grep for UEK4.  This is the 
awesomeness I found:

$ cd /path/to/mounted/install.img
$ grep -r UEK4 *
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:enableUEK4repo = True
usr/lib/anaconda/yuminstall.py:# If we are upgrading we need to check 
for pre-UEK4 kernel
usr/lib/anaconda/yuminstall.py:# if found we do not want to enable the 
UEK4 repo unless it is also installed
usr/lib/anaconda/yuminstall.py:foundUEK4 = False
usr/lib/anaconda/yuminstall.py:log.info("Found UEK4 
modules directory %s" %(dirname))
usr/lib/anaconda/yuminstall.py:foundUEK4 = True
usr/lib/anaconda/yuminstall.py:if not foundUEK4:
usr/lib/anaconda/yuminstall.py:log.info("Found UEK1 kernel 
and no UEK4 kernel, disabling UEK4 repo")
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:if not foundUEK4:
usr/lib/anaconda/yuminstall.py:log.info("Found UEK2 kernel 
and no UEK4 kernel, disabling UEK4 repo")
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:if not foundUEK4:
usr/lib/anaconda/yuminstall.py:log.info("Found UEK3 kernel 
and no UEK4 kernel, disabling UEK4 repo")
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:if enableUEK4repo:
usr/lib/anaconda/yuminstall.py:self.addUEKRepo(extraRepos, "UEK4")

I've not found a way to disable this via any sort of boot options or the like 
and am currently headed down the path of creating a new, custom version of 
their install.img.  If anyone has any brilliant ideas I would love to hear 
them.  I even checked their non-UEK boot media and it had the same code.  
Hopefully, at the least, some other poor slave forced to use OEL will benefit 
from my discovery.

Regards,

j

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

[foreman-users] [Katello] How should RedHat products be accessed behind Corporate firewalls & w/ a proxy?

2016-11-15 Thread JC 
I have previously imported (the manifest) and used Red Hat products in 
Katello 2.4.*.  I've recently built a Katello 3.1 server and would like to 
do the same.

The manifest imports, but trying to select products returns:

getaddrinfo: Temporary failure in name resolution

I've seen this before (and in fact asked 

 
about it before), but I think it just 'went away'.

Both Katello servers sit behind Corporate firewalls and use a Corporate 
proxy.  The local DNS source doesn't know about public domains (so can't 
help with cdn.redhat.com).

When syncing the existing 2.4 Red Hat repositories, all requests 
successfully use the details provided in:

/etc/pulp/server/plugins.conf.d/yum_importer.json

But browsing the Red Hat product list now returns the same cdn.redhat.com 
lookup failure as the 3.1 server.

I've tried creating a host file entry for one of the public IPs for that 
site, but that naturally returns:

Connection refused - connect(2)

As that address is not reachable; this is prevented by the firewalls.

I've tried setting the host file entry for cdn.redhat.com to the IP of the 
proxy, then added a redirect rule in iptables to send the TCP443 request to 
the correct port of the proxy, but then I get an SSL error, as Katello is 
expecting a different conversation to the one the proxy wants to have.

>From what I can tell, there wouldn't be a problem if there wasn't the 
initial DNS lookup and this part solely used the json file.

Can anyone help please?

Cheers.

-- 
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] Re: default hostgroup plugin question

2016-11-15 Thread Greg Sutcliffe 
On 11 November 2016 at 18:09, Mike Tupker  wrote:

>  what is the correct way to declare a logical AND with more than one fact?
>

It's not explicitly documented, but the OR nature of the fact groups is
explicitly coded (see
https://github.com/theforeman/foreman_default_hostgroup/blob/develop/lib/default_hostgroup_base_host_patch.rb#L43-L52
if you like reading Ruby). There's an open PR on this which I've been
meaning to get to for *ages* (
https://github.com/theforeman/foreman_default_hostgroup/pull/22) which goes
along this line - you could try it if you're feeling adventurous :)

Greg

-- 
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: Changing The Foreman's 1.12.2 SSL Certificate

2016-11-15 Thread woj woj 
It's works, but after couple of weeks I have some problems:



1. When I opened  foreman URL, web browser asked me for user certifcate for 
authentification. When I clicked cancel, a could normaly log in. 

It isn't a big problem, but i'm corious why it's happening. 


2. When i restarted service puppetserver, autosign certifcates became 
untrusted, and I had to cleaned certifcates on agent, and manual signed it 
by forman GUI.

It's a bigger problem :) 


W dniu środa, 21 września 2016 09:29:23 UTC+2 użytkownik woj woj napisał:
>
> It works.
> Thank you very much! 
>
> W dniu wtorek, 20 września 2016 18:54:48 UTC+2 użytkownik Edward Berger 
> napisał:
>>
>>
>> I know there's some SElinux magic, but if you have disabled SELinux you 
>> can try a command line like
>> this to install a new web certificate, key, and chain (intermediate 
>> certificates) and keep the puppet part working...
>>
>> foreman-installer \
>> --foreman-server-ssl-key=/etc/pki/tls/private/foreman.example.com.key \
>> --puppet-server-foreman=true \
>> --foreman-server-ssl-cert=/etc/pki/tls/certs/foreman.example.com.crt \
>> --foreman-server-ssl-chain=/etc/pki/tls/certs/cachain.crt \
>> --foreman-server-ssl-certs-dir=/etc/pki/tls/certs \
>> --foreman-websockets-encrypt=true \
>> --foreman-websockets-ssl-key=/etc/pki/tls/private/foreman.example.com.key 
>> \
>> --foreman-websockets-ssl-cert=/etc/pki/tls/certs/foreman.example.com.crt \
>> --puppet-server-foreman=true \
>> --puppet-server-foreman-ssl-ca=/etc/pki/tls/certs/cachain.crt \
>> --foreman-proxy-foreman-ssl-ca=/etc/pki/tls/certs/cachain.crt \
>> --foreman-foreman-url=https://foreman.example.com
>>
>>
>>

-- 
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] Foreman api v2 post filter

2016-11-15 Thread mobios 
Thank for your answer Thomas.

My Problem is resolved.
I used Curl against the Restapi and i realized i need one more parameter in 
my http request.

Your ideas were very usefull.

Best regards
mobios

-- 
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] Custom variables in templates

2016-11-15 Thread Dominic Cleal 
On 14/11/16 20:48, Sean O'Keeffe wrote:
> Use a Parameter you can set them on an Organisation, Location, operating
> system, subnet, host group and host. They have a priority so you can
> override them at points*. You could get access them from the template
> using @host.params[''] so when the hosts PXE template is
> generated it would be set to what ever that param is set to for that host.
> 
> * sorry I can't remember he priory right now!

See https://theforeman.org/manuals/1.13/index.html#4.2.3Parameters under
Global parameters.

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

Re: [foreman-users] OEL 6 hardcoded yum repo

2016-11-15 Thread Klaas Demter 
Hey,
the current community templates should work for oracle linux 
(https://github.com/theforeman/community-templates). I'm not sure about the 
uek4 repository but the way to get rid of the mysql repository during kickstart 
is in this commit: 
https://github.com/theforeman/community-templates/commit/9ec2d99f1de16e4f0640883aeb18a29a2015853e
maybe something simmilar to this will also work for the uek repo. also note 
that there is a disable-uek parameter now: 
https://github.com/theforeman/community-templates/commit/4d62c9bf7f4af989e9f115fa76f8cf7839a62de8


Greetings
Klaas

- Ursprüngliche Mail -
Von: "'Jason B. Nance' via Foreman users" 
An: foreman-users@googlegroups.com
Gesendet: Montag, 14. November 2016 22:25:12
Betreff: [foreman-users] OEL 6 hardcoded yum repo

Hello Everyone,

I've been attempting to kickstart an OEL 6 server off my Katello environment 
and kept getting an error about failing to add a UEK4 repository.  Since there 
is no such repository definition in my provisioning templates / kickstart this 
was very perplexing to me.  After banging my head against the wall for a bit I 
finally mounted the OEL 6 "install.img" and did a grep for UEK4.  This is the 
awesomeness I found:

$ cd /path/to/mounted/install.img
$ grep -r UEK4 *
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:enableUEK4repo = True
usr/lib/anaconda/yuminstall.py:# If we are upgrading we need to check 
for pre-UEK4 kernel
usr/lib/anaconda/yuminstall.py:# if found we do not want to enable the 
UEK4 repo unless it is also installed
usr/lib/anaconda/yuminstall.py:foundUEK4 = False
usr/lib/anaconda/yuminstall.py:log.info("Found UEK4 
modules directory %s" %(dirname))
usr/lib/anaconda/yuminstall.py:foundUEK4 = True
usr/lib/anaconda/yuminstall.py:if not foundUEK4:
usr/lib/anaconda/yuminstall.py:log.info("Found UEK1 kernel 
and no UEK4 kernel, disabling UEK4 repo")
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:if not foundUEK4:
usr/lib/anaconda/yuminstall.py:log.info("Found UEK2 kernel 
and no UEK4 kernel, disabling UEK4 repo")
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:if not foundUEK4:
usr/lib/anaconda/yuminstall.py:log.info("Found UEK3 kernel 
and no UEK4 kernel, disabling UEK4 repo")
usr/lib/anaconda/yuminstall.py:enableUEK4repo = False
usr/lib/anaconda/yuminstall.py:if enableUEK4repo:
usr/lib/anaconda/yuminstall.py:self.addUEKRepo(extraRepos, "UEK4")

I've not found a way to disable this via any sort of boot options or the like 
and am currently headed down the path of creating a new, custom version of 
their install.img.  If anyone has any brilliant ideas I would love to hear 
them.  I even checked their non-UEK boot media and it had the same code.  
Hopefully, at the least, some other poor slave forced to use OEL will benefit 
from my discovery.

Regards,

j

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