[foreman-users] Unable to add non-RHEL subscription to activation key

[Stephen Odo]

I'm running Katello 3.4.2. When creating an activation key, I click on the 
"Subscriptions" --> "Add" tab to add, say, EPEL (which I've set up as a 
product) to the activation key.

The only choices that show up are the Red Hat subscriptions. None of the 
non-Red Hat products show up. Is there something special I need to do in 
order to add non-Red Hat subscriptions to an activation key?

Thanks.

--Stephen

-- 
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: Newbie help with configuring classes

[Andrew Schofield]

You need to use the cron::job class. Looks like you're using the cron 
class. The documentation for this seems pretty clear?

On Monday, July 3, 2017 at 1:30:56 PM UTC-4, 1284...@gmail.com wrote:
>
> Hi
>
> It might be best if you post your class to debug...
>
>
>
> On Friday, June 23, 2017 at 9:35:50 AM UTC+1, Hernan Vera wrote:
>>
>> Hi, I´m new to Foreman and Puppet, I´ve deployed Foreman and upgraded it 
>> to 15, it´s working right for NTP class (as shown on tutorials).
>> I´m trying to configure cron on clients, but I don´t know how to do it, 
>> which Smart Parameters should I modify and where to add the job to deploy 
>> to clients. I´ve looked on the web but nothing found. I´m using 
>> rmueller/cron from forge puppet. Would anyone help me please?
>>
>>
>>
>> 
>>
>>
>> 
>>
>>
>>
>> 
>>
>

-- 
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] Plugin or tool to link Foreman to GIT

[1284typeb]

Hi All

I have been attemtping to use r10k as a tool to create dynamic environments 
with git and my puppet master, however i was wondering if there is a plugin 
or tool that would interface between a git repo and Foreman directly? 

Please let me know if there is anything!

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

[foreman-users] Re: Newbie help with configuring classes

[1284typeb]

Hi

It might be best if you post your class to debug...



On Friday, June 23, 2017 at 9:35:50 AM UTC+1, Hernan Vera wrote:
>
> Hi, I´m new to Foreman and Puppet, I´ve deployed Foreman and upgraded it 
> to 15, it´s working right for NTP class (as shown on tutorials).
> I´m trying to configure cron on clients, but I don´t know how to do it, 
> which Smart Parameters should I modify and where to add the job to deploy 
> to clients. I´ve looked on the web but nothing found. I´m using 
> rmueller/cron from forge puppet. Would anyone help me please?
>
>
>
> 
>
>
> 
>
>
>
> 
>

-- 
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: Problem upgrading Katello. Upgrade step errata_import failed. Complains about apipie cache

[louis . coilliot]

I tried this :

# foreman-rake apipie:cache --trace
** Invoke apipie:cache (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute apipie:cache
2017-07-03 14:45:15 +0200 | Started
2017-07-03 14:45:29 +0200 | Documents loaded...
2017-07-03 14:45:29 +0200 | Processing docs for
rake aborted!
Missing template ../../layouts/apipie/apipie with {:locale=>[:ru, :en], 
:formats=>[:html], :handlers=>[:erb, :builder, :rabl]}. Searched in:
  * 
"/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/app/views/apipie/apipies"
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/path_set.rb:58:in
 
`find'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/lookup_context.rb:116:in
 
`find'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/abstract_renderer.rb:3:in
 
`find_template'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/template_renderer.rb:80:in
 
`resolve_layout'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/template_renderer.rb:70:in
 
`block in find_layout'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/lookup_context.rb:239:in
 
`with_layout_format'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/abstract_renderer.rb:3:in
 
`with_layout_format'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/template_renderer.rb:70:in
 
`find_layout'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/template_renderer.rb:54:in
 
`render_with_layout'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/template_renderer.rb:46:in
 
`render_template'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/template_renderer.rb:18:in
 
`render'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/renderer.rb:41:in
 
`render_template'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/renderer/renderer.rb:22:in
 
`render'
/opt/rh/ruby193/root/usr/share/gems/gems/actionpack-3.2.8/lib/action_view/helpers/rendering_helper.rb:24:in
 
`render'
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:117:in
 
`block in render_page'
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:113:in
 
`open'
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:113:in
 
`render_page'
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:147:in
 
`generate_index_page'
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:77:in
 
`block (4 levels) in '
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:66:in
 
`each'
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:66:in
 
`block (3 levels) in '
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:188:in
 
`with_loaded_documentation'
/opt/theforeman/tfm/root/usr/share/gems/gems/apipie-rails-0.2.6/lib/tasks/apipie.rake:64:in
 
`block (2 levels) in '
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `call'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `block in execute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `each'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `execute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in `block in 
invoke_with_call_chain'
/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in `mon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in 
`invoke_with_call_chain'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:in `invoke'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in `invoke_task'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `block (2 
levels) in top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `each'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `block in 
top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in 
`standard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in `top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:in `block in run'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in 
`standard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:in `run'
/opt/rh/ruby193/root/usr/bin/rake:32:in `'
Tasks: TOP => apipie:cache


The packages installed are :



tfm-rubygem-addressable-2.3.6-2.el7.noarch 
tfm-rubygem-algebrick-0.7.3-3.el7.noarch 
tfm-rubygem-ancestry-2.0.0-3.el7.noarch 
tfm-rubygem-anemone-0.7.2-11.el7.noarch 
tfm-rubygem-angular-rails-templates-0.1.2-3.el7.noarch 
tfm-rubygem-ansi-1.4.3-5.el7.noarch 
tfm-rubygem-apipie-bindings-0.0.14

Re: [foreman-users] Re: [foreman-dev] [event] Deep Dive: Running the Foreman Stack in Containers - Mon 10th July, 2pm (UK)

[Ohad Levy]

On Fri, Jun 30, 2017 at 1:35 AM, Eric D Helms  wrote:

> Thanks for setting this up Greg.
>
> I wanted to send out a few notes ahead of time so that folks can do any
> background reading, using the work I'll be presenting or think about
> questions they might have. If you want to send along questions ahead of
> time you'd like addressed (or to ensure I cover) please feel free to reply
> here and I'll do my best to work them into the presentation.
>
> Rough Topics I'll be covering:
>
>  * Brief presentation on why containers, the technologies involved in
> build and deploy
>  * Architecture presentation of service breakdown
>  * How the PR[1] works
>  * Current state and future Roadmap
>

I would be happy if you could also cover:
- Smart proxy features (and how it works - e.g. a container per feature
with base container etc).
- Dev vs Production (whats in scope vs not)
- Installer - do we still need it in a context of a Kubernetes application?
- SCL ? can we move away from it?
- reuse? for example, https://github.com/manageiq?q=container have some
basic ruby / rails containers etc
- application scaling ? (e.g. more dynflow workers etc).

sorry for the long list :)

thanks,
Ohad

>
>
> Thanks,
> Eric
>
>
> [1] https://github.com/theforeman/forklift/pull/424
>
> On Thu, Jun 29, 2017 at 10:15 AM, Greg Sutcliffe  > wrote:
>
>> Hi all,
>>
>> Running Foreman in a container is a question that comes up from time to
>> time in the Foreman community. Eric Helms has been experimenting with
>> running the whole Foreman stack (core, proxies, plugins) inside
>> Kubernetes, and wants to show you how it looks. We'll be holding a deep
>> dive into this on Monday 10th July, at 2pm (GMT +1). You can tune in
>> here:
>>
>> https://www.youtube.com/watch?v=mPjUvNAYp1c
>>
>> As always, we welcome your contributions to the video - do join us live
>> on YouTube Live chat or in our IRC channel to put your questions to
>> Eric!
>>
>> Cheers,
>> Greg
>> --
>> IRC / Twitter: @gwmngilfen
>> Diaspora: gwmngil...@joindiaspora.com
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "foreman-dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to foreman-dev+unsubscr...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Eric D. Helms
> Red Hat Engineering
>
> --
> 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] Problem upgrading Katello. Upgrade step errata_import failed. Complains about apipie cache

[louis . coilliot]

Hello, I get an error when I try to upgrade Katello from ver. 2.3 to 2.4. 

Upgrade step errata_import failed.

The logs say :




[ERROR 2017-06-28 18:25:26 main] API controllers newer than Apipie cache! Run 
apipie:cache rake task to regenerate cache.
rake aborted!
401 Unauthorized

Tasks: TOP => katello:upgrades:2.1:import_errata
(See full trace by running task with --trace)
Importing Errata

[ERROR 2017-06-28 18:25:26 main] Upgrade step errata_import failed. Check logs 
for more information.
[DEBUG 2017-06-28 18:25:26 main] Exit with status code: 1 (signal was 1)
[ERROR 2017-06-28 18:25:26 main] Repeating errors encountered during run:
[ERROR 2017-06-28 18:25:26 main] sed: can't read /etc/mongodb.conf: No such 
file or directory

[ERROR 2017-06-28 18:25:26 main]  Could not back up 
/etc/httpd/conf.d/userdir.conf: Got passed new contents for sum 
{md5}d4a2620683cc3ff2315c685f9f354265
[ERROR 2017-06-28 18:25:26 main]  Could not back up 
/etc/httpd/conf.d/userdir.conf: Got passed new contents for sum 
{md5}d4a2620683cc3ff2315c685f9f354265
[ERROR 2017-06-28 18:25:26 main]  
/Stage[main]/Apache/File[/etc/httpd/conf.d/userdir.conf]/ensure: change from 
file to absent failed: Could not back up /etc/httpd/conf.d/userdir.conf: Got 
passed new contents for sum {md5}d4a2620683cc3ff2315c685f9f354265
[ERROR 2017-06-28 18:25:26 main]  Could not back up 
/etc/httpd/conf.d/welcome.conf: Got passed new contents for sum 
{md5}9d1328b985d0851eb5bc610da6122f44
[ERROR 2017-06-28 18:25:26 main]  Could not back up 
/etc/httpd/conf.d/welcome.conf: Got passed new contents for sum 
{md5}9d1328b985d0851eb5bc610da6122f44
[ERROR 2017-06-28 18:25:26 main]  
/Stage[main]/Apache/File[/etc/httpd/conf.d/welcome.conf]/ensure: change from 
file to absent failed: Could not back up /etc/httpd/conf.d/welcome.conf: Got 
passed new contents for sum {md5}9d1328b985d0851eb5bc610da6122f44
[ERROR 2017-06-28 18:25:26 main]  Could not back up /etc/httpd/conf.d/README: 
Got passed new contents for sum {md5}20b886e8496027dcbc31ed28d404ebb1
[ERROR 2017-06-28 18:25:26 main]  Could not back up /etc/httpd/conf.d/README: 
Got passed new contents for sum {md5}20b886e8496027dcbc31ed28d404ebb1
[ERROR 2017-06-28 18:25:26 main]  
/Stage[main]/Apache/File[/etc/httpd/conf.d/README]/ensure: change from file to 
absent failed: Could not back up /etc/httpd/conf.d/README: Got passed new 
contents for sum {md5}20b886e8496027dcbc31ed28d404ebb1
[ERROR 2017-06-28 18:25:26 main] API controllers newer than Apipie cache! Run 
apipie:cache rake task to regenerate cache.
rake aborted!
401 Unauthorized

Tasks: TOP => katello:upgrades:2.1:import_errata
(See full trace by running task with --trace)
Importing Errata

[ERROR 2017-06-28 18:25:26 main] Upgrade step errata_import failed. Check logs 
for more information.



The Foreman has been upgraded just before from ver. 1.9.3 to 1.10.4, painfully 
(the Centos 7 SCL repo provides ruby193-rubygem-activesupport-3.2.8-5 but 
3.2.8-6 is needed, with 
security_utils.rb) but without errors in the end. 


I'm using the upstream versions of Foreman and Katello, on Centos 7 (I mean, 
this is not a RH Satellite) 


Do you know how to fix this and restart the faulty step, please ?


Thanks in advance.


Louis Coilliot

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