Re: [foreman-users] Re: Katello 3.3.1 released!

2017-03-23 Thread 'Jason B. Nance' via Foreman users 
FYI, I opened http://projects.theforeman.org/issues/19015 for this. 




From: "Jason Nance"  
To: "Foreman Users"  
Sent: Thursday, March 23, 2017 5:32:40 PM 
Subject: Re: [foreman-users] Re: Katello 3.3.1 released! 

So does this mean that you can't upgrade to 3.3 if you have the remote 
execution plugin installed/enabled? I'm running into the same error. 

In my case I'm attempting to upgrade to get a newer Pulp to resolve this: 

https://pulp.plan.io/issues/2344 

...which basically allows Pulp to work with a proxy when the upstream is https. 




From: "Eric D Helms"  
To: "Foreman Users"  
Sent: Thursday, March 23, 2017 8:56:06 AM 
Subject: Re: [foreman-users] Re: Katello 3.3.1 released! 

I believe this is the key error " ArgumentError: Unknown key: 
:host_action_button. Valid keys are: :provided_inputs, :description" which 
comes from foreman_remote_execution having an older release. This is fixed in 
master of the plugin but releasing a newer version is blocked by other issues 
that are being worked on. 

On Thu, Mar 23, 2017 at 9:14 AM, Duncan Innes < [ mailto:dun...@innes.net | 
dun...@innes.net ] > wrote: 



I'm not skilled in diagnosing log files, but I see the following in 
katello.1.log and katello.log: 

1. 
[ INFO 2017-03-22 10:58:20 main] Upgrade Step: migrate_foreman... 

2. 
[ERROR 2017-03-22 10:58:25 main] 

3. 
[ERROR 2017-03-22 10:58:31 main] API controllers newer than Apipie cache! Run 
apipie:cache rake task to regenerate cache. 

4. 
rake aborted! 

Is this the source of the problem, or just a symptom of an underlying issue? 

Duncan 

On Wednesday, 22 March 2017 12:21:15 UTC, Duncan Innes wrote: 
BQ_BEGIN


Apologies, forgot about my pastebin account until midway through splitting 
initial log file: 
[root@katello ~]# cd /var/log/foreman-installer/ 
[root@katello foreman-installer]# ls -lrt 
total 3572 
-rw-r--r--. 1 root root 0 Feb 28 21:47 foreman.2.log 
-rw-r--r--. 1 root root 0 Feb 28 21:48 katello.6.log 
-rw-r--r--. 1 root root 15751 Feb 28 21:50 katello.5.log 
-rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log 
-rw-r--r--. 1 root root 8553 Mar 22 10:47 foreman.1.log <- [ 
http://pastebin.com/ep4HajV5 | http://pastebin.com/ep4HajV5 ] 
-rw-r--r--. 1 root root 1212 Mar 22 10:47 foreman.log <- [ 
http://pastebin.com/TVixt0eK | http://pastebin.com/TVixt0eK ] 
-rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log <- [ 
http://pastebin.com/530ih26P | http://pastebin.com/530ih26P ] 
-rw-r--r--. 1 root root 8624 Mar 22 10:49 katello.2.log <- [ 
http://pastebin.com/d7RLn3Hw | http://pastebin.com/d7RLn3Hw ] 
-rw-r--r--. 1 root root 49047 Mar 22 10:55 katello.1.log <- [ 
http://pastebin.com/G0EFGwCa | http://pastebin.com/G0EFGwCa ] 
-rw-r--r--. 1 root root 48628 Mar 22 10:58 katello.log <- [ 
http://pastebin.com/UDTTjrwU | http://pastebin.com/UDTTjrwU ] 
[root@katello foreman-installer]# 


On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote: 
BQ_BEGIN

What errors? 




BQ_END



-- 
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 [ mailto:foreman-users+unsubscr...@googlegroups.com | 
foreman-users+unsubscr...@googlegroups.com ] . 
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] . 
Visit this group at [ https://groups.google.com/group/foreman-users | 
https://groups.google.com/group/foreman-users ] . 
For more options, visit [ https://groups.google.com/d/optout | 
https://groups.google.com/d/optout ] . 

BQ_END




-- 
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 [ mailto:foreman-users+unsubscr...@googlegroups.com | 
foreman-users+unsubscr...@googlegroups.com ] . 
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] . 
Visit this group at [ https://groups.google.com/group/foreman-users | 
https://groups.google.com/group/foreman-users ] . 
For more options, visit [ https://groups.google.com/d/optout | 
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.

Re: [foreman-users] Re: Katello 3.3.1 released!

2017-03-23 Thread 'Jason B. Nance' via Foreman users 
So does this mean that you can't upgrade to 3.3 if you have the remote 
execution plugin installed/enabled? I'm running into the same error. 

In my case I'm attempting to upgrade to get a newer Pulp to resolve this: 

https://pulp.plan.io/issues/2344 

...which basically allows Pulp to work with a proxy when the upstream is https. 




From: "Eric D Helms"  
To: "Foreman Users"  
Sent: Thursday, March 23, 2017 8:56:06 AM 
Subject: Re: [foreman-users] Re: Katello 3.3.1 released! 

I believe this is the key error " ArgumentError: Unknown key: 
:host_action_button. Valid keys are: :provided_inputs, :description" which 
comes from foreman_remote_execution having an older release. This is fixed in 
master of the plugin but releasing a newer version is blocked by other issues 
that are being worked on. 

On Thu, Mar 23, 2017 at 9:14 AM, Duncan Innes < [ mailto:dun...@innes.net | 
dun...@innes.net ] > wrote: 



I'm not skilled in diagnosing log files, but I see the following in 
katello.1.log and katello.log: 

1. 
[ INFO 2017-03-22 10:58:20 main] Upgrade Step: migrate_foreman... 

2. 
[ERROR 2017-03-22 10:58:25 main] 

3. 
[ERROR 2017-03-22 10:58:31 main] API controllers newer than Apipie cache! Run 
apipie:cache rake task to regenerate cache. 

4. 
rake aborted! 

Is this the source of the problem, or just a symptom of an underlying issue? 

Duncan 

On Wednesday, 22 March 2017 12:21:15 UTC, Duncan Innes wrote: 
BQ_BEGIN


Apologies, forgot about my pastebin account until midway through splitting 
initial log file: 
[root@katello ~]# cd /var/log/foreman-installer/ 
[root@katello foreman-installer]# ls -lrt 
total 3572 
-rw-r--r--. 1 root root 0 Feb 28 21:47 foreman.2.log 
-rw-r--r--. 1 root root 0 Feb 28 21:48 katello.6.log 
-rw-r--r--. 1 root root 15751 Feb 28 21:50 katello.5.log 
-rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log 
-rw-r--r--. 1 root root 8553 Mar 22 10:47 foreman.1.log <- [ 
http://pastebin.com/ep4HajV5 | http://pastebin.com/ep4HajV5 ] 
-rw-r--r--. 1 root root 1212 Mar 22 10:47 foreman.log <- [ 
http://pastebin.com/TVixt0eK | http://pastebin.com/TVixt0eK ] 
-rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log <- [ 
http://pastebin.com/530ih26P | http://pastebin.com/530ih26P ] 
-rw-r--r--. 1 root root 8624 Mar 22 10:49 katello.2.log <- [ 
http://pastebin.com/d7RLn3Hw | http://pastebin.com/d7RLn3Hw ] 
-rw-r--r--. 1 root root 49047 Mar 22 10:55 katello.1.log <- [ 
http://pastebin.com/G0EFGwCa | http://pastebin.com/G0EFGwCa ] 
-rw-r--r--. 1 root root 48628 Mar 22 10:58 katello.log <- [ 
http://pastebin.com/UDTTjrwU | http://pastebin.com/UDTTjrwU ] 
[root@katello foreman-installer]# 


On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote: 
BQ_BEGIN

What errors? 




BQ_END



-- 
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 [ mailto:foreman-users+unsubscr...@googlegroups.com | 
foreman-users+unsubscr...@googlegroups.com ] . 
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] . 
Visit this group at [ https://groups.google.com/group/foreman-users | 
https://groups.google.com/group/foreman-users ] . 
For more options, visit [ https://groups.google.com/d/optout | 
https://groups.google.com/d/optout ] . 

BQ_END




-- 
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 [ mailto:foreman-users+unsubscr...@googlegroups.com | 
foreman-users+unsubscr...@googlegroups.com ] . 
To post to this group, send email to [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] . 
Visit this group at [ https://groups.google.com/group/foreman-users | 
https://groups.google.com/group/foreman-users ] . 
For more options, visit [ https://groups.google.com/d/optout | 
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.

Re: [foreman-users] Provisioning a host fails with interface errors

2017-03-23 Thread Johannes Kastl 
Johannes Kastl schrieb:
> Johannes Kastl schrieb:
>> It is the step after that, when provisioning the host, that fails.
> 
> I am attaching a screen shot of the error (I hope it gets through to
> the list).

Is there anything I can do to debug this further? Any more logs?
Anything in the settings I should have a look at?

Is there a way to get foreman to actually say, what the problem is with
the interface? What exactly it is, that is disturbing foreman?

This is rendering foreman unusable for my usecase, so it is kind of
urgent that I get this running.

Johannes

-- 
Johannes Kastl
Linux Consultant & Trainer
Tel.: +49 (0) 151 2372 5802
Mail: ka...@b1-systems.de

B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537

-- 
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: Katello 3.3.1 released!

2017-03-23 Thread Eric D Helms 
I believe this is the key error "ArgumentError: Unknown key:
:host_action_button. Valid keys are: :provided_inputs, :description" which
comes from foreman_remote_execution having an older release. This is fixed
in master of the plugin but releasing a newer version is blocked by other
issues that are being worked on.

On Thu, Mar 23, 2017 at 9:14 AM, Duncan Innes  wrote:

> I'm not skilled in diagnosing log files, but I see the following in
> katello.1.log and katello.log:
>
>
>1. [ INFO 2017-03-22 10:58:20 main] Upgrade Step: migrate_foreman...
>2. [ERROR 2017-03-22 10:58:25 main]
>3. [ERROR 2017-03-22 10:58:31 main] API controllers newer than Apipie
>cache! Run apipie:cache rake task to regenerate cache.
>4. rake aborted!
>
> Is this the source of the problem, or just a symptom of an underlying
> issue?
>
> Duncan
>
> On Wednesday, 22 March 2017 12:21:15 UTC, Duncan Innes wrote:
>>
>>
>> Apologies, forgot about my pastebin account until midway through
>> splitting initial log file:
>>
>> [root@katello ~]# cd /var/log/foreman-installer/
>> [root@katello foreman-installer]# ls -lrt
>> total 3572
>> -rw-r--r--. 1 root root   0 Feb 28 21:47 foreman.2.log
>> -rw-r--r--. 1 root root   0 Feb 28 21:48 katello.6.log
>> -rw-r--r--. 1 root root   15751 Feb 28 21:50 katello.5.log
>> -rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log
>> -rw-r--r--. 1 root root8553 Mar 22 10:47 foreman.1.log   <-
>> http://pastebin.com/ep4HajV5
>> -rw-r--r--. 1 root root1212 Mar 22 10:47 foreman.log <-
>> http://pastebin.com/TVixt0eK
>> -rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log   <-
>> http://pastebin.com/530ih26P
>> -rw-r--r--. 1 root root8624 Mar 22 10:49 katello.2.log   <-
>> http://pastebin.com/d7RLn3Hw
>> -rw-r--r--. 1 root root   49047 Mar 22 10:55 katello.1.log   <-
>> http://pastebin.com/G0EFGwCa
>> -rw-r--r--. 1 root root   48628 Mar 22 10:58 katello.log <-
>> http://pastebin.com/UDTTjrwU
>> [root@katello foreman-installer]#
>>
>>
>> On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>>>
>>> What errors?
>>>
>>
>>
> --
> 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.
>



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

Re: [foreman-users] Re: Katello 3.3.1 released!

2017-03-23 Thread Duncan Innes 
I'm not skilled in diagnosing log files, but I see the following in 
katello.1.log and katello.log:


   1. [ INFO 2017-03-22 10:58:20 main] Upgrade Step: migrate_foreman...
   2. [ERROR 2017-03-22 10:58:25 main]
   3. [ERROR 2017-03-22 10:58:31 main] API controllers newer than Apipie 
   cache! Run apipie:cache rake task to regenerate cache.
   4. rake aborted!
   
Is this the source of the problem, or just a symptom of an underlying issue?

Duncan

On Wednesday, 22 March 2017 12:21:15 UTC, Duncan Innes wrote:
>
>
> Apologies, forgot about my pastebin account until midway through splitting 
> initial log file:
>
> [root@katello ~]# cd /var/log/foreman-installer/
> [root@katello foreman-installer]# ls -lrt
> total 3572
> -rw-r--r--. 1 root root   0 Feb 28 21:47 foreman.2.log
> -rw-r--r--. 1 root root   0 Feb 28 21:48 katello.6.log
> -rw-r--r--. 1 root root   15751 Feb 28 21:50 katello.5.log
> -rw-r--r--. 1 root root 2172590 Feb 28 23:27 katello.4.log
> -rw-r--r--. 1 root root8553 Mar 22 10:47 foreman.1.log   <- 
> http://pastebin.com/ep4HajV5
> -rw-r--r--. 1 root root1212 Mar 22 10:47 foreman.log <- 
> http://pastebin.com/TVixt0eK
> -rw-r--r--. 1 root root 1338785 Mar 22 10:48 katello.3.log   <- 
> http://pastebin.com/530ih26P
> -rw-r--r--. 1 root root8624 Mar 22 10:49 katello.2.log   <- 
> http://pastebin.com/d7RLn3Hw
> -rw-r--r--. 1 root root   49047 Mar 22 10:55 katello.1.log   <- 
> http://pastebin.com/G0EFGwCa
> -rw-r--r--. 1 root root   48628 Mar 22 10:58 katello.log <- 
> http://pastebin.com/UDTTjrwU
> [root@katello foreman-installer]# 
>
>
> On Wednesday, 22 March 2017 11:47:39 UTC, Eric Helms wrote:
>>
>> What errors?
>>
>  
>

-- 
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: Auto-provision not configuring tftp proxy

2017-03-23 Thread bena 
I'm also experiencing this problem with Foreman 1.14.0, FWIW.

If I manually provision the host and fill in everything by hand, Foreman 
creates a file with the MAC of the host in /srv/tftp/pxelinux.cfg as 
expected, and the box reboots into the installation process as I'd hope. If 
I autoprovision it, nothing is created and the box just reboots back to the 
discovery image.

On Thursday, 2 March 2017 18:26:04 UTC, Michael Vollman wrote:
>
>
> When I say "rebuild config" I am referring to the "All Hosts" page of the 
> web UI.  When you check the box next to a host there is an action drop down 
> that appears above the table that gives an option to "Rebuild Config".
>
> I have attached the log output from Foreman.
>
>
> On Friday, February 24, 2017 at 10:29:57 AM UTC-5, Lukas Zapletal wrote:
>>
>> When you say "rebuild config" do you mean hitting Cancel build and 
>> then Build buttons? 
>>
>> Try with DEBUG yes please. Also if you can enable SQL logger as well. 
>>
>> On Fri, Feb 24, 2017 at 4:01 PM, Michael Vollman 
>>  wrote: 
>> > I have attempted the second test of editing the host immediately after 
>> it 
>> > has been auto-provisioned and just clicking submit.  It does not error, 
>> but 
>> > it does change the hostname to the default of prefix 'mac' followed by 
>> mac 
>> > address.  And it still does not generate the tftp config unless I run 
>> > rebuild config on the host.  I have been watching both the 
>> 'production.log' 
>> > on the foreman host and the 'proxy.log' on the tftp smart proxy. 
>>  Nothing 
>> > happens on the tftp smart proxy log, because foreman never appears to 
>> > attempt to contact it.  I have not seen an error in the production.log. 
>>  I 
>> > will increase verbosity and try again. 
>> > 
>> > 
>> > On Tuesday, February 21, 2017 at 5:21:10 PM UTC-5, Michael Vollman 
>> wrote: 
>> >> 
>> >> Hello, 
>> >> 
>> >> I recently installed foreman 1.14.1 and I am attempting to use 
>> foreman's 
>> >> auto provisioning feature for the first time.  I am able to provision 
>> >> discovered hosts manually without any issue, but when I try to auto 
>> >> provision the same host foreman does not call out to the tftp smart 
>> proxy to 
>> >> create the tftp config.  The host reboots back to discovery and errors 
>> that 
>> >> it cannot discover a host that is pending for build.  However if I run 
>> >> 'Rebuild Config' against the host that has been auto-provisioned, 
>> foreman 
>> >> calls the tftp proxy, the tftp config is created and I can boot the 
>> node to 
>> >> kickstart as expected. 
>> >> 
>> >> The host then provisions fine, but when it gets to the end of 
>> provisioning 
>> >> and tries to call back to foreman that it is built (via a templates 
>> smart 
>> >> proxy) it fails and then reboots back into provisioning.  This is what 
>> is 
>> >> logged in the template smart proxy proxy.log: 
>> >> 
>> >> 
>> >> E, [2017-02-17T10:16:52.851486 ] ERROR -- : Failed to retrieve built 
>> >> template for {"token"=>"fa01bedd-344d-4863-9dc0-3754dad51cbe", 
>> "splat"=>[], 
>> >> "captures"=>["built"], "kind"=>"built"}: Error retrieving built for 
>> >> {"token"=>"fa01bedd-344d-4863-9dc0-3754dad51cbe", 
>> >> :url=>"http://tftp1.deploy.local:8000"} from foreman14.deploy.local: 
>> >> Net::HTTPConflict 
>> >> D, [2017-02-17T10:16:52.851578 ] DEBUG -- : Error retrieving built for 
>> >> {"token"=>"fa01bedd-344d-4863-9dc0-3754dad51cbe", 
>> >> :url=>"http://tftp1.deploy.local:8000"} from foreman14.deploy.local: 
>> >> Net::HTTPConflict (RuntimeError) 
>> >> 
>> >> 
>> >> Having never used auto provisioning in foreman I am sure this is a 
>> >> configuration issue on my side, but I am confused by the fact that 
>> regular 
>> >> provisioning works just fine.  I assumed if I could provision then I 
>> could 
>> >> auto provision as well once I configured discovery rules. 
>> >> 
>> >> Any help would be very much appreciated. 
>> >> 
>> >> Thanks,MIKE 
>> > 
>> > -- 
>> > 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-user...@googlegroups.com. 
>> > To post to this group, send email to forema...@googlegroups.com. 
>> > Visit this group at https://groups.google.com/group/foreman-users. 
>> > For more options, visit https://groups.google.com/d/optout. 
>>
>>
>>
>> -- 
>> 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] Error while installation

2017-03-23 Thread Dominic Cleal 
On 23/03/17 04:08, prakash ranjan wrote:
> Hi,
> 
> Trying to install by
> following:- https://theforeman.org/manuals/1.14/index.html#1.Foreman1.14Manual
> 
> After running - foreman-installer,getting following error:-
> 
> /Stage[main]/Apache::Mod::Passenger/Apache::Mod[passenger]/Package[mod_passenger]/ensure:
> change from purged to present failed: Execution of '/usr/bin/yum -d 0 -e
> 0 -y install mod_passenger' returned 1: Error: Package:
> passenger-4.0.53-4.el7.x86_64 (epel)
> 
> Requires: rubygem(rake)

You're missing this dependency from your OS repo. If you're using RHEL,
check you have the "optional" repository enabled. Otherwise check for
the source of rubygem-rake in your OS distribution, it should be present.

> After facing the same issue previously, I installed rubygem and
> passenger. But getting the same error.
> 
> 
> [root@foreman-home ~]# gem install rack -v=1.6.4

If you're using the installer, you're using a packaged installation. Do
not install gems locally over the top, you may introduce version conflicts.

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