Re: [foreman-users] katello-agent 3.4 repos missing deps

['Jason B. Nance' via Foreman users]

Errr... wait, sorry, I totally misread your email. I thought you were referring 
to Katello server, not client. 

Sorry sorry... Ignore me. 

j 




From: "Jason Nance"  
To: "Foreman Users"  
Sent: Tuesday, June 27, 2017 3:52:19 PM 
Subject: Re: [foreman-users] katello-agent 3.4 repos missing deps 

Hi Matthew, 

EL 6 support was dropped earlier in the 3.x series. EL 7 is currently the only 
supported version for RHEL/RHEL-like distros. 

Regards, 

j 




From: matthewhmil...@gmail.com 
To: "Foreman Users"  
Sent: Tuesday, June 27, 2017 3:03:29 PM 
Subject: [foreman-users] katello-agent 3.4 repos missing deps 

I'm attempting to install the katello-agent on a CentOS 6 system per the 
instructions listed here: 
https://theforeman.org/plugins/katello/3.4/installation/clients.html 

But I get the following error: 

Cannot open: 
http://fedorapeople.org/groups/katello/releases/yum/3.4/client/el6/x86_64/katello-client-repos-latest.rpm.
 Skipping. 
Error: Nothing to do 

Looking at the repo the katello-client-repos-latest.rpm does not exist there. 
Nor do any of the dependencies for katello-agent (except for 
katello-agent-fact-plugin). The only OS that seems to have a fully populated 
repo for 3.4 is EL7. 



-- 
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] katello-agent 3.4 repos missing deps

['Jason B. Nance' via Foreman users]

Hi Matthew, 

EL 6 support was dropped earlier in the 3.x series. EL 7 is currently the only 
supported version for RHEL/RHEL-like distros. 

Regards, 

j 




From: matthewhmil...@gmail.com 
To: "Foreman Users"  
Sent: Tuesday, June 27, 2017 3:03:29 PM 
Subject: [foreman-users] katello-agent 3.4 repos missing deps 

I'm attempting to install the katello-agent on a CentOS 6 system per the 
instructions listed here: 
https://theforeman.org/plugins/katello/3.4/installation/clients.html 

But I get the following error: 

Cannot open: 
http://fedorapeople.org/groups/katello/releases/yum/3.4/client/el6/x86_64/katello-client-repos-latest.rpm.
 Skipping. 
Error: Nothing to do 

Looking at the repo the katello-client-repos-latest.rpm does not exist there. 
Nor do any of the dependencies for katello-agent (except for 
katello-agent-fact-plugin). The only OS that seems to have a fully populated 
repo for 3.4 is EL7. 



-- 
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] Foreman and Infrastructure as Code

['Jason B. Nance' via Foreman users]

Hi Peter, 

>> > I want the configuration changes to happen through source control only.
>> > Forman only for transparency, i.e. reporting, sounds perfect.

>> Then I'd suggest putting everything into the Puppet environment, forget
>> Foreman's Puppet class and parameter handling and use Puppet's data
>> lookup and Hiera to assign classes and parameters to hosts.

> That still sounds a bit like a half-baked solution.

>1. Why is the Foreman host being set up and configured using a Puppet 
> recipe,
>and then I should be throwing it away instead of maintaining, modifying,
> extending it?
>2. What is the cleanest path to add the Foreman host to the Puppet
>configuration? (I'm not sure how the foreman-answers.yaml is integrated, 
> and
> whether I should copy everything over from /usr/share/foreman-installer/
> modules )

>3. Also, shouldn't the foreman-installer be uninstalled to maintain a slim,
> clean system?

> I really don't want to SSH into the Foreman host after setting it up, and
> install stuff manually. How do I set things up that a Forman system is set up,
> including a Puppet configuration under version control in /etc/puppetlabs ,
> practically from zero? Every step I need to do manually is somewhat wasted
> time, and potential to introduce errors. I want to avoid that.

Unless you are in a situation where you are installing new Foreman hosts on a 
regular basis I think you're being a bit extreme. There is a point at which 
automation no longer gives you a return on investment. 

You may want to look into Nailgun to help automate some of your setup: 

https://github.com/SatelliteQE/nailgun 

https://pypi.python.org/pypi/nailgun 

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.

Re: [foreman-users] Foreman 1.14/Katello 3.3 upgrade make CCVs useless

['Jason B. Nance' via Foreman users]

Hey Lachlan, 

You could create 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.2.1.1/db/migrate/20170321012632_fill_in_content_view_components.rb
 (or similar based on your Katello version) with the contents of: 

https://github.com/Katello/katello/pull/6690/files 

...then run a --upgrade if you don't have luck with the console. 

Regards, 

j 



From: "Lachlan Musicman"  
To: "Foreman Users"  
Sent: Tuesday, May 9, 2017 6:08:57 PM 
Subject: Re: [foreman-users] Foreman 1.14/Katello 3.3 upgrade make CCVs useless 

Thanks Klaas. I'm not 100% sure how foreman-rake console works so I'll need to 
look into it. 

Appreciate your help. 

cheers 
L. 

-- 
"Mission Statement: To provide hope and inspiration for collective action, to 
build collective power, to achieve collective transformation, rooted in grief 
and rage but pointed towards vision and dreams." 

- Patrice Cullors, Black Lives Matter founder 

On 9 May 2017 at 17:15, Klaas Demter < [ mailto:dem...@atix.de | dem...@atix.de 
] > wrote: 


Sorry wrong link - right solution: 
[ http://projects.theforeman.org/issues/18820 | 
http://projects.theforeman.org/issues/18820 ] 


Greetings 
Klaas Demter 

ATIX - The Linux & Open Source Company 
[ http://www.atix.de/ | www.atix.de ] 

- Ursprüngliche Mail - 
Von: "Klaas Demter" < [ mailto:dem...@atix.de | dem...@atix.de ] > 
An: [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] 
Gesendet: Dienstag, 9. Mai 2017 09:12:13 
Betreff: Re: [foreman-users] Foreman 1.14/Katello 3.3 upgrade make CCVs useless 

Hey, 
this sounds like [ http://projects.theforeman.org/issues/19024 | 
http://projects.theforeman.org/issues/19024 ] . 

you can fix it by applying it manually - something like this in "foreman-rake 
console" - or wait for 3.3.2: 
class FakeContentView < ActiveRecord::Base 
self.table_name = 'katello_content_views' 

has_many :content_view_components, :class_name => "FakeContentViewVersion", 
:dependent => :destroy, 
:inverse_of => :composite_content_view, :foreign_key => 
:composite_content_view_id 
end 

class FakeContentViewVersion < ActiveRecord::Base 
self.table_name = 'katello_content_view_versions' 

has_many :content_view_components, :inverse_of => :content_view_version, 
:dependent => :destroy, :class_name => 'FakeContentViewComponent' 
end 

class FakeContentViewComponent < ActiveRecord::Base 
self.table_name = 'katello_content_view_components' 

belongs_to :content_view_version, :class_name => "FakeContentViewVersion", 
:inverse_of => :content_view_components 
belongs_to :content_view, :class_name => "FakeContentView", 
:inverse_of => :component_composites 
end 

FakeContentViewComponent.find_each do |cvc| 
if cvc.content_view_id.nil? && cvc.content_view_version_id 
cvc.content_view_id = cvc.content_view_version.content_view_id 
cvc.save! 
end 
end 


Greetings 
Klaas Demter 

ATIX - The Linux & Open Source Company 
[ http://www.atix.de/ | www.atix.de ] 

- Ursprüngliche Mail - 
Von: "Lachlan Musicman" < [ mailto:data...@gmail.com | data...@gmail.com ] > 
An: [ mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] 
Gesendet: Dienstag, 9. Mai 2017 07:46:03 
Betreff: [foreman-users] Foreman 1.14/Katello 3.3 upgrade make CCVs useless 

Hi 

I upgraded Foreman/Katello successfully (ie, without warning or error) from 
1.13/3.2 -> 1.14/3.3 

Now, when I go to a Composite Content Views, their "List/Remove Content 
Views" has the right number of rows in the table, but there is no text nor 
any ability to update to a newer version. 

This makes them useless, and I'm not sure how to solve it? 

I have rebooted the machine, and checked in Firefox and Chromium on Debian 
Stretch, Chrome in Windows. 

See attached images for eg 

Also attached: the html source code for the table cell with the missing 
value 

How do I fix this? 

cheers 
L. 
-- 
"Mission Statement: To provide hope and inspiration for collective action, 
to build collective power, to achieve collective transformation, rooted in 
grief and rage but pointed towards vision and dreams." 

- Patrice Cullors, *Black Lives Matter founder* 

-- 
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%2bunsubscr...@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, 

Re: [foreman-users] Re: repo not showig all packages synced locally

['Jason B. Nance' via Foreman users]

Hi Edward, 

Unless you have explicitly changed it, the default sync policy for Yum 
repositories in 3.3 is "on demand", which means that your Katello server should 
be attempting to pull the upstream package the first time a client requests it 
(not during syncs, only if requested). It may be that, for whatever reason, 
this is failing. Try running "foreman-tail" on your Katello server and then 
kick off the "yum upgrade" on a client and watch the transaction. That will 
help point to the real problem. 

Regards, 

j 



From: "Edward Clay"  
To: "Foreman Users"  
Sent: Tuesday, May 9, 2017 4:10:42 PM 
Subject: [foreman-users] Re: repo not showig all packages synced locally 

Should of included that I'm I'm running katello 3.3.1-1 with foreman 1.14.3-1. 

On Tuesday, 9 May 2017 15:05:59 UTC-6, Edward Clay wrote: 


Hello, 
I'm experiencing a strange issue where I've created a product with one repo 
that points syncs content from the following url. 

[ http://repo.r1soft.com/yum/stable/x86_64/ | 
http://repo.r1soft.com/yum/stable/x86_64/ ] 

and it seems to successfully sync data locally from this remote repo but when I 
look at the repo's url on my system I don't see all rpms that should be 
available. What I mean by this the repo shows 23 packages available but I only 
see the following browsing to the repos publish at url. 

[ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/
 | Parent Directory ] 

* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/repodata/
 | repodata/ ] 
* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/r1soft-docstore-6.2.2-78.x86_64.rpm
 | r1soft-docstore-6.2.2-78.x86_64.rpm ] 
* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/r1soft-getmodule-1.0.0-51.x86_64.rpm
 | r1soft-getmodule-1.0.0-51.x86_64.rpm ] 
* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-agent-6.2.2.x86_64.rpm
 | serverbackup-agent-6.2.2.x86_64.rpm ] 
* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-async-agent-2-6-6.2.2.x86_64.rpm
 | serverbackup-async-agent-2-6-6.2.2.x86_64.rpm ] 
* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-enterprise-6.2.2.x86_64.rpm
 | serverbackup-enterprise-6.2.2.x86_64.rpm ] 
* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-enterprise-agent-6.2.2.x86_64.rpm
 | serverbackup-enterprise-agent-6.2.2.x86_64.rpm ] 
* [ 
http://il-foreman1.slc.westdc.net/pulp/repos/UK2_Group/Library/custom/r1soft_cdp_server/cdp/serverbackup-setup-6.2.2.x86_64.rpm
 | serverbackup-setup-6.2.2.x86_64.rpm ] 

When I attempt to do a yum upgrade using this repo the server fails to download 
the needed, supossadly available, packages with the following error. 

Error Downloading Packages: 
serverbackup-manager-6.2.2-78.x86_64: failure: 
serverbackup-manager-6.2.2.x86_64.rpm from UK2_Group_r1soft_cdp_server_cdp: 
[Errno 256] No more mirrors to try. 

There are not any filtered content views involved here the product activation 
key we use is configured to use the default organization view. 

I'm not sure of what else I should check or how to troubleshoot this issue. 





-- 
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] Smart Class Parameters don't delete

['Jason B. Nance' via Foreman users]

Hi Quentin, 

When you got to Configure -> Puppet classes is your class still listed? 

According to http://projects.theforeman.org/issues/13665 the parameters should 
be removed when the class is. 

Regards, 

j 



From: "Quentin lenglet"  
To: "Foreman Users"  
Sent: Friday, April 28, 2017 3:11:07 AM 
Subject: [foreman-users] Smart Class Parameters don't delete 

Hello everyone 

I have foreman 1.14 on Centos 7. 
I have a big problem. Lots of my smart parameters stay after a desinstallation 
module when i delete my puppet class. 
It's really anoying because i have a least, 70 pages of smart parameters! 

Can you help me pls ? 

Thx a lot 


-- 
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 templates silently reverting...

['Jason B. Nance' via Foreman users]

Hi Gavin, 

The default templates should not be edited in place as they can be overwritten 
during updates and such. Instead, you should clone the template and make 
changes to your clone. 

Regards, 

j 



From: "Gavin Williams"  
To: "Foreman Users"  
Sent: Friday, April 28, 2017 6:33:34 AM 
Subject: [foreman-users] Provisioning templates silently reverting... 

Afternoon all, 
I've got a slightly strange one with a fresh Foreman install, whereby it would 
appear that changes I'm making to the provided Provisioning templates are being 
silently reverted... 

I'm running Foreman 1.14, installed using Foreman-installer, and have made a 
couple of tweaks to the provided 'Kickstart Default Finish' and 'puppet_setup' 
templates, which are recorded in the template history, along with a diff of the 
changes showing the actual changes I made. 
However those changes are no longer present in the template... 

I've had a look through logs etc, but I'm not seeing anything obvious. 

Any ideas? 

Cheers 
Gavin 


-- 
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] Too many open files during a patching operation

['Jason B. Nance' via Foreman users]

Hi Tony, 

Based on the output below this error appears to be coming from yum. Since yum 
transactions typically require root access it would seem that you have limited 
the number of open files for the root user. 

Have you intentionally lowered the number of open files on your system? I would 
check the output of "ulimit -n" on the system that failed. 

Regards, 

j 



From: "Tony Coffman"  
To: "Foreman Users"  
Sent: Monday, April 24, 2017 1:50:20 PM 
Subject: [foreman-users] Too many open files during a patching operation 

I was applying patches to a system yesterday and ran into a problem. 
The yum transaction (initiated from Katello as part of a host_collection update 
operation) failed with a "too many open files" type error. 

Transaction ID : 22 
Begin time : Sun Apr 23 06:58:51 2017 
Begin rpmdb : 577:26374e5863e3ea247fb52909e95e53f8062161aa 
End time : 06:58:56 2017 (5 seconds) 
End rpmdb : 577:26374e5863e3ea247fb52909e95e53f8062161aa 
User : System  
Return-Code : Failure: 1 


Scriptlet output: 
1 error: systemd-libs-219-30.el7_3.8.x86_64: install failed 
2 error: nspr-4.13.1-1.0.el7_3.x86_64: install failed 
3 error: nss-util-3.28.4-1.0.el7_3.x86_64: install failed 
4 error: libgudev1-219-30.el7_3.8.x86_64: install failed 
5 error: libuuid-2.23.2-33.el7_3.2.x86_64: install failed 
6 error: libblkid-2.23.2-33.el7_3.2.x86_64: install failed 
7 error: audit-libs-2.6.5-3.el7_3.1.x86_64: install failed 
8 error: libsss_idmap-1.14.0-43.el7_3.14.x86_64: install failed 
9 error: ipa-common-4.4.0-14.el7.centos.7.noarch: install failed 
10 error: libmount-2.23.2-33.el7_3.2.x86_64: install failed 
11 error: error creating temporary file /var/tmp/rpm-tmp.DO30rh: Too many open 
files 
12 error: Couldn't create temporary file for 
%pre(systemd-219-30.el7_3.8.x86_64): Too many open files 
13 error: systemd-219-30.el7_3.8.x86_64: install failed 
14 error: util-linux-2.23.2-33.el7_3.2.x86_64: install failed 
15 error: error creating temporary file /var/tmp/rpm-tmp.UOeiAX: Too many open 
files 
16 error: Couldn't create temporary file for 
%pre(openssh-6.6.1p1-35.el7_3.x86_64): Too many open files 

Everything after that was just more of the same (Too many open files). 

Do I need to bump up the number of open files for goferd? 

Regards, 
--Tony 



-- 
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] Forman was working, after CentOS update, dead. help?

['Jason B. Nance' via Foreman users]

Hi Scott, 

There's a chance that a default configuration was put in place by an RPM that 
is causing issues. Try running: 

foreman-installer --scenario  --upgrade 

That should fix any configuration issues, at least. 

Regards, 

j 



From: "Scott Lopez"  
To: "Foreman Users"  
Sent: Friday, April 14, 2017 11:20:52 AM 
Subject: [foreman-users] Forman was working, after CentOS update, dead. help? 

Thanks for any assistance in advance! 

I'm at a loss here, out of my depth, and am not finding enough information out 
there to diagnose this myself. I have a Foreman 1.14.3 installation running on 
CentOS 7.3. All was well, today there were a bunch of CentOS upgrades and I 
installed them (I've done this before). I rebooted the server when I had time 
and Foreman now isn't working. There are some Foreman related processes 
running, I've turned on debug and looked over production.log, but I still can't 
find what's wrong. The web-interface isn't running/refusing connections. 

The only message I see of note in the production.log is that postgresql isn't 
available, but it is up and running, so I was thinking that's just a timeout 
issue until postgresql gets up and running. 

Anyone have time to help out a Foreman novice? I've put the contents of 
production.log up at http://termbin.com/jrhv 
Any help would be appreciated! 

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 [ 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] installation media does not show

['Jason B. Nance' via Foreman users]

Hi Travis, 

You're syncing the "base" repo from CentOS, right? I doubt you're doing 
anything wrong. I've not had any consistency in the auto-creation of 
installation media. Out of about a dozen Katello installs I've done I think 
I've only seen the auto-creation happen 2-3 times, and the "Sync Content" radio 
button next to "Media Selection" on the "Operating System" tab of a host group 
is always greyed out for me. 

So sorry I don't have a solution, but know that you aren't alone. They are easy 
to create. The URL will be something like: 

http:///pulp/repos//Library/custom/// 

Regards, 

j 




From: "Travis Camechis"  
To: "Foreman Users"  
Sent: Wednesday, April 12, 2017 2:39:27 PM 
Subject: [foreman-users] installation media does not show 

I have synced a Centos kickstart tree into a product. If I recall this is 
supposed to automatically create installation media for this OS. Currently in 
Katello 3.3 this is not showing up anywhere. I believe this used to work in at 
least Katello 3.1. Am I missing anything ? 
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 [ 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] PLP0034 with Puppet modules sync on Capsule

['Jason B. Nance' via Foreman users]

Ah ha!  There was an update to the puppet-agent RPM which reset the ownership 
on /etc/puppetlabs/code/environments to root:root, but it needs to be 
apache:root for Katello.

So I guess the lesson here is to run foreman-installer ... --upgrade after any 
package update that is related to the whole shebang.



- Original Message -
From: "Foreman Users" 
To: "Foreman Users" 
Sent: Thursday, April 6, 2017 2:20:34 PM
Subject: [foreman-users] PLP0034 with Puppet modules sync on Capsule

Hello,

My Katello 3.2.2 / Foreman 1.13.4 box is failing to sync content views with 
Puppet modules to my Capsule (of the same version) with the following error:

PLP0034: The distributor tkc-holdings-Library-puppet-modules indicated a 
failed response when publishing repository tkc-holdings-Library-puppet-modules.

According to the Googles this has been resolved:

https://access.redhat.com/solutions/2600231

I don't know how to correlate Satellite version numbers to Katello version 
numbers.  Should this be fixed in my version?  If so, is there something more I 
need to do to clean up my Capsule to allow these syncs to work again?

Thanks,

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.

Re: [foreman-users] [Katello] Pulp repos sync on schedule but not showing in katello

['Jason B. Nance' via Foreman users]

Hi Alan, 

In the web UI have you created a sync plan (Content -> Sync Plans) and 
associated that sync plan with each of your products? And if so, are the 
results of those tasks successful (Monitor -> Tasks)? 

Regards, 

j 



From: "Alan Evans"  
To: "Foreman Users"  
Sent: Thursday, April 6, 2017 5:12:54 PM 
Subject: Re: [foreman-users] [Katello] Pulp repos sync on schedule but not 
showing in katello 

Thanks John. 
I've been poking around at this for a couple of days. I have looked at the 
tasks and was going to share but didn't want to overwhelm anyone that tried to 
help. 

A plain 'tasks list' gives nothing. 

$ sudo pulp - admin tasks list 
+--+ 
Tasks 
+--+ 

No tasks found 


tasks list --all, gives a lot, so I'll pull out a few sections 

$ sudo pulp - admin tasks list - a | grep - A5 My_Org - centos - centos - 6 - 
x86_64 - os 
-- 
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository ) 
State : Successful 
Start Time : 2017 - 04 - 05T19 : 31 : 00Z 
Finish Time : 2017 - 04 - 05T19 : 31 : 07Z 
Task Id : dd6e6dac - 5988 - 4cc3 - be6c - 95b223936f98 

-- 
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository ) 
State : Successful 
Start Time : 2017 - 04 - 05T19 : 31 : 07Z 
Finish Time : 2017 - 04 - 05T19 : 31 : 07Z 
Task Id : 2d9ec7cd - de30 - 44d7 - a3b1 - 8a10e1aa7257 

-- 
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository ) 
State : Successful 
Start Time : 2017 - 04 - 06T19 : 36 : 55Z 
Finish Time : 2017 - 04 - 06T19 : 37 : 02Z 
Task Id : d8cb7dac - b13c - 4420 - 83a3 - 432f1c06c635 

-- 
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository ) 
State : Successful 
Start Time : 2017 - 04 - 06T19 : 37 : 02Z 
Finish Time : 2017 - 04 - 06T19 : 37 : 02Z 
Task Id : 19543dbd - fe67 - 4442 - b56e - c3b0d91d695a 

$ TZ = UTC date 
Thu Apr 6 21 : 18 : 46 UTC 2017 

You can see that for the repo centos-6-os repo, pulp has synced and published 
the repo for the last couple of days. But you can see that Katello seems to 
think the last sync was almost a week ago. 

$ hammer repository info -- id 1 
ID : 1 
Name : CentOS 6 x86_64 OS 
Label : centos - 6 - x86_64 - os 
Organization : My Org 
Red Hat Repository : no 
Content Type : yum 
Checksum Type : sha256 
Mirror on Sync : yes 
URL : http : //mirror.centos.org/centos/6/os/x86_64/ 
Publish Via HTTP : yes 
Published At : http : 
//katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/
 
Relative Path : My_Org / Library / custom / centos / centos - 6 - x86_64 - os 
Download Policy : on_demand 
Product : 
ID : 1 
Name : CentOS 
GPG Key : 
ID : 2 
Name : RPM - GPG - KEY - CentOS - 6 
Sync : 
Status : Success 
Last Sync Date : 6 days 
Created : 2017 / 03 / 31 00 : 26 : 52 
Updated : 2017 / 03 / 31 20 : 47 : 13 
Content Counts : 
Packages : 6696 
Package Groups : 214 
Errata : 0 

But get this, if I sync it from Katello it will update. 

$ hammer repository synchronize -- id 1 
[.] [ 100 
%] 
No new packages . 

$ hammer repository info -- id 1 
ID : 1 
Name : CentOS 6 x86_64 OS 
Label : centos - 6 - x86_64 - os 
Organization : My Org 
Red Hat Repository : no 
Content Type : yum 
Checksum Type : sha256 
Mirror on Sync : yes 
URL : http : //mirror.centos.org/centos/6/os/x86_64/ 
Publish Via HTTP : yes 
Published At : http : 
//katello.example.com/pulp/repos/My_Org/Library/custom/centos/centos-6-x86_64-os/
 
Relative Path : My_Org / Library / custom / centos / centos - 6 - x86_64 - os 
Download Policy : on_demand 
Product : 
ID : 1 
Name : CentOS 
GPG Key : 
ID : 2 
Name : RPM - GPG - KEY - CentOS - 6 
Sync : 
Status : Success 
Last Sync Date : 3 minutes 
Created : 2017 / 03 / 31 00 : 26 : 52 
Updated : 2017 / 03 / 31 20 : 47 : 13 
Content Counts : 
Packages : 6696 
Package Groups : 214 
Errata : 670 

$ sudo pulp - admin tasks list - a | grep - A5 My_Org - centos - centos - 6 - 
x86_64 - os 
-- 
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository ) 
State : Successful 
Start Time : 2017 - 04 - 06T21 : 26 : 15Z 
Finish Time : 2017 - 04 - 06T21 : 26 : 22Z 
Task Id : 1565fbd3 - ea26 - 4e43 - 8551 - 40fb8e5b2850 

-- 
Resources : My_Org - centos - centos - 6 - x86_64 - os ( repository ) 
State : Successful 
Start Time : 2017 - 04 - 06T21 : 26 : 22Z 
Finish Time : 2017 - 04 - 06T21 : 26 : 22Z 
Task Id : 75beb6a0 - 0b3f - 4b61 - 8eb9 - a88dc27168e3 

$ TZ = UTC date 
Thu Apr 6 21 : 31 : 49 UTC 2017 

Thank you, 
-Alan 

On Tuesday, April 4, 2017 at 3:36:14 PM UTC-6, John Mitsch wrote: 


Alan, 
I don't have much experience with Sync Plans, but I would expect they would 
create syncing tasks in Katello. You can look at your pulp tasks using 
pulp-admin, see if you see any activity corresponding to your sync plans 

[foreman-users] PLP0034 with Puppet modules sync on Capsule

['Jason B. Nance' via Foreman users]

Hello,

My Katello 3.2.2 / Foreman 1.13.4 box is failing to sync content views with 
Puppet modules to my Capsule (of the same version) with the following error:

PLP0034: The distributor tkc-holdings-Library-puppet-modules indicated a 
failed response when publishing repository tkc-holdings-Library-puppet-modules.

According to the Googles this has been resolved:

https://access.redhat.com/solutions/2600231

I don't know how to correlate Satellite version numbers to Katello version 
numbers.  Should this be fixed in my version?  If so, is there something more I 
need to do to clean up my Capsule to allow these syncs to work again?

Thanks,

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.

Re: [foreman-users] "provisioning" IP for Puppet

['Jason B. Nance' via Foreman users]

The data needed for this is already in the YAML generated by Foreman (and 
hence, the host facts).  I was just hoping that someone else had already gone 
through the work of parsing it as it is buried in hashes so you have to loop 
and test to pull it out.  :-D

It turns out that Puppet (4, at least) does a good enough job at figuring out 
what the "primary" IP of a host is for my needs.  So I can just use ::ipaddress.

Thanks for link to Vox, though.  I'll see if there are any other goodies in 
there I could make use of.

j


- Original Message -
From: "Greg Sutcliffe" <greg.sutcli...@gmail.com>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Monday, April 3, 2017 6:49:39 AM
Subject: Re: [foreman-users] "provisioning" IP for Puppet

On Tuesday, 28 March 2017 23:04:09 BST 'Jason B. Nance' via Foreman users 
wrote:
> Hello,
> 
> Has anyone happened to already have written some code to get the
> "provisioning" IP (provision: true in the foreman_interfaces array) for a
> host for use in a Puppet ERB template?

I'm not aware of any puppet module for working with foreman_interfaces, 
although that would be cool :)

You could use something more generic (like https://github.com/voxpupuli/
puppet-network) and pass in data via the smart parameters - then you'd put 
something like <%= @host.provision_interface.ip %> in your matcher

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

-- 
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] "provisioning" IP for Puppet

['Jason B. Nance' via Foreman users]

Hello,

Has anyone happened to already have written some code to get the "provisioning" 
IP (provision: true in the foreman_interfaces array) for a host for use in a 
Puppet ERB template?

Thanks,

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.

Re: [foreman-users] Run job - send sudo password from Foreman

['Jason B. Nance' via Foreman users]

Hi Diggy, 

I don't know of a way of achieving what you are after, however, I question the 
"more secure" sentiment that is driving this. Sudo is specifically designed to 
try and prevent what you are trying to do because it opens up doors for people 
to gleam passwords and leads to other bad habits. In fact, you cannot just 
"pipe" a password to sudo normally (you have to pass the -S flag). 

So I disagree that using NOPASSWD "clearly ... flies in the face of best 
practices". I also disagree that setting PermitRootLogin to no is "as it should 
be". The "without-password" option is perfectly acceptable in many situations 
when using SSH keys - especially when you include "from=" options in your 
authorized_keys file and such. 

If you have company policies which require a specific design that is one thing, 
but in general keep in mind that there are many different levels of "secure" 
and different people/organizations have different needs/tolerances. For 
example, allowing Foreman to ssh directly as root is fine in my case because 
the logging/auditing in Foreman itself is sufficient to meet our compliance 
requirements. 

Regards, 

j 



From: "Diggy"  
To: "Foreman Users"  
Sent: Monday, March 27, 2017 9:54:37 AM 
Subject: [foreman-users] Run job - send sudo password from Foreman 

Hello, all. 
In my Foreman instance, I've set up job execution (Run job) to work. On my 
hosts, I have ssh PermitRootLogin set to no, as it should be. We log into hosts 
with our own usernames, then run commands via sudo. Thus, in order to get Run 
job to work properly, in Foreman I set Administer > Settings > RemoteExecution 
> r emote_execution_effective_user=root, 
remote_execution_effective_user_method=sudo, and 
remote_execution_ssh_user=asudouser. The only way I could see to make this work 
was to set NOPASSWD in asudouser's sudoer file directive. Clearly, this flies 
in the face of best practices. Is there a way for me to pass asudouser's sudo 
password via Foreman, or is there some more secure way to make Run job work? 

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 [ 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] is gutterball used with foreman/katello?

['Jason B. Nance' via Foreman users]

I'm pretty sure the answer is "no" as there is a step that is ran by 
foreman-installer that is "remove gutterball". 

j 



From: "Cristian Falcas"  
To: "Foreman Users"  
Sent: Friday, March 24, 2017 11:47:55 AM 
Subject: [foreman-users] is gutterball used with foreman/katello? 

Hello, 

Is gutterball still used? I see that the puppet modules have a warning that the 
module is UNMAINTAINED. 

Thank you, 
Cristian Falcas 



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

['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!

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

[foreman-users] logging to deleted files

['Jason B. Nance' via Foreman users]

Hello all,

For some reason I'm having an issue with rotation of some of my Foreman and 
Squid logs.  It appears that the processes aren't releasing the logs and 
continuing to write to the deleted files.  For example:

$ sudo lsof /var/log/ | grep delete
squid  70644  root5u   REG  253,6  7165 2117710 
/var/log/squid/cache.log-20170319 (deleted)
squid  70646 squid5u   REG  253,6  7165 2117710 
/var/log/squid/cache.log-20170319 (deleted)
ruby   70859 foreman-proxy7w   REG  253,6  1042 1050840 
/var/log/foreman-proxy/smart_proxy_dynflow_core.log-20170318 (deleted)
ruby   70968 foreman-proxy7w   REG  253,6 16473 1050819 
/var/log/foreman-proxy/proxy.log-20170318 (deleted)

I'm running Foreman 1.13.4 on CentOS 7 and have not modified the provided 
logrotate.d files, though in my main logrotate.conf I have enabled "compress" 
as a global option.

Any clues as to what may be going on here?

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.

Re: [foreman-users] How to configure web proxy for content syncing

['Jason B. Nance' via Foreman users]

What I mean is that I want Katello to use the web proxy when syncing content 
but I don't want that web proxy used when different components are talking to 
each other (such as the UI hitting Foreman APIs).

j


- Original Message -
From: "Stephen Benjamin" <step...@redhat.com>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Thursday, March 16, 2017 9:07:56 AM
Subject: Re: [foreman-users] How to configure web proxy for content syncing

On Wed, Mar 15, 2017 at 10:34 AM, 'Jason B. Nance' via Foreman users
<foreman-users@googlegroups.com> wrote:
> Hello,
>
> I'm looking for the current "best" way to configure an http proxy for Katello 
> to use to pull down content from upstream.  Are the --katello-proxy-* options 
> to foreman-installer it?  I only want Katello to use the proxy when trying to 
> pull content, not for any other "internal" stuff.
>
> Regards,
>

What's "internal" mean? The proxy settings set by the installer are
used by Katello and pulp for outbound access, we're not setting any
system settings for proxies.  But it'll be used for all content though
even things on the local network, that's a known problem if your proxy
doesn't have access to them. Some users setup a squid proxy until we
let you set a proxy per-repo .
http://projects.theforeman.org/issues/17425

-- 
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] How to configure web proxy for content syncing

['Jason B. Nance' via Foreman users]

Hello,

I'm looking for the current "best" way to configure an http proxy for Katello 
to use to pull down content from upstream.  Are the --katello-proxy-* options 
to foreman-installer it?  I only want Katello to use the proxy when trying to 
pull content, not for any other "internal" stuff.

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.

Re: [foreman-users] Katello 3.3 building CentOS 7 hosts

['Jason B. Nance' via Foreman users]

Here's Puppet Augeas code to disable the stuff if you want to put it in a 
module and preserve the files: 

augeas { 'yum-repo-disable-centos-base': 
context => '/files/etc/yum.repos.d/CentOS-Base.repo/base', 
changes => 'set enabled 0', 
onlyif => 'match name size > 0', 
} 
augeas { 'yum-repo-disable-centos-updates': 
context => '/files/etc/yum.repos.d/CentOS-Base.repo/updates', 
changes => 'set enabled 0', 
onlyif => 'match name size > 0', 
} 
augeas { 'yum-repo-disable-centos-extras': 
context => '/files/etc/yum.repos.d/CentOS-Base.repo/extras', 
changes => 'set enabled 0', 
onlyif => 'match name size > 0', 
} 
augeas { 'yum-repo-disable-centos-cr': 
context => '/files/etc/yum.repos.d/CentOS-CR.repo/cr', 
changes => 'set enabled 0', 
onlyif => 'match name size > 0', 
} 
augeas { 'yum-repo-disable-centos-fasttrack': 
context => '/files/etc/yum.repos.d/CentOS-fasttrack.repo/fasttrack', 
changes => 'set enabled 0', 
onlyif => 'match name size > 0', 
} 



From: "Duncan Innes"  
To: "Foreman Users"  
Cc: "Jason Nance"  
Sent: Wednesday, March 1, 2017 10:00:32 AM 
Subject: Re: [foreman-users] Katello 3.3 building CentOS 7 hosts 

Good point. I've moved the code into the snippet as you suggest. I altered the 
"blow away" code to: 
for repo in `ls /etc/yum.repos.d/*.repo` 
do 
echo "" > $repo 
done 

as per the IRC chat I saw. This fits the bill for now. I'll ensure enabled=0 in 
any CentOS repo at a later date in case the content of the files comes back. 

Cheers, 

D 

On Wednesday, 1 March 2017 14:33:09 UTC, Jason B. Nance wrote: 


You'd have this same problem kickstarting a CentOS system regardless of 
Katello/Foreman. In my opinion it's a problem with how overloaded 
centos-release is (I don't think the yum configurations should be in there for 
this exact reason). Centos-release is absolutely required by a CentOS system 
and it also includes the CentOS mirror yum configurations. By the time your 
installation gets to %post - which is where the subscription-manager snipped is 
executed - centos-release has been installed and the system is aware of the yum 
configurations and uses them. Remember that %post happens inside the newly 
installed system. 

There isn't a way in %post to tell yum to only use the repos that were 
configured to be installed from. So the subscription-manager snippet would have 
to make make some wild assumptions and just generally be overly complex and 
still wouldn't cover all use cases. 

What I've done is put the subscription-manager package in %packages and 
cloned/modified the provided subscription manager snippet to look like this: 

<% if @host.params['kt_activation_keys'] %> 
#blow away default repo files 
/bin/rm -f /etc/yum.repos.d/*.repo 

# add subscription manager 
<% if @host.operatingsystem.atomic? %> 
curl -s <%= subscription_manager_configuration_url(@host, false) %> | 
IS_ATOMIC=true bash 
<% else %> 
# subscription-manager package is installed in %packages section 
rpm -ivh <%= subscription_manager_configuration_url(@host) %> 
<% end %> 

echo "Registering the System" 
subscription-manager register --org="<%= @host.rhsm_organization_label %>" 
--name="<%= @ [ http://host.name/ | host.name ] %>" --activationkey="<%= 
@host.params['kt_activation_keys'] %>" 

<% unless @host.operatingsystem.atomic? %> 
echo "Installing Katello Agent" 
yum -t -y -e 0 install katello-agent 
chkconfig goferd on 
<% end %> 
<% end %> 




From: "Duncan Innes" < [ javascript-blocked: | dun...@innes.net ] > 
To: "Foreman Users" < [ javascript-blocked: | forema...@googlegroups.com ] > 
Sent: Wednesday, March 1, 2017 7:07:40 AM 
Subject: Re: [foreman-users] Katello 3.3 building CentOS 7 hosts 

I've taken the rather extreme option of deleting the "CentOS-*.repo" files from 
/etc/yum.repos.d/ at the start of the %post section. Bit harsh, but it proved 
the theory was sound. I can now perform successful builds with no external 
access. 
This can't be the 'right' way to do it though. Is this the way the 
subscription_manager_registration snippet is supposed to work? 

On Wednesday, 1 March 2017 12:10:15 UTC, Duncan Innes wrote: 
BQ_BEGIN

Do you do that during kickstart or once booted? I think at the point of trying 
to install subscription-manager, my hosts only have the external repos 
configured, so there's no way to satisfy the install internally. 
I've edited the Katello Kickstart Default template to include 
subscription-manager in the initial %packages list. This means it's already 
there when the subscription_manager_registration snippet is run. But the yum 
commands still fail if I remove internet access as I've not "enabled=0" to all 
the external repos at this point. 

Shouldn't the subscription_manager_registration snippet be capable of 
installing subscription-manager without internet access? 

D 

On Wednesday, 1 March 2017 11:00:46 UTC, Lachlan Musicman wrote: 
BQ_BEGIN

I don't know if there's an automagic 

Re: [foreman-users] Puppet 4 and foreman

['Jason B. Nance' via Foreman users]

For Puppet 4 I enable the Puppet Labs PC 1 repo (as well as the 
Foreman-specific repos) and then run foreman-installer, which will result in 
Foreman with Puppet 4. 

Regards, 

j 



From: anothermailbo...@gmail.com 
To: "Foreman Users"  
Sent: Wednesday, March 1, 2017 8:54:47 AM 
Subject: [foreman-users] Puppet 4 and foreman 


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 [ 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] Katello 3.3 building CentOS 7 hosts

['Jason B. Nance' via Foreman users]

You'd have this same problem kickstarting a CentOS system regardless of 
Katello/Foreman. In my opinion it's a problem with how overloaded 
centos-release is (I don't think the yum configurations should be in there for 
this exact reason). Centos-release is absolutely required by a CentOS system 
and it also includes the CentOS mirror yum configurations. By the time your 
installation gets to %post - which is where the subscription-manager snipped is 
executed - centos-release has been installed and the system is aware of the yum 
configurations and uses them. Remember that %post happens inside the newly 
installed system. 

There isn't a way in %post to tell yum to only use the repos that were 
configured to be installed from. So the subscription-manager snippet would have 
to make make some wild assumptions and just generally be overly complex and 
still wouldn't cover all use cases. 

What I've done is put the subscription-manager package in %packages and 
cloned/modified the provided subscription manager snippet to look like this: 

<% if @host.params['kt_activation_keys'] %> 
#blow away default repo files 
/bin/rm -f /etc/yum.repos.d/*.repo 

# add subscription manager 
<% if @host.operatingsystem.atomic? %> 
curl -s <%= subscription_manager_configuration_url(@host, false) %> | 
IS_ATOMIC=true bash 
<% else %> 
# subscription-manager package is installed in %packages section 
rpm -ivh <%= subscription_manager_configuration_url(@host) %> 
<% end %> 

echo "Registering the System" 
subscription-manager register --org="<%= @host.rhsm_organization_label %>" 
--name="<%= @host.name %>" --activationkey="<%= 
@host.params['kt_activation_keys'] %>" 

<% unless @host.operatingsystem.atomic? %> 
echo "Installing Katello Agent" 
yum -t -y -e 0 install katello-agent 
chkconfig goferd on 
<% end %> 
<% end %> 




From: "Duncan Innes"  
To: "Foreman Users"  
Sent: Wednesday, March 1, 2017 7:07:40 AM 
Subject: Re: [foreman-users] Katello 3.3 building CentOS 7 hosts 

I've taken the rather extreme option of deleting the "CentOS-*.repo" files from 
/etc/yum.repos.d/ at the start of the %post section. Bit harsh, but it proved 
the theory was sound. I can now perform successful builds with no external 
access. 
This can't be the 'right' way to do it though. Is this the way the 
subscription_manager_registration snippet is supposed to work? 

On Wednesday, 1 March 2017 12:10:15 UTC, Duncan Innes wrote: 


Do you do that during kickstart or once booted? I think at the point of trying 
to install subscription-manager, my hosts only have the external repos 
configured, so there's no way to satisfy the install internally. 
I've edited the Katello Kickstart Default template to include 
subscription-manager in the initial %packages list. This means it's already 
there when the subscription_manager_registration snippet is run. But the yum 
commands still fail if I remove internet access as I've not "enabled=0" to all 
the external repos at this point. 

Shouldn't the subscription_manager_registration snippet be capable of 
installing subscription-manager without internet access? 

D 

On Wednesday, 1 March 2017 11:00:46 UTC, Lachlan Musicman wrote: 
BQ_BEGIN

I don't know if there's an automagic way to do it, but I use ansible to change 
all files in /etc/yum.repos.d/ except "redhat.repo". In each file change any 
enabled =1 to enabled = 0. 

cheers 
L. 

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

- Grace Hopper 

On 1 March 2017 at 21:55, Duncan Innes < dun...@innes.net > wrote: 

BQ_BEGIN

Hi, 
I've built a new Katello 3.3 system and loaded it up with CentOS 7, EPEL, and 
Katello Client 3.3 channels. The various repositories have been synched 
(although lazy sync). Content View, Activation Key etc created. 

When I build a new system, however, the installation of subscription-manager 
appears to be heading out to the internet rather than finding the relevant 
packages from the Katello server. The top of my install.post.log reads: 

updating system time 
Loaded plugins: fastestmirror 
Determining fastest mirrors 
* base: [ http://mirror.sax.uk.as61049.net/ | mirror.sax.uk.as61049.net ] 
* extras: [ http://mirror.bytemark.co.uk/ | mirror.bytemark.co.uk ] 
* updates: [ http://mirrors.coreix.net/ | mirrors.coreix.net ] 
Resolving Dependencies 
--> Running transaction check 
---> Package subscription-manager.x86_64 0:1.17.15-1.el7.centos will be 
installed 
--> Processing Dependency: python-rhsm >= 1.17.0 for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64 
--> Processing Dependency: usermode for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64 
--> Processing Dependency: python-ethtool for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64 
--> Processing Dependency: python-dmidecode for package: 
subscription-manager-1.17.15-1.el7.centos.x86_64 
--> Processing Dependency: python-dateutil for package: 

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

['Jason B. Nance' via Foreman users]

Hi Tomas, 

Check out my reply in the following thread: 

https://groups.google.com/d/msg/foreman-users/q_Qr9sg2PJs/XUN8YEeMDAAJ 

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" <tha...@gmail.com> 
To: "Foreman Users" <foreman-users@googlegroups.com> 
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 | 
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 < [ 
mailto:foreman-users@googlegroups.com | foreman-users@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" < [ mailto:tha...@gmail.com | tha...@gmail.com ] > 
To: "Foreman Users" < [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] > 
Sent: Friday, February 24, 2017 6:25:37 PM 
Subject: [foreman-users] Recommendations for products with discovered 
repositories and subscriptions for content hosts 

Greetings, 
I have a Satellite 6.2.7 installation and I am adding third party repositories 
using the Discover Repositories function within a product. For example, I add 
the EPEL repositories with the url [ https://dl.fedoraproject.org/pub/epel | 
https://dl.fedoraproject.org/pub/epel ] . The repos get discovered for EL 5,6,7 
and various architectures (x86_64, i386, etc.). I select those that I am 
interested in and this all works fine. However, when I register a content host 
(subscription-manager register --org "Organization" I noticed that the host 
sees all of the available repositories from that product and not just those 
specific to it's RHEL version or architecture. So my RHEL 6 x86_64 system now 
has access RHEL 5 and RHEL 7 packages. 
Does any one have a recommendation or best practice for how to deal with 
external repositories like this. It seems that the Red Hat repositories with 
their related products seem to do this such that the system registered only 
sees repositories for its relevant RHEL version and arch. I know that there are 
a number of ways to do this 

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

['Jason B. Nance' via Foreman users]

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 

Greetings, 
I have a Satellite 6.2.7 installation and I am adding third party repositories 
using the Discover Repositories function within a product. For example, I add 
the EPEL repositories with the url https://dl.fedoraproject.org/pub/epel. The 
repos get discovered for EL 5,6,7 and various architectures (x86_64, i386, 
etc.). I select those that I am interested in and this all works fine. However, 
when I register a content host (subscription-manager register --org 
"Organization" I noticed that the host sees all of the available repositories 
from that product and not just those specific to it's RHEL version or 
architecture. So my RHEL 6 x86_64 system now has access RHEL 5 and RHEL 7 
packages. 
Does any one have a recommendation or best practice for how to deal with 
external repositories like this. It seems that the Red Hat repositories with 
their related products seem to do this such that the system registered only 
sees repositories for its relevant RHEL version and arch. I know that there are 
a number of ways to do this manually with activation keys or specifying within 
each host entry in Satellite what repositories within a product are on by 
default but is there a better or simpler way. I considered creating products 
specific to arch and version but that seems just as difficult to manage. If all 
all possible I'd prefer that the content host only be able to subscribe to 
repositories that are relevant to arch and version. 
I hope that my question makes sense, if not I can try to clarify. Any advice on 
this would be much appreciated. 
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 [ 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] Programmatic method for finding content views?

['Jason B. Nance' via Foreman users]

You have lots of options. 

The API: 
https:///apidoc/v2/content_views.html 

Nailgun: 
https://github.com/SatelliteQE/nailgun 

Various projects here: 
https://github.com/RedHatSatellite 




From: "Lachlan Musicman"  
To: "Foreman Users"  
Sent: Wednesday, February 22, 2017 4:39:58 PM 
Subject: [foreman-users] Programmatic method for finding content views? 

I have become comfortable with the Foreman/Katello GUI, but sometimes I want an 
easy way to find a list of Composite Content Views, their versions, what 
Content View is in each version of said Composite Content View, and what that 
version is. 

eg: 

list CCVs 

CCV Worker Node 
v5.0: 
- base centos 7.2 v4.0 
- extras v3.0 
- sssd@copr v2.0 

v4.0: 
- base centos 7.2 v3.0 
- extras v3.0 
- sssd@copr v2.0 

v3.0: 
- base centos 7.2 v3.0 
- extras v2.0 
- sssd@copr v1.0 

CCV Head Node 
v3.0: 
- base centos 7.2 v4.0 
- extras v3.0 
- sssd@copr v2.0 

CCV Utils 
v6.0 
- base centos 7.2 v4.0 
- extras v3.0 
- sssd@copr v2.0 
- forman v4.0 
- zabbix v2.0 

Is there a way to do that using a command line tool? (GUI is ok too) 

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 [ 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: Pulp streamer is looking for non directory

['Jason B. Nance' via Foreman users]

I was wondering if perhaps you were running into this: 

http://projects.theforeman.org/issues/17715 

But it is a bit tricky to track down... 

j 




From: "Lachlan Musicman"  
To: "Foreman Users"  
Sent: Wednesday, February 22, 2017 4:32:00 PM 
Subject: [foreman-users] Re: Pulp streamer is looking for non directory 

I seem to have solved this problem. While reading 

[ https://bugzilla.redhat.com/show_bug.cgi?id=1330042 | 
https://bugzilla.redhat.com/show_bug.cgi?id=1330042 ] 

I found what I was looking for in [ 
https://bugzilla.redhat.com/show_bug.cgi?id=1330042#c17 | 
https://bugzilla.redhat.com/show_bug.cgi?id=1330042#c17 ] (" 

Use case I would think of: 
- The repository is corrupt - we don't trust it 
All we want is a full (brute force) sync to rebuild it.") 

Then I saw that someone else mentioned the Download policy. For some reason it 
was set to "On Demand". 

Changing it to Immediate and performing a resync worked. 

cheers 
L. 


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

- Grace Hopper 

On 22 February 2017 at 11:35, Lachlan Musicman < [ mailto:data...@gmail.com | 
data...@gmail.com ] > wrote: 
> 
> Hola, 
> 
> I am seeing a lot of errors because one repository seems to be off kilter. 
> 
> The directory that it is publishing as being where the various rpms can be 
> found doesn't exist on the file system. 
> 
> The symptoms I see on the content hosts are failures to update 
> 
> 
> [ 
> https://katello.petermac.org.au/pulp/repos/PMCC/Worker/Node/custom/ELRepo_org_Community_Enterprise_Linux_Repository_for_el7/elrepo-mainline-kernel/kernel-ml-4.9.8-1.el7.elrepo.x86_64.rpm
>  | 
> https://katello.petermac.org.au/pulp/repos/PMCC/Worker/Node/custom/ELRepo_org_Community_Enterprise_Linux_Repository_for_el7/elrepo-mainline-kernel/kernel-ml-4.9.8-1.el7.elrepo.x86_64.rpm
>  ] : [Errno 14] HTTPS Error 404 - Not Found 
> 
> [ https://access.redhat.com/articles/1320623 | 
> https://access.redhat.com/articles/1320623 ] 
> 
> which ends with an "error downloading packages" error. 
> 
> The repo exists and is syncing correctly. 
> 
> On the server, in the messages, I'm seeing: 
> 
> Feb 22 11:21:42 katello pulp_streamer: [-] 127.0.0.1 - - 
> [22/Feb/2017:00:21:41 +] "GET 
> /var/lib/pulp/content/units/rpm/43/697e454f4bd11a054a035a756afee9405c3f84882b7bdb3594ee9414e008c5/kernel-ml-4.9.8-1.el7.elrepo.x86_64.rpm
>  HTTP/1.1" 404 - "-" "urlgrabber/3.10 yum/3.4.3" 
> 
> In this case the long string directory doesn't exist. 
> 
> /var/lib/pulp/content/units/rpm/43 is there 
> 
> 697e454f4bd11a054a035a756afee9405c3f84882b7bdb3594ee9414e008c5 is not. 
> 
> kernel-ml-4.9.8-1.el7.elrepo.x86_64.rpm is available in a couple of places, 
> but not 
> 
> /var/lib/pulp/content/ 
> 
> only 
> 
> /var/lib/pulp/published/ 
> 
> What has gone wrong and how can it be fixed? 
> 
> 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 [ 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.

[foreman-users] How to tell cause of mismatch

['Jason B. Nance' via Foreman users]

Hello,

I have a Katello/Foreman server and a Capsule/Smart Proxy server in a different 
data center (read: location).  As far as I can tell, all hosts are pointing to 
the respective server in their data center.  However, the location with the 
Capsule/SP is telling me that the main Katello/TFM server is in use by a host 
(via editing the location and/or running a mismatch report).

Location/Organization   Mismatch Details
OM1 (Location)  sl1mmgplsat0001.ipa.gen.zone (SmartProxy) 

How can I determine which host is causing this mismatch?  Is it the 
Capsule/Smart Proxy itself that causes this?

Thanks,

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.

Re: [foreman-users] Error when trying to update foreman

['Jason B. Nance' via Foreman users]

rubygem-rack-protection is provided by EPEL, which currently has 1.5.3 
available. 

j 



From: "Cristian Falcas"  
To: "Foreman Users"  
Sent: Tuesday, February 21, 2017 10:12:12 AM 
Subject: [foreman-users] Error when trying to update foreman 

Hi, 

I get the following error when trying to u[pdate foreman: 

--> Finished Dependency Resolution 
Error: Package: 1:rubygem-sinatra-1.4.7-1.el7.noarch (foreman) 
Requires: rubygem(rack-protection) >= 1.4.0 
Installed: rubygem-rack-protection-1.3.2-3.el7.noarch (@foreman) 
rubygem(rack-protection) = 1.3.2 

Is the new rpm for rubygem-rack-protection somewhere else? In the official 
foreman repo the latest version is still 1.3.x 

Thank you, 
Cristian Falcas 



-- 
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] Generic Image For Capsule

['Jason B. Nance' via Foreman users]

In the boot disk drop down I would most likely change subnet image to content 
host image, though I can see how that is misleading since the image isn't 
really based on the selected content host but the subnet configuration.  How 
about Capsule/Smart Proxy generic image instead?

I would name the ISO the same way the generic image is, though, since it is the 
same as the generic but pointed at the Capsule/Smart Proxy.

j


- Original Message -
From: "Lukas Zapletal" <l...@redhat.com>
To: "Foreman Users" <foreman-users@googlegroups.com>
Cc: "Jason Nance" <ja...@tresgeek.net>
Sent: Tuesday, February 21, 2017 1:33:32 AM
Subject: Re: [foreman-users] Generic Image For Capsule

Ok, guys what label would you recommend then? My eyes are very biased
after these years spending on this codebase, help! :-)

LZ

On Thu, Feb 16, 2017 at 5:40 AM, Andrew Schofield <a...@ourhavens.co.uk> wrote:
> I found that out the hard way a while back too Jason. This should be more
> visible on the UI somewhere!
>
> On Wednesday, February 15, 2017 at 9:58:09 AM UTC-5, Jason B. Nance wrote:
>>
>> Ahh... this is much simpler than I though.  The "subnet" image basically
>> is the "generic" image just pointing to the Capsule/Smart Proxy.  The name
>> of the ISO was what was throwing me off.  I thought there was something
>> subnet-specific in there, but after mounting and comparing I see otherwise.
>>
>> j
>>
>>
>> - Original Message -
>> From: "Foreman Users" <forema...@googlegroups.com>
>> To: "Foreman Users" <forema...@googlegroups.com>
>> Sent: Wednesday, February 15, 2017 8:44:18 AM
>> Subject: Re: [foreman-users] Generic Image For Capsule
>>
>> Hi Lukas,
>>
>> I already had the settings as you indicated but the generic image for this
>> host is pointing to the primary Katello/Foreman server.  I tried cancelling
>> the build and clicking build again but results were same.
>>
>> Am I misunderstanding how this should work?  Is the "generic" image always
>> the same regardless of content host/location/subnet?  Should I be using the
>> subnet image instead?
>>
>> Thanks,
>>
>> j
>>
>>
>> - Original Message -
>> From: "Lukas Zapletal" <lz...@redhat.com>
>> To: "Foreman Users" <forema...@googlegroups.com>
>> Sent: Wednesday, February 15, 2017 5:54:41 AM
>> Subject: Re: [foreman-users] Generic Image For Capsule
>>
>> Make sure both TFTP and Templates features are enabled on Subnet
>> proxy, then rebuild the host (hit Build button) and you should see
>> templated bootdisk.
>>
>> Can you please upvote this bug? I want to start counting on this,
>> other users often hit this.
>>
>> http://projects.theforeman.org/issues/17316
>>
>> LZ
>>
>> On Tue, Feb 14, 2017 at 3:59 PM, 'Jason B. Nance' via Foreman users
>> <forema...@googlegroups.com> wrote:
>> > Hello,
>> >
>> > After creating a new host I can download the generic image, which can be
>> > used to boot/install the host.  This generic image points at the
>> > Katello/Foreman server itself.  How do I download a generic image that
>> > points at a Capsule/Smart Proxy?
>> >
>> > I've tried creating a host and setting its content source to the Capsule
>> > but the generic boot disk still points at the primary Kat/TFM server.
>> >
>> > Thanks,
>> >
>> > 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-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-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.
>>
>> --
>> You recei

Re: [foreman-users] Generic Image For Capsule

['Jason B. Nance' via Foreman users]

Ahh... this is much simpler than I though.  The "subnet" image basically is the 
"generic" image just pointing to the Capsule/Smart Proxy.  The name of the ISO 
was what was throwing me off.  I thought there was something subnet-specific in 
there, but after mounting and comparing I see otherwise.

j


- Original Message -
From: "Foreman Users" <foreman-users@googlegroups.com>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Wednesday, February 15, 2017 8:44:18 AM
Subject: Re: [foreman-users] Generic Image For Capsule

Hi Lukas,

I already had the settings as you indicated but the generic image for this host 
is pointing to the primary Katello/Foreman server.  I tried cancelling the 
build and clicking build again but results were same.

Am I misunderstanding how this should work?  Is the "generic" image always the 
same regardless of content host/location/subnet?  Should I be using the subnet 
image instead?

Thanks,

j


- Original Message -
From: "Lukas Zapletal" <l...@redhat.com>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Wednesday, February 15, 2017 5:54:41 AM
Subject: Re: [foreman-users] Generic Image For Capsule

Make sure both TFTP and Templates features are enabled on Subnet
proxy, then rebuild the host (hit Build button) and you should see
templated bootdisk.

Can you please upvote this bug? I want to start counting on this,
other users often hit this.

http://projects.theforeman.org/issues/17316

LZ

On Tue, Feb 14, 2017 at 3:59 PM, 'Jason B. Nance' via Foreman users
<foreman-users@googlegroups.com> wrote:
> Hello,
>
> After creating a new host I can download the generic image, which can be used 
> to boot/install the host.  This generic image points at the Katello/Foreman 
> server itself.  How do I download a generic image that points at a 
> Capsule/Smart Proxy?
>
> I've tried creating a host and setting its content source to the Capsule but 
> the generic boot disk still points at the primary Kat/TFM server.
>
> Thanks,
>
> 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.



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

-- 
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] Generic Image For Capsule

['Jason B. Nance' via Foreman users]

Hello,

After creating a new host I can download the generic image, which can be used 
to boot/install the host.  This generic image points at the Katello/Foreman 
server itself.  How do I download a generic image that points at a 
Capsule/Smart Proxy?

I've tried creating a host and setting its content source to the Capsule but 
the generic boot disk still points at the primary Kat/TFM server.

Thanks,

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.

Re: [foreman-users] CV publishing errors

['Jason B. Nance' via Foreman users]

Are you using the user/pass from the "default_login" and "default_password" in 
/etc/pulp/server.conf? 

j 




From: "Lachlan Musicman"  
To: "Foreman Users"  
Sent: Thursday, February 9, 2017 4:58:03 PM 
Subject: Re: [foreman-users] CV publishing errors 

/var/log/messages shows 

pulp.server.webservices.middleware.exception:INFO: Authentication with username 
admin failed: invalid username or password 

cheers 
L. 

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

- Grace Hopper 

On 10 February 2017 at 09:42, Lachlan Musicman < [ mailto:data...@gmail.com | 
data...@gmail.com ] > wrote: 



That didn't work either :/ same error. 


[root@vmpr-res-utils ~]# pulp-admin login -u admin -p admin 
The specified user does not have permission to execute the given command 


cheers 
L. 

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

- Grace Hopper 

On 10 February 2017 at 09:39, Tom McKay < [ mailto:thomasmc...@redhat.com | 
thomasmc...@redhat.com ] > wrote: 

BQ_BEGIN

Try including the -u admin -p admin on all the pulp-admin commands 

On Thu, Feb 9, 2017 at 5:30 PM, Lachlan Musicman < [ mailto:data...@gmail.com | 
data...@gmail.com ] > wrote: 

BQ_BEGIN

CentOS 7.3.1611, foreman 1.13.4, katello 3.2.2, pulp* 2.9.3, 

When I try to publish a CV, I get this error 


Actions::Pulp::Repository::CopyYumMetadataFile 


{"source_pulp_id"=> 
"Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_sssd-Copr_repository_for_sssd_1_15", 
"target_pulp_id"=> 
"Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_repository_for_sssd_1_15",
 
"clauses"=>nil, 
"remote_user"=>"admin", 
"remote_cp_user"=>"admin"} 

{"pulp_tasks"=> 
[{"exception"=>nil, 
"task_type"=> 
"pulp.server.managers.repo.unit_association.associate_from_repo", 
"_href"=>"/pulp/api/v2/tasks/39286b9b-7684-4b1c-b092-bc593d4ca46d/", 
"task_id"=>"39286b9b-7684-4b1c-b092-bc593d4ca46d", 
"tags"=> 
["pulp:repository:Peter_MacCallum_Cancer_Centre-Gaffa-dev-GAFFA-_sssd-Copr_repository_for_sssd_1_15",
 
"pulp:repository:Peter_MacCallum_Cancer_Centre-GAFFA-2_0-_sssd-Copr_repository_for_sssd_1_15",
 
"pulp:action:associate"], 
"finish_time"=>"2017-02-09T21:29:59Z", 
"_ns"=>"task_status", 
"start_time"=>"2017-02-09T21:29:59Z", 
"traceback"=> 
"Traceback (most recent call last):\n File 
\"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 240, in 
trace_task\n R = retval = fun(*args, **kwargs)\n File 
\"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 484, in 
__call__\n return super(Task, self).__call__(*args, **kwargs)\n File 
\"/usr/lib/python2.7/site-packages/pulp/server/async/tasks.py\", line 103, in 
__call__\n return super(PulpTask, self).__call__(*args, **kwargs)\n File 
\"/usr/lib/python2.7/site-packages/celery/app/trace.py\", line 437, in 
__protected_call__\n return self.run(*args, **kwargs)\n File 
\"/usr/lib/python2.7/site-packages/pulp/server/managers/repo/unit_association.py\",
 line 273, in associate_from_repo\n units=transfer_units)\n File 
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/importer.py\",
 line 58, in import_units\n return associate.associate(source_repo, dest_repo, 
import_conduit, config, units)\n File 
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
 line 53, in associate\n associated_units = set([_associate_unit(dest_repo, 
unit) for unit in units])\n File 
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
 line 339, in _associate_unit\n return associate_copy_for_repo(unit, dest_repo, 
True)\n File 
\"/usr/lib/python2.7/site-packages/pulp_rpm/plugins/importers/yum/associate.py\",
 line 379, in associate_copy_for_repo\n 
new_unit.safe_import_content(unit._storage_path)\n File 
\"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\", line 
905, in safe_import_content\n self.import_content(path, location)\n File 
\"/usr/lib/python2.7/site-packages/pulp/server/db/model/__init__.py\", line 
879, in import_content\n storage.put(self, path, location)\n File 
\"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\", line 123, 
in put\n mkdir(os.path.dirname(destination))\n File 
\"/usr/lib/python2.7/site-packages/pulp/server/content/storage.py\", line 20, 
in mkdir\n os.makedirs(path)\n File \"/usr/lib64/python2.7/os.py\", line 157, 
in makedirs\n mkdir(name, mode)\nPulpExecutionException: Pulp exception 
occurred: PulpExecutionException\n", 
"spawned_tasks"=>[], 
"progress_report"=>{}, 
"queue"=> 
"reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au.dq", 
"state"=>"error", 
"worker_name"=> 
" [ mailto:reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au | 
reserved_resource_worke...@vmpr-res-utils.unix.petermac.org.au ] ", 
"result"=>nil, 
"error"=> 
{"code"=>"PLP", 
"data"=>{}, 
"description"=>"Pulp exception occurred: PulpExecutionException", 

Re: [foreman-users] "Planning" taking forever

['Jason B. Nance' via Foreman users]

I only have 1 version of each of my CVs as it is. :-\ 




From: "Lachlan Musicman" <data...@gmail.com> 
To: "Foreman Users" <foreman-users@googlegroups.com> 
Sent: Thursday, February 9, 2017 5:02:36 PM 
Subject: Re: [foreman-users] "Planning" taking forever 

I found that reducing the number of versions of CVs helped - clearing out old 
versions that weren't used any more. 

cheers 
L. 

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

- Grace Hopper 

On 10 February 2017 at 09:56, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 


In the past week or two I've noticed that when I go to publish a new version of 
a CV or promote it the "Planning" phase is taking 30-60 minutes or even more. 
Mongodb is hogging all of the resources. This is on Katello 3.2.2, Foreman 
1.13.4, CentOS 7.3+. 

Anyone else experiencing this or found a solution? 

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 [ mailto:foreman-users%2bunsubscr...@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 [ 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] realm provider?

['Jason B. Nance' via Foreman users]

Hello Jason, 

It appears that this is still under development, though may be close: 

http://projects.theforeman.org/issues/4917 

https://github.com/theforeman/smart-proxy/pull/480 

Depending on your tolerance for "uh ohs" you may be able to use that pull 
request to implement this earlier. 

Regards, 

j 



From: "Jason McMahan"  
To: "Foreman Users"  
Sent: Wednesday, February 8, 2017 1:57:44 PM 
Subject: [foreman-users] realm provider? 

Good day, 
I was looking over realms in foreman and noticed there is a realm type of 
active directory. 
Is there any information to setup/configure connecting to a realm provider of 
active directory? 

Unless i misunderstood what realms were for it appears that it could connect to 
active directory and allow creation of computer/host objects. 

Thank you in advance for any help. 


-- 
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] composite content view use latest version

['Jason B. Nance' via Foreman users]

This sounds similar to the "restrict_composite_view" option. Perhaps it could 
be an extension of that functionality. 



From: "Tom McKay"  
To: "Foreman Users"  
Sent: Saturday, January 28, 2017 9:16:15 AM 
Subject: [foreman-users] composite content view use latest version 

After playing around with composite content views today, I wonder if others may 
agree with the need for an RFE: 

I have a CV "RHEL Atomic Host" and another cv "Solr" that I've combined into 
CCV "Solr Appliance". I've chosen to use latest of both CVs in the CCV. Now 
here's the problem: I want to use the latest CV versions from a specific 
lifecycle environment, namely Production. 

The problem is that if I publish a new version of CV Solr, I'd want to wait to 
consume it in my CCV until it reaches the Production lifecycle environment. 

The RFE would be "As a user, I want to choose the lifecycle environment to use 
when determining the version for a component CV in a CCV." 

The current tooling forces the lifecycle environment to always be Library. This 
would, or course, still be an option and the default. 

Thoughts? 


-- 
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] pxe provisioning issue

['Jason B. Nance' via Foreman users]

Lars, 

It would be helpful if you could provide some error messages from the host 
(such as the URL it is attempting to use to pull the kickstart). I ran into a 
similar issue that had to do with templates, but I don't want to lead you 
astray. 

j 




From: "Lars"  
To: "Foreman Users"  
Sent: Wednesday, January 25, 2017 9:28:26 AM 
Subject: [foreman-users] pxe provisioning issue 

I've been trying to get pxe unattended to work with Foreman (satellite) but 
keep hitting a wall. 
When i provision a new host, it boots but when it needs to download the ks file 
it always time outs. 
There's an error about the ks could not be fetched, connection timed out. 

Don't know where to look to resolve this as i cant find anything helpful in the 
docs. 

kind regards, 


-- 
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] Cannot delete the default Location

['Jason B. Nance' via Foreman users]

Ah, I see:

https://bugzilla.redhat.com/show_bug.cgi?id=1268012

http://projects.theforeman.org/issues/18226



- Original Message -
From: "Foreman Users" 
To: "Foreman Users" 
Sent: Tuesday, January 24, 2017 2:09:47 PM
Subject: [foreman-users] Cannot delete the default Location

Hello,

When attempting to delete a location in 3.2.2/1.13.3 I get the following error:

Cannot delete the default Location

Where do I change the default location so that I can delete this one?

No hosts are using this location.

Thanks,

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.

[foreman-users] Cannot delete the default Location

['Jason B. Nance' via Foreman users]

Hello,

When attempting to delete a location in 3.2.2/1.13.3 I get the following error:

Cannot delete the default Location

Where do I change the default location so that I can delete this one?

No hosts are using this location.

Thanks,

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.

Re: [foreman-users] Could not retrieve catalog from remote server: Error 400 on SERVER: Failed when searching for node

['Jason B. Nance' via Foreman users]

Hi Manoj, 

Depending on your Puppet version you may want to look at one of these 
parameters (on your client): 

https://docs.puppet.com/puppet/latest/configuration.html#configtimeout 

https://docs.puppet.com/puppet/latest/configuration.html#httpconnecttimeout 

https://docs.puppet.com/puppet/latest/configuration.html#httpreadtimeout 

HTH, 

j 




From: "Manoj Potluri"  
To: "Foreman Users"  
Sent: Monday, January 23, 2017 3:18:53 PM 
Subject: [foreman-users] Could not retrieve catalog from remote server: Error 
400 on SERVER: Failed when searching for node 


I am running into a weird problem for one of my nodes, the yml file for this 
specific node is 22k lines (its because this node has so many interfaces 1600+ 
and is running docker ) this is a test box. 

Puppet agent fails to complete with (Error 400 on SERVER: Failed when searching 
for node test01.lab.net: Failed to find test01.lab.net via exec: Execution of 
'/etc/puppet/node.rb test01.lab.net' returned 1). when i run the script from 
puppet master i get back the yaml response in 25+sec. 
When looked in the production.log file, there are no errors. 

2017-01-23 14:20:20 [app] [I] Started GET "/node/ test01.lab.net ?format=yml" 
for 10.52.55.54 at 2017-01-23 14:20:20 -0600 
2017-01-23 14:20:20 [app] [I] Processing by HostsController#externalNodes as 
YML 
2017-01-23 14:20:20 [app] [I] Parameters: {"name"=>" test01.lab.net "} 
I dont see a corresponding COMPELTED line in the production.log file. REf: 
http://stackoverflow.com/questions/38345818/puppet-agent-unable-to-retrieve-catalog-from-master-when-using-enc-error-400-on
 
is there a timeout value when puppet agent runs to retrieve the catalog? 
I checked the YML responce and ran it trough "ruby -e "require 'yaml'; 
YAML.load_file('test.yaml')" and did not see any yaml related syntax errors. " 

Any thoughts on how i can debug this issue? please let me know. 

Thanks, 
Manoj. 


-- 
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] Web Components Stop Responding

['Jason B. Nance' via Foreman users]

It says: 

ERROR: Phusion Passenger doesn't seem to be running. 

Though that is what it says when things are working, as well. 

Should I be running that as a user other than root or something? 

j 




From: "Christopher Duryee"  
To: "Foreman Users"  
Sent: Tuesday, January 17, 2017 10:30:29 AM 
Subject: Re: [foreman-users] Web Components Stop Responding 

does 'passenger-status' show anything interesting? 

-- 
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] Web Components Stop Responding

['Jason B. Nance' via Foreman users]

  0 172.16.246.31:53340 172.16.246.31:443   ESTABLISHED
tcp6   0  0 :::80   :::*LISTEN
tcp6   0  0 :::8080 :::*LISTEN
tcp6   0  0 :::443  :::*LISTEN
tcp6   0  0 :::8443 :::*LISTEN
tcp6   0  0 127.0.0.1:8005  :::*LISTEN
tcp6   0  0 :::8009 :::*LISTEN
tcp6  32  0 172.16.246.31:443   172.16.246.31:53482 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53170 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.240:58842ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53476 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53488 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.240:58778ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53376 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.31:53324 ESTABLISHED
tcp6   0  0 172.16.246.31:443   172.16.246.31:53340 ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53510 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53256 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53146 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53502 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.240:58774ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53304 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53450 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53140 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53486 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53456 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53454 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53492 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53370 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53498 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53156 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.240:58848ESTABLISHED
tcp6   0  0 172.16.246.31:443   172.16.246.240:58854ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53472 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53506 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53528 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53344 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53518 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53500 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53466 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53504 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53364 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.240:58838ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53428 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53470 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53494 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53530 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53378 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.31:53508 ESTABLISHED
tcp6   0  0 172.16.246.31:443   172.16.246.31:53514 ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53218 CLOSE_WAIT
udp0  0 0.0.0.0:51680   0.0.0.0:*




- Original Message -
From: "Jason Nance" <ja...@tresgeek.net>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Thursday, January 12, 2017 2:22:51 PM
Subject: Re: [foreman-users] Web Components Stop Responding

Not sure what was going on.  I typically have fewer than 10 hosts connected to 
this lab install which was hanging.  I updated it to 3.2.2/1.13.3 on Monday and 
have debug logging on and haven't seen the issue reappear.

*shrug*


- Original Message -
From: "Stephen Benjamin" <step...@redhat.com>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Tuesday, January 10, 2017 6:13:27 PM
Subject: Re: [foreman-users] Web Components Stop Responding

- Original Message -
> From: "'Jason B. Nance' via Foreman users" <foreman-users@googlegroups.com>
> To: "Foreman Users" <foreman-users

Re: [foreman-users] "Promotion" task stuck in planning/pending

['Jason B. Nance' via Foreman users]

Figured it out:

# foreman-rake console
irb(main):001:0> ForemanTasks::Task.where(:id => 
'61c39eaa-0ad9-4c8f-be42-20c10db7caf3').destroy_all



- Original Message -
From: "Foreman Users" 
To: "Foreman Users" 
Sent: Monday, January 16, 2017 2:28:00 PM
Subject: [foreman-users] "Promotion" task stuck in planning/pending

On a 3.2.2/1.13.3 server I have a "Promotion" task that stuck in the "planning" 
state/"pending" result.  If I attempt to view the task in the web UI I get the 
following error:

plan_self has to be invoked before being able to reference the output

(full stack track is below)

Attempting to view this task in Dynflow results in a 500 error as well.

This stuck task appears to be preventing other promotions from happening as 
they never leave the planning state, either.

How can I go about cancelling or deleting this task?

Thanks,

j




2017-01-16 14:24:26 621ed894 [app] [W] Action failed
 | RuntimeError: plan_self has to be invoked before being able to reference the 
output
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.15/lib/dynflow/action.rb:140:in
 `output'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/_running_steps.html.erb:33:in
 `block in _11eaad6fe81d7f628f18504e45d82d2f'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/_running_steps.html.erb:7:in
 `each'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/_running_steps.html.erb:7:in
 `_11eaad6fe81d7f628f18504e45d82d2f'
 | 
/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/theforeman/tfm/root/usr/share/gems/gems/deface-1.0.2/lib/deface/action_view_extensions.rb:41:in
 `render'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/partial_renderer.rb:339:in
 `render_partial'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/partial_renderer.rb:310:in
 `block in render'
 | 
/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/partial_renderer.rb:309:in
 `render'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/renderer.rb:51:in
 `render_partial'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/renderer.rb:25:in
 `render'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/rendering_helper.rb:32:in
 `render'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/show.html.erb:103:in
 `block in _ff424f6f413334c3caa2ca7cd46f3724'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/capture_helper.rb:38:in
 `block in capture'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/capture_helper.rb:202:in
 `with_output_buffer'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/capture_helper.rb:38:in
 `capture'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/form_helper.rb:444:in
 `form_for'
 | /usr/share/foreman/app/helpers/form_helper.rb:278:in `form_for'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/show.html.erb:88:in
 `_ff424f6f413334c3caa2ca7cd46f3724'
 | 
/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'
 | 

[foreman-users] "Promotion" task stuck in planning/pending

['Jason B. Nance' via Foreman users]

On a 3.2.2/1.13.3 server I have a "Promotion" task that stuck in the "planning" 
state/"pending" result.  If I attempt to view the task in the web UI I get the 
following error:

plan_self has to be invoked before being able to reference the output

(full stack track is below)

Attempting to view this task in Dynflow results in a 500 error as well.

This stuck task appears to be preventing other promotions from happening as 
they never leave the planning state, either.

How can I go about cancelling or deleting this task?

Thanks,

j




2017-01-16 14:24:26 621ed894 [app] [W] Action failed
 | RuntimeError: plan_self has to be invoked before being able to reference the 
output
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.15/lib/dynflow/action.rb:140:in
 `output'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/_running_steps.html.erb:33:in
 `block in _11eaad6fe81d7f628f18504e45d82d2f'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/_running_steps.html.erb:7:in
 `each'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/_running_steps.html.erb:7:in
 `_11eaad6fe81d7f628f18504e45d82d2f'
 | 
/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/theforeman/tfm/root/usr/share/gems/gems/deface-1.0.2/lib/deface/action_view_extensions.rb:41:in
 `render'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/partial_renderer.rb:339:in
 `render_partial'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/partial_renderer.rb:310:in
 `block in render'
 | 
/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/partial_renderer.rb:309:in
 `render'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/renderer.rb:51:in
 `render_partial'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/renderer/renderer.rb:25:in
 `render'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/rendering_helper.rb:32:in
 `render'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/show.html.erb:103:in
 `block in _ff424f6f413334c3caa2ca7cd46f3724'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/capture_helper.rb:38:in
 `block in capture'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/capture_helper.rb:202:in
 `with_output_buffer'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/capture_helper.rb:38:in
 `capture'
 | 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/actionview-4.2.5.1/lib/action_view/helpers/form_helper.rb:444:in
 `form_for'
 | /usr/share/foreman/app/helpers/form_helper.rb:278:in `form_for'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.8.2/app/views/foreman_tasks/tasks/show.html.erb:88:in
 `_ff424f6f413334c3caa2ca7cd46f3724'
 | 
/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/theforeman/tfm/root/usr/share/gems/gems/deface-1.0.2/lib/deface/action_view_extensions.rb:41: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'
 | 

Re: [foreman-users] Web Components Stop Responding

['Jason B. Nance' via Foreman users]

tcp6  32  0 172.16.246.31:443   172.16.246.31:53428 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53470 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53494 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53530 CLOSE_WAIT
tcp6  32  0 172.16.246.31:443   172.16.246.31:53378 CLOSE_WAIT
tcp6   0  0 172.16.246.31:443   172.16.246.31:53508 ESTABLISHED
tcp6   0  0 172.16.246.31:443   172.16.246.31:53514 ESTABLISHED
tcp6  32  0 172.16.246.31:443   172.16.246.31:53218 CLOSE_WAIT
udp0  0 0.0.0.0:51680   0.0.0.0:*




- Original Message -
From: "Jason Nance" <ja...@tresgeek.net>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Thursday, January 12, 2017 2:22:51 PM
Subject: Re: [foreman-users] Web Components Stop Responding

Not sure what was going on.  I typically have fewer than 10 hosts connected to 
this lab install which was hanging.  I updated it to 3.2.2/1.13.3 on Monday and 
have debug logging on and haven't seen the issue reappear.

*shrug*


- Original Message -
From: "Stephen Benjamin" <step...@redhat.com>
To: "Foreman Users" <foreman-users@googlegroups.com>
Sent: Tuesday, January 10, 2017 6:13:27 PM
Subject: Re: [foreman-users] Web Components Stop Responding

----- Original Message -
> From: "'Jason B. Nance' via Foreman users" <foreman-users@googlegroups.com>
> To: "Foreman Users" <foreman-users@googlegroups.com>
> Sent: Friday, January 6, 2017 11:41:55 AM
> Subject: [foreman-users] Web Components Stop Responding
> 
> Hello Everyone,
> 
> On a Katello 3.2.1 / TFM 1.13.2 server (and noticed on previous versions as
> well) I run into the situation where occasionally the web interface and API
> stop responding.  Attempts to load any page, click on any
> button/link/whatever results in the browser just spinning and eventually
> timing out.  The only log message printed is:
> 
> ==> /var/log/httpd/foreman-ssl_error_ssl.log <==
> [Fri Jan 06 10:16:11.926220 2017] [ssl:warn] [pid 24448] [client
> 172.16.246.240:56536] AH02227: Failed to set r->user to
> 'SSL_CLIENT_S_DN_CN'
> 
> (I see this frequently under normal conditions)
> 
> The system is not under heavy loads during this freeze.  Load average is
> about 1.2 (on a 6 vCPU / 16G memory virtual server).  The only process doing
> noticeable work is mongodb.
> 
> Puppet runs on clients also fail during this time because /etc/puppet/node.rb
>  fails with:
> 
> Could not send facts to Foreman: Net::ReadTimeout
> 
> (no log messages are printed)
> 
> A 'yum install' on a client is able to download the package, but then hangs
> on "Uploading Package Profile" (and eventually times out and skips it).
>
> If I restart [tomcat and] httpd things start responding again.  I'm not sure
> if the tomcat restart matters, as I did it first and nothing changed but
> after I restarted httpd - which took much longer than normal - is when
> everything came back to life.  There were about 55 connections to httpd at
> the time, nearly all in CLOSE_WAIT.
> 
> Anyone have ideas as to what may be happening?

This sounds an awful lot like what we fixed in 
http://projects.theforeman.org/issues/14023.

Do you have a lot of puppet clients checking in? You could try to tweak the 
passenger
settings as described here in the Red Hat BZ (will be the default in Foreman 
1.14), and
see if that helps:

  https://bugzilla.redhat.com/show_bug.cgi?id=1163452#c11

- Stephen


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

Re: [foreman-users] Deploying firmware from Foreman smart proxy

['Jason B. Nance' via Foreman users]

Hi Graham, 

You should be able to use the "file" content type to serve this content. I 
believe in a recent release it was even made versionable. 

You can always dump unmanaged content in /var/www/html/pub, as well. 

Regards, 

j 



From: "Graham"  
To: "Foreman Users"  
Sent: Thursday, January 12, 2017 6:18:27 AM 
Subject: [foreman-users] Deploying firmware from Foreman smart proxy 

I have a need to download/run bash scripts and firmware files (not RPMs) on 
machines provisioned by Foreman/katello smart proxy. 

How can I best serve this content? 

I currently use a http server but would like to include this into a 
synchronised content view maintained on Foreman. 

I've checked the ISO repo facility but this can't be sycnronised to a capsule 
server for some reason. 

If no replication available, then can I serve custom http content from the 
smart proxy by manually copying and configuring /etc/httpd/conf/httpd.conf ? 



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 [ 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] Host Not Leaving "Build" Mode

['Jason B. Nance' via Foreman users]

Ehh, disregard this.  I upgraded to 3.2.2/1.13.3 and it went away.  Likely 
related:

http://projects.theforeman.org/issues/16475


- Original Message -
From: "Foreman Users" 
To: "Foreman Users" 
Sent: Tuesday, January 10, 2017 3:47:46 PM
Subject: [foreman-users] Host Not Leaving "Build" Mode

Hello,

My hosts have recently stopped exiting from build mode after being provisioned. 
 I see the following in my provisioning template:

<% if @provisioning_type == nil || @provisioning_type == 'host' -%>
# Inform the build system that we are done.
echo "Informing Foreman that we are built"
wget -q -O /dev/null --no-check-certificate <%= foreman_url %>
<% end -%>
) 2>&1 | tee /root/install.post.log
exit 0

And on a newly provisioned host the last line of /root/install.post.log is:

Informing Foreman that we are built

But the host's build status is still "Pending installation".

In production.log I see:

2017-01-10 14:03:05 17cd [app] [I] Started GET 
"/unattended/built?token=4eb1bd5b-b6d1-4d1b-ba97-fc970546fe23" for 
172.16.246.110 at 2017-01-10 14:03:05 -0600
2017-01-10 14:03:05 17cd [app] [I] Processing by 
UnattendedController#built as TEXT
2017-01-10 14:03:05 17cd [app] [I]   Parameters: 
{"token"=>"4eb1bd5b-b6d1-4d1b-ba97-fc970546fe23"}
2017-01-10 14:03:05 17cd [app] [D] Found sl2aosplpxy0001.ipa.centric.lab
2017-01-10 14:03:05 17cd [app] [D] Setting current user thread-local 
variable to foreman_api_admin
2017-01-10 14:03:05 17cd [app] [I] unattended: 
sl2aosplpxy0001.ipa.centric.lab is Built!
2017-01-10 14:03:05 17cd [templates] [I] Rendering template 'PXEGrub2 
default local boot'
2017-01-10 14:03:05 17cd [templates] [I] Rendering template 
'pxegrub2_chainload'
2017-01-10 14:03:05 17cd [app] [W] Deploy TFTP PXEGrub2 config for 
sl2aosplpxy0001.ipa.centric.lab task failed with the following error: 
ERF12-5472 [ProxyAPI::ProxyException]: Unable to set TFTP boot entry for 
00:50:56:91:71:66 ([RestClient::BadRequest]: 400 Bad Request) for proxy 
https://katello.ipa.centric.lab:9090/tftp
 | ProxyAPI::ProxyException: ERF12-5472 [ProxyAPI::ProxyException]: Unable 
to set TFTP boot entry for 00:50:56:91:71:66 ([RestClient::BadRequest]: 400 Bad 
Request) for proxy https://katello.ipa.centric.lab:9090/tftp
 | /usr/share/foreman/lib/proxy_api/tftp.rb:17:in `rescue in set'
 | /usr/share/foreman/lib/proxy_api/tftp.rb:15:in `set'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:102:in 
`block in setTFTP'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:204:in 
`block in each_unique_feasible_tftp_proxy'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:203:in `map'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:203:in 
`each_unique_feasible_tftp_proxy'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:101:in 
`setTFTP'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:194:in `execute'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:135:in `block in 
process'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:127:in `each'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:127:in `process'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:35:in 
`around_save_orchestration'


Any ideas?

Thanks,

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.

Re: [foreman-users] Web Components Stop Responding

['Jason B. Nance' via Foreman users]

I have debugging on now and am just waiting for it to happen again. 

Will report back then. 

j 




From: "Tomer Brisker" <tbris...@redhat.com> 
To: "Foreman Users" <foreman-users@googlegroups.com> 
Sent: Saturday, January 7, 2017 7:13:05 AM 
Subject: Re: [foreman-users] Web Components Stop Responding 

Hi Jason, 
Could you please turn on debug logging on foreman ( [ 
https://theforeman.org/manuals/1.13/index.html#7.2Debugging | 
https://theforeman.org/manuals/1.13/index.html#7.2Debugging ] ) and attach the 
output in production.log during the host provisioning? That might give us a 
clue as to what is failing. 

On Fri, Jan 6, 2017 at 11:15 PM, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 


A bit more information - the tomcat restart makes no difference (the httpd 
restart is what fixes the issue). And, this is happening every time I provision 
a host. O.O 

j 



- Original Message - 
From: "Foreman Users" < [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] > 
To: "Foreman Users" < [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] > 
Sent: Friday, January 6, 2017 10:41:55 AM 
Subject: [foreman-users] Web Components Stop Responding 

Hello Everyone, 

On a Katello 3.2.1 / TFM 1.13.2 server (and noticed on previous versions as 
well) I run into the situation where occasionally the web interface and API 
stop responding. Attempts to load any page, click on any button/link/whatever 
results in the browser just spinning and eventually timing out. The only log 
message printed is: 

==> /var/log/httpd/foreman-ssl_error_ssl.log <== 
[Fri Jan 06 10:16:11.926220 2017] [ssl:warn] [pid 24448] [client [ 
http://172.16.246.240:56536/ | 172.16.246.240:56536 ] ] AH02227: Failed to set 
r->user to 'SSL_CLIENT_S_DN_CN' 

(I see this frequently under normal conditions) 

The system is not under heavy loads during this freeze. Load average is about 
1.2 (on a 6 vCPU / 16G memory virtual server). The only process doing 
noticeable work is mongodb. 

Puppet runs on clients also fail during this time because /etc/puppet/node.rb 
 fails with: 

Could not send facts to Foreman: Net::ReadTimeout 

(no log messages are printed) 

A 'yum install' on a client is able to download the package, but then hangs on 
"Uploading Package Profile" (and eventually times out and skips it). 

If I restart [tomcat and] httpd things start responding again. I'm not sure if 
the tomcat restart matters, as I did it first and nothing changed but after I 
restarted httpd - which took much longer than normal - is when everything came 
back to life. There were about 55 connections to httpd at the time, nearly all 
in CLOSE_WAIT. 

Anyone have ideas as to what may be happening? 

Thanks, 

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 [ mailto:foreman-users%2bunsubscr...@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 [ mailto:foreman-users%2bunsubscr...@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 ] . 






-- 
Have a nice day, 
Tomer Brisker 
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 Gro

[foreman-users] Host Not Leaving "Build" Mode

['Jason B. Nance' via Foreman users]

Hello,

My hosts have recently stopped exiting from build mode after being provisioned. 
 I see the following in my provisioning template:

<% if @provisioning_type == nil || @provisioning_type == 'host' -%>
# Inform the build system that we are done.
echo "Informing Foreman that we are built"
wget -q -O /dev/null --no-check-certificate <%= foreman_url %>
<% end -%>
) 2>&1 | tee /root/install.post.log
exit 0

And on a newly provisioned host the last line of /root/install.post.log is:

Informing Foreman that we are built

But the host's build status is still "Pending installation".

In production.log I see:

2017-01-10 14:03:05 17cd [app] [I] Started GET 
"/unattended/built?token=4eb1bd5b-b6d1-4d1b-ba97-fc970546fe23" for 
172.16.246.110 at 2017-01-10 14:03:05 -0600
2017-01-10 14:03:05 17cd [app] [I] Processing by 
UnattendedController#built as TEXT
2017-01-10 14:03:05 17cd [app] [I]   Parameters: 
{"token"=>"4eb1bd5b-b6d1-4d1b-ba97-fc970546fe23"}
2017-01-10 14:03:05 17cd [app] [D] Found sl2aosplpxy0001.ipa.centric.lab
2017-01-10 14:03:05 17cd [app] [D] Setting current user thread-local 
variable to foreman_api_admin
2017-01-10 14:03:05 17cd [app] [I] unattended: 
sl2aosplpxy0001.ipa.centric.lab is Built!
2017-01-10 14:03:05 17cd [templates] [I] Rendering template 'PXEGrub2 
default local boot'
2017-01-10 14:03:05 17cd [templates] [I] Rendering template 
'pxegrub2_chainload'
2017-01-10 14:03:05 17cd [app] [W] Deploy TFTP PXEGrub2 config for 
sl2aosplpxy0001.ipa.centric.lab task failed with the following error: 
ERF12-5472 [ProxyAPI::ProxyException]: Unable to set TFTP boot entry for 
00:50:56:91:71:66 ([RestClient::BadRequest]: 400 Bad Request) for proxy 
https://katello.ipa.centric.lab:9090/tftp
 | ProxyAPI::ProxyException: ERF12-5472 [ProxyAPI::ProxyException]: Unable 
to set TFTP boot entry for 00:50:56:91:71:66 ([RestClient::BadRequest]: 400 Bad 
Request) for proxy https://katello.ipa.centric.lab:9090/tftp
 | /usr/share/foreman/lib/proxy_api/tftp.rb:17:in `rescue in set'
 | /usr/share/foreman/lib/proxy_api/tftp.rb:15:in `set'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:102:in 
`block in setTFTP'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:204:in 
`block in each_unique_feasible_tftp_proxy'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:203:in `map'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:203:in 
`each_unique_feasible_tftp_proxy'
 | /usr/share/foreman/app/models/concerns/orchestration/tftp.rb:101:in 
`setTFTP'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:194:in `execute'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:135:in `block in 
process'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:127:in `each'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:127:in `process'
 | /usr/share/foreman/app/models/concerns/orchestration.rb:35:in 
`around_save_orchestration'


Any ideas?

Thanks,

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.

Re: [foreman-users] GUI Problem with Foreman

['Jason B. Nance' via Foreman users]

> You might also need something in the %post section to ensure the 
> graphical.target is reached by systemd (I've not installed RHEL7/CentOS 
> desktop systems from Satellite, so not sure about this part) 

You should be able to just remove the "skipx" option in the kickstart 
[template] (and install a desktop environment).  If you install a desktop and 
don't have skipx the default boot target will be graphical.

https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html

(search for "skipx")

-- 
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] Web Components Stop Responding

['Jason B. Nance' via Foreman users]

Hello Everyone,

On a Katello 3.2.1 / TFM 1.13.2 server (and noticed on previous versions as 
well) I run into the situation where occasionally the web interface and API 
stop responding.  Attempts to load any page, click on any button/link/whatever 
results in the browser just spinning and eventually timing out.  The only log 
message printed is:

==> /var/log/httpd/foreman-ssl_error_ssl.log <==
[Fri Jan 06 10:16:11.926220 2017] [ssl:warn] [pid 24448] [client 
172.16.246.240:56536] AH02227: Failed to set r->user to 'SSL_CLIENT_S_DN_CN'

(I see this frequently under normal conditions)

The system is not under heavy loads during this freeze.  Load average is about 
1.2 (on a 6 vCPU / 16G memory virtual server).  The only process doing 
noticeable work is mongodb.

Puppet runs on clients also fail during this time because /etc/puppet/node.rb 
 fails with:

Could not send facts to Foreman: Net::ReadTimeout

(no log messages are printed)

A 'yum install' on a client is able to download the package, but then hangs on 
"Uploading Package Profile" (and eventually times out and skips it).

If I restart [tomcat and] httpd things start responding again.  I'm not sure if 
the tomcat restart matters, as I did it first and nothing changed but after I 
restarted httpd - which took much longer than normal - is when everything came 
back to life.  There were about 55 connections to httpd at the time, nearly all 
in CLOSE_WAIT.

Anyone have ideas as to what may be happening?

Thanks,

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.

Re: [foreman-users] Package does not match intended download

['Jason B. Nance' via Foreman users]

This turned out to be an issue in the Squid cache.  For some reason the mime 
type on the request was text/plain, for example:

1483463085.583  1 127.0.0.1 TCP_MEM_HIT/200 232660 GET http://127.0.0.1:3128
/var/lib/pulp/content/units/rpm/3b/965cfedb57c5a3cde020b31992b34cd17acbec807dc6543845ecd899eb9680/systemd-219-30.el7_3.6.x86_64.rpm
 - HIER_NONE/- text/plain

After shutting down Squid, deleting the cache, and starting Squid back up that 
same request changed to:

1483465857.848534 127.0.0.1 TCP_MISS/200 5482957 GET 
http://127.0.0.1:3128/var/lib/pulp/content/units/rpm/3b/965cfedb57c5a3cde020b31992b34cd17acbec807dc6543845ecd899eb9680/systemd-219-30.el7_3.6.x86_64.rpm
 - FIRSTUP_PARENT/127.0.0.1 application/x-rpm

(note the change to application/x-rpm)

Big thanks to Justin Sherrill for helping me through this one.

j



- Original Message -
From: "'Jason B. Nance' via Foreman users" <foreman-users@googlegroups.com>
To: foreman-users@googlegroups.com
Sent: Tuesday, January 3, 2017 8:51:03 AM
Subject: [foreman-users] Package does not match intended download

Hello everyone,

I have an install of Katello 3.2.2/1.13.3 with the CentOS 7 repositories synced 
and content views created that contain the packages and a client host 
registered and pointed at the CV.  Yum is reporting the following error when 
attempting to install/update several packages:

[Errno -1] Package does not match intended download.

I have ran "yum clean all" and removed /var/cache/yum/x86_64.  I've also 
re-synced the repos (with force post sync enabled) and generated new versions 
of the CVs with no change.

Does anyone have any suggestions for how to troubleshoot or resolve this?

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.

Re: [foreman-users] foreman_subnets with Puppet 4

['Jason B. Nance' via Foreman users]

I ended up using each() to solve this issue, but if someone has a better idea 
I'm all ears.

j


- Original Message -
From: "'Jason B. Nance' via Foreman users" <foreman-users@googlegroups.com>
To: foreman-users@googlegroups.com
Sent: Thursday, December 29, 2016 4:32:12 PM
Subject: [foreman-users] foreman_subnets with Puppet 4

Hello everyone,

I have a custom firewall module that defines a resource which creates rules 
based on values in foreman_subnets.  So in my module I say:

firewall::foreman_subnet { $::foreman_subnets: }

...and it creates rules for each of the subnets in the array of hashes.

This worked great in Puppet 3, but Puppet 4 rejects this $title with:

Illegal title type at index 0.  Expected String, got Has[String, String] 
at...

Does anyone have any recommendations for converting/handling this data in a way 
that makes Puppet 4 happy?  I can certainly update the resource to accept 
parameters or whatever.  I'm not just sure how to handle the "iteration" 
(creating an instance for each network, where the number of networks is not 
fixed).

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.

Re: [foreman-users] How to access puppet resources?

['Jason B. Nance' via Foreman users]

Hi Julia, 

I'm sorry, I made too many assumptions about your setup. I don't know how to 
get the data you're looking for in this case. 

Regards, 

j 



From: "jul1a berger"  
To: "Foreman users"  
Cc: "Jason Nance"  
Sent: Tuesday, December 20, 2016 1:10:14 PM 
Subject: Re: [foreman-users] How to access puppet resources? 

Hi Jason, 
thank you for your quick response. 




In the web UI this information is available at: 

Hosts -> Content Hosts ->  -> "Packages" tab 




But aren't Content Hosts only available if the Katello plugin is installed and 
if the "Subscription Manager" is installed on the client? Is there no 
possibility to get this information without an additional installation (except 
of the puppet client) on the host which should be monitored? And if not, how 
can I handle Windows Clients? As far as I know, the Katello Client is not 
available for Windows Systems or did I miss something? 

Thank you! 

Julia 

-- 
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.1 to 3.2.1 upgrade

['Jason B. Nance' via Foreman users]

6.100 - 2c90769f58b1f1fd0158c19f1e88010d [20/Dec/2016:09:16:00 -0600] 
"GET 
/streamer/var/lib/pulp/content/units/rpm/b6/c339b4992d674e001ad5508802a2fbc3d7cb46af992c8366f6f9251227d3b4/NetworkManager-1.4.0-13.el7_3.x86_64.rpm?policy=eyJleHRlbnNpb25zIjogeyJyZW1vdGVfaXAiOiAiMTcyLjE2LjI0Ni4xMDAifSwgInJlc291cmNlIjogIi9zdHJlYW1lci92YXIvbGliL3B1bHAvY29udGVudC91bml0cy9ycG0vYjYvYzMzOWI0OTkyZDY3NGUwMDFhZDU1MDg4MDJhMmZiYzNkN2NiNDZhZjk5MmM4MzY2ZjZmOTI1MTIyN2QzYjQvTmV0d29ya01hbmFnZXItMS40LjAtMTMuZWw3XzMueDg2XzY0LnJwbSIsICJleHBpcmF0aW9uIjogMTQ4MjI0NzA1MH0%3D;signature=CehLSHyVEGDJu-6r0SMoHEKJxksW0BqZqdnSDHfqzQom33_-apNDJhn2X965O1wJjk0okw8gv-ITUSM3CoLHrgt2Cg6LRAC5kZ1tSwiNurFJFLjIa2SVtiiUXt13XxBFN_AACAd8i_0uVs29AeMuLiKWkdFAzGcWqWmQS1ixQ4uACGHfy7-DHdbbrupBhWDCzPyURu6wChpDSqhcymRMWsb1JNLIgBo1_qu479zby1hr9Sv2LOpN37sdm4WOq_vkWfu6Tkq7IyDTnxF5hMOn8DiEg1UvfEMOCzDqFQYjGvc1LIJvPaWR1ZBnLz2pT5pTHNPUyIZud0gjpzrRikKytg%3D%3D
 HTTP/1.1" 404 - "-" "urlgrabber/3.10 yum/3.4.3" 

...from /var/log/squid/access.log: 

1482246959.418 223 127.0.0.1 TCP_MISS/404 385 GET 
http://127.0.0.1:3128/var/lib/pulp/content/units/drpm/b3/0d7170a4d95e8aa576223089b92f08182f7ccb1dd769096aab49b0091fa051/drpms/expat-2.1.0-8.el7_2.1.0-10.el7_3.x86_64.drpm
 - FIRSTUP_PARENT/127.0.0.1 text/html 
1482246961.086 92 127.0.0.1 TCP_MISS/404 385 GET 
http://127.0.0.1:3128/var/lib/pulp/content/units/rpm/b6/c339b4992d674e001ad5508802a2fbc3d7cb46af992c8366f6f9251227d3b4/NetworkManager-1.4.0-13.el7_3.x86_64.rpm
 - FIRSTUP_PARENT/127.0.0.1 text/html 

...from /var/log/squid/store.log: 

1482246959.418 RELEASE -1  50995C9E832B61A47EC237BB0AEBD4E7 ? ? ? ? ?/? 
?/? ? ? 
1482246961.086 RELEASE -1  F26384D752D959E8933E933A500182FB ? ? ? ? ?/? 
?/? ? ? 


>From the Katello host I'm able to "wget" the packages from mirror.centos.org. 






From: "Peter Kirby" <peter.ki...@objectstream.com> 
To: foreman-users@googlegroups.com 
Sent: Tuesday, December 20, 2016 8:59:52 AM 
Subject: Re: [foreman-users] Re: Katello 3.1 to 3.2.1 upgrade 


On Tue, Dec 20, 2016 at 8:55 AM, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 



Pascalp, 

Were you using the Puppet 3 or Puppet 4 repo on your server? 

Thanks, 

j 





Jason, 

FWIW - I got this error with Puppet 3 and also again with Puppet 4 repos. When 
I have time I'll try the solution posted by Pascalp and report back on the 
results. 

Thanks, 
Peter 






BQ_BEGIN


From: "pascalp" < [ mailto:supremerulerx...@gmail.com | 
supremerulerx...@gmail.com ] > 
To: "Foreman users" < [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] > 
Sent: Tuesday, December 20, 2016 8:50:45 AM 
Subject: [foreman-users] Re: Katello 3.1 to 3.2.1 upgrade 

I found a solution that worked for me (3.2.0 to 3.2.1). Steps are listed in 
your issue at [ http://projects.theforeman.org/issues/17722 | 
http://projects.theforeman.org/issues/17722 ] Hope it works for you. 

On Sunday, December 18, 2016 at 12:15:14 PM UTC+1, Martin Õunap wrote: 
BQ_BEGIN

Hi 
When I was running upgrade I had an error: 

[ http://projects.theforeman.org/issues/17703 | 
http://projects.theforeman.org/issues/17703 ] 

So I did as it is mentioned in thiissue: 

":run_always => true" seems to be a remnant of the previous 30-upgrade.rb where 
every upgrade_step had a ":run_always" or ":long_running" option passed. With 
the 3.2.1 30-upgrade.rb ":migrate_candlepin" is the only upgrade_step with an 
option and since the function only takes one argument this results in the error 
seen. 



Deleting ", :run_always => true" lets the upgrade continue. 


But after that I have an error: 

[ INFO 2016-12-17 15:22:32 main] Upgrade Step: db_seed... 
[ERROR 2016-12-17 15:22:47 main] rake aborted! 
RestClient::ResourceNotFound: 404 Resource Not Found 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/abstract_response.rb:74:in
 `return!' 
/opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.9.0/lib/runcible/base.rb:79:in
 `block in get_response' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in
 `call' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in
 `process_result' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:421:in
 `block in transmit' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in
 `transmit' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:176:in
 `execute' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in
 `execute' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/resource.rb:51:in
 `get' 
/opt/theforeman/tfm/root/usr/share/gems/gems/ru

Re: [foreman-users] Re: Katello 3.1 to 3.2.1 upgrade

['Jason B. Nance' via Foreman users]

Pascalp, 

Were you using the Puppet 3 or Puppet 4 repo on your server? 

Thanks, 

j 



From: "pascalp"  
To: "Foreman users"  
Sent: Tuesday, December 20, 2016 8:50:45 AM 
Subject: [foreman-users] Re: Katello 3.1 to 3.2.1 upgrade 

I found a solution that worked for me (3.2.0 to 3.2.1). Steps are listed in 
your issue at [ http://projects.theforeman.org/issues/17722 | 
http://projects.theforeman.org/issues/17722 ] Hope it works for you. 

On Sunday, December 18, 2016 at 12:15:14 PM UTC+1, Martin Õunap wrote: 


Hi 
When I was running upgrade I had an error: 

[ http://projects.theforeman.org/issues/17703 | 
http://projects.theforeman.org/issues/17703 ] 

So I did as it is mentioned in thiissue: 

":run_always => true" seems to be a remnant of the previous 30-upgrade.rb where 
every upgrade_step had a ":run_always" or ":long_running" option passed. With 
the 3.2.1 30-upgrade.rb ":migrate_candlepin" is the only upgrade_step with an 
option and since the function only takes one argument this results in the error 
seen. 



Deleting ", :run_always => true" lets the upgrade continue. 


But after that I have an error: 

[ INFO 2016-12-17 15:22:32 main] Upgrade Step: db_seed... 
[ERROR 2016-12-17 15:22:47 main] rake aborted! 
RestClient::ResourceNotFound: 404 Resource Not Found 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/abstract_response.rb:74:in
 `return!' 
/opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.9.0/lib/runcible/base.rb:79:in
 `block in get_response' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in
 `call' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:493:in
 `process_result' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:421:in
 `block in transmit' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in
 `transmit' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:176:in
 `execute' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in
 `execute' 
/opt/theforeman/tfm/root/usr/share/gems/gems/rest-client-1.8.0/lib/restclient/resource.rb:51:in
 `get' 
/opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.9.0/lib/runcible/base.rb:78:in
 `get_response' 
/opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.9.0/lib/runcible/base.rb:66:in
 `call' 
/opt/theforeman/tfm/root/usr/share/gems/gems/runcible-1.9.0/lib/runcible/resources/event_notifier.rb:48:in
 `list' 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.2.1.1/app/models/katello/glue/pulp/repo.rb:32:in
 `ensure_sync_notification' 
/opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.2.1.1/db/seeds.d/108-ensure_sync_notification.rb:9:in
 `' 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:268:in
 `load' 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:268:in
 `block in load' 
/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:268:in
 `load' 
/usr/share/foreman/db/seeds.rb:81:in `block in ' 
/usr/share/foreman/db/seeds.rb:79:in `each' 
/usr/share/foreman/db/seeds.rb:79:in `' 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:268:in
 `load' 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activesupport-4.2.5.1/lib/active_support/dependencies.rb:268:in
 `block in load' 
/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:268:in
 `load' 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/railties-4.2.5.1/lib/rails/engine.rb:547:in
 `load_seed' 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/tasks/database_tasks.rb:250:in
 `load_seed' 
/opt/rh/sclo-ror42/root/usr/share/gems/gems/activerecord-4.2.5.1/lib/active_record/railties/databases.rake:183:in
 `block (2 levels) in ' 
Tasks: TOP => db:seed 
(See full trace by running task with --trace) 
Seeding /usr/share/foreman/db/seeds.d/03-auth_sources.rb 
Seeding /usr/share/foreman/db/seeds.d/03-permissions.rb 
Seeding /usr/share/foreman/db/seeds.d/03-roles.rb 
Seeding /usr/share/foreman/db/seeds.d/04-admin.rb 
Seeding /usr/share/foreman/db/seeds.d/05-taxonomies.rb 
Seeding /usr/share/foreman/db/seeds.d/06-architectures.rb 
Seeding /usr/share/foreman/db/seeds.d/07-provisioning_templates.rb 
Seeding /usr/share/foreman/db/seeds.d/08-partition_tables.rb 
Seeding /usr/share/foreman/db/seeds.d/10-installation_media.rb 

Re: [foreman-users] Custom Partition Table

['Jason B. Nance' via Foreman users]

Give one of these methods a try: 

https://stackoverflow.com/questions/2113235/ruby-is-a-string-in-a-list-of-values
 


From: "'Denis Müller' via Foreman users"  
To: "Foreman users"  
Sent: Monday, December 19, 2016 9:35:07 AM 
Subject: [foreman-users] Custom Partition Table 

Hi guys, 
we would woulk like to do this: 

<% if @host.facts['Productname'] == '' ProLiant DL360 G7" -%> < How can we 
provide multiply strings like G7,G8,G9? 
part / --size=1 --grow --fstype ext4 --ondisk=sda 
part swap --size=8192 --ondisk=sda 
part /var/lib/mysql --size=1 --grow --asprimary --ondisk=sdb 
<% 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 ] . 

-- 
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] Content syncing in Katello 3.2.1 appears to be broken out of the box

['Jason B. Nance' via Foreman users]

Some additional info here... Not sure if this makes it better or worse... 

I did another fresh install but this time used the Puppet 4 repo instead of 
Puppet 3 and I'm not having the content problems. :-\ 

j 



From: "Peter Kirby" <peter.ki...@objectstream.com> 
To: foreman-users@googlegroups.com 
Sent: Friday, December 16, 2016 3:26:03 PM 
Subject: Re: [foreman-users] Content syncing in Katello 3.2.1 appears to be 
broken out of the box 

I am also getting a 500 error going to the Content -> Sync Status page. I only 
just upgraded this morning and I haven't had a chance to investigate further. 


On Fri, Dec 16, 2016 at 3:05 PM, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 


Team, 

I upgraded my Katello box from 3.1 to 3.2, and then to 3.2.1 and all hell broke 
loose in terms of syncing packages, which led me to file this bug: 

[ http://projects.theforeman.org/issues/17715 | 
http://projects.theforeman.org/issues/17715 ] 

...because I'm using on demand for everything and I assumed that was related as 
I initially discovered the issue trying to update subscribed hosts. 

But then I did a fresh install of 3.2.1 and am getting 500 errors clicking on 
Content -> Sync Status just like my upgraded host (and this is before doing any 
customization - no products, CVs, etc). 

Is anyone else having any issues? I feel like I'm going crazy or something... 

production.log says: 

2016-12-16 14:54:30 5c1b2060 [app] [I] Started GET "/katello/sync_management" 
for 192.168.16.133 at 2016-12-16 14:54:30 -0600 
2016-12-16 14:54:31 5c1b2060 [app] [I] Processing by 
Katello::SyncManagementController#index as HTML 
2016-12-16 14:54:31 74681c86 [app] [I] Started POST 
"/pulp/api/v2/repositories/search/" for 192.168.16.212 at 2016-12-16 14:54:31 
-0600 
2016-12-16 14:54:31 74681c86 [app] [F] 
| ActionController::RoutingError (No route matches [POST] 
"/pulp/api/v2/repositories/search"): 
| lib/middleware/tagged_logging.rb:18:in `call' 
| 
| 
2016-12-16 14:54:31 5c1b2060 [katello/pulp_rest] [I] RestClient.post " [ 
https://satellite.tresgeek.org/pulp/api/v2/repositories/search/ | 
https://satellite.tresgeek.org/pulp/api/v2/repositories/search/ ] ", 
"{\"criteria\":{\"filters\":{\"id\":{\"$in\":[]", "Accept"=>"*/*; q=0.5, 
application/xml", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"42", 
"accept"=>"application/json", "content_type"=>"application/json" 
| \n# => 404 NotFound | application/json 36 bytes 
| 
2016-12-16 14:54:31 5c1b2060 [app] [I] Completed 500 Internal Server Error in 
129ms (ActiveRecord: 7.6ms) 
2016-12-16 14:54:31 5c1b2060 [app] [F] 
| RestClient::ResourceNotFound (404 Resource Not Found): 
| katello (3.2.1.1) app/models/katello/glue/pulp/repos.rb:53:in `prepopulate!' 
| katello (3.2.1.1) app/helpers/katello/sync_management_helper.rb:38:in 
`collect_repos' 
| katello (3.2.1.1) app/controllers/katello/sync_management_controller.rb:27:in 
`index' 
| app/controllers/concerns/application_shared.rb:14:in `set_timezone' 
| lib/middleware/catch_json_parse_errors.rb:9:in `call' 
| lib/middleware/tagged_logging.rb:18:in `call' 
| 
| 
2016-12-16 14:54:31 5c1b2060 [app] [I] Started GET "/favicon.ico" for 
192.168.16.133 at 2016-12-16 14:54:31 -0600 
2016-12-16 14:54:31 5c1b2060 [app] [F] 
| ActionController::RoutingError (No route matches [GET] "/favicon.ico"): 
| lib/middleware/tagged_logging.rb:18:in `call' 
| 
| 

Here's my foreman-installer line: 

foreman-installer \ 
--scenario katello \ 
--enable-foreman-plugin-bootdisk \ 
--enable-foreman-plugin-discovery \ 
--enable-foreman-plugin-hooks \ 
--enable-foreman-plugin-openscap \ 
--enable-foreman-plugin-remote-execution \ 
--enable-foreman-plugin-templates \ 
--enable-foreman-proxy-plugin-openscap \ 
--enable-foreman-proxy-plugin-remote-execution-ssh \ 
--certs-city 'My City' \ 
--certs-org 'My Org' \ 
--certs-org-unit Katello \ 
--certs-state Mystate \ 
--foreman-admin-email [ mailto:ad...@email.com | ad...@email.com ] \ 
--foreman-admin-password foobar \ 
--foreman-configure-epel-repo false \ 
--foreman-configure-scl-repo false \ 
--foreman-email-delivery-method sendmail \ 
--foreman-initial-location Lab \ 
--foreman-initial-organization 'My Org' \ 
--foreman-ipa-authentication true \ 
--foreman-puppetrun true \ 
--foreman-plugin-discovery-install-images true \ 
--foreman-proxy-manage-puppet-group true \ 
--foreman-proxy-manage-sudoersd true \ 
--foreman-proxy-puppetrun-provider ssh \ 
--foreman-proxy-realm true \ 
--foreman-proxy-realm-principal [ mailto:realm-pr...@domain.org | 
realm-pr...@domain.org ] \ 
--foreman-proxy-templates true \ 
--foreman-proxy-tftp true \ 
--foreman-proxy-plugin-openscap-configure-op

[foreman-users] Content syncing in Katello 3.2.1 appears to be broken out of the box

['Jason B. Nance' via Foreman users]

Team,

I upgraded my Katello box from 3.1 to 3.2, and then to 3.2.1 and all hell broke 
loose in terms of syncing packages, which led me to file this bug:

http://projects.theforeman.org/issues/17715

...because I'm using on demand for everything and I assumed that was related as 
I initially discovered the issue trying to update subscribed hosts.

But then I did a fresh install of 3.2.1 and am getting 500 errors clicking on 
Content -> Sync Status just like my upgraded host (and this is before doing any 
customization - no products, CVs, etc).

Is anyone else having any issues?  I feel like I'm going crazy or something...

production.log says:

2016-12-16 14:54:30 5c1b2060 [app] [I] Started GET "/katello/sync_management" 
for 192.168.16.133 at 2016-12-16 14:54:30 -0600
2016-12-16 14:54:31 5c1b2060 [app] [I] Processing by 
Katello::SyncManagementController#index as HTML
2016-12-16 14:54:31 74681c86 [app] [I] Started POST 
"/pulp/api/v2/repositories/search/" for 192.168.16.212 at 2016-12-16 14:54:31 
-0600
2016-12-16 14:54:31 74681c86 [app] [F]
 | ActionController::RoutingError (No route matches [POST] 
"/pulp/api/v2/repositories/search"):
 |   lib/middleware/tagged_logging.rb:18:in `call'
 |
 |
2016-12-16 14:54:31 5c1b2060 [katello/pulp_rest] [I] RestClient.post 
"https://satellite.tresgeek.org/pulp/api/v2/repositories/search/;, 
"{\"criteria\":{\"filters\":{\"id\":{\"$in\":[]", "Accept"=>"*/*; q=0.5, 
application/xml", "Accept-Encoding"=>"gzip, deflate", "Content-Length"=>"42", 
"accept"=>"application/json", "content_type"=>"application/json"
 | \n# => 404 NotFound | application/json 36 bytes
 |
2016-12-16 14:54:31 5c1b2060 [app] [I] Completed 500 Internal Server Error in 
129ms (ActiveRecord: 7.6ms)
2016-12-16 14:54:31 5c1b2060 [app] [F]
 | RestClient::ResourceNotFound (404 Resource Not Found):
 |   katello (3.2.1.1) app/models/katello/glue/pulp/repos.rb:53:in 
`prepopulate!'
 |   katello (3.2.1.1) app/helpers/katello/sync_management_helper.rb:38:in 
`collect_repos'
 |   katello (3.2.1.1) 
app/controllers/katello/sync_management_controller.rb:27:in `index'
 |   app/controllers/concerns/application_shared.rb:14:in `set_timezone'
 |   lib/middleware/catch_json_parse_errors.rb:9:in `call'
 |   lib/middleware/tagged_logging.rb:18:in `call'
 |
 |
2016-12-16 14:54:31 5c1b2060 [app] [I] Started GET "/favicon.ico" for 
192.168.16.133 at 2016-12-16 14:54:31 -0600
2016-12-16 14:54:31 5c1b2060 [app] [F]
 | ActionController::RoutingError (No route matches [GET] "/favicon.ico"):
 |   lib/middleware/tagged_logging.rb:18:in `call'
 |
 |

Here's my foreman-installer line:

foreman-installer \
  --scenario katello \
  --enable-foreman-plugin-bootdisk \
  --enable-foreman-plugin-discovery \
  --enable-foreman-plugin-hooks \
  --enable-foreman-plugin-openscap \
  --enable-foreman-plugin-remote-execution \
  --enable-foreman-plugin-templates \
  --enable-foreman-proxy-plugin-openscap \
  --enable-foreman-proxy-plugin-remote-execution-ssh \
  --certs-city 'My City' \
  --certs-org 'My Org' \
  --certs-org-unit Katello \
  --certs-state Mystate \
  --foreman-admin-email ad...@email.com \
  --foreman-admin-password foobar \
  --foreman-configure-epel-repo false \
  --foreman-configure-scl-repo false \
  --foreman-email-delivery-method sendmail \
  --foreman-initial-location Lab \
  --foreman-initial-organization 'My Org' \
  --foreman-ipa-authentication true \
  --foreman-puppetrun true \
  --foreman-plugin-discovery-install-images true \
  --foreman-proxy-manage-puppet-group true \
  --foreman-proxy-manage-sudoersd true \
  --foreman-proxy-puppetrun-provider ssh \
  --foreman-proxy-realm true \
  --foreman-proxy-realm-principal realm-pr...@domain.org \
  --foreman-proxy-templates true \
  --foreman-proxy-tftp true \
  --foreman-proxy-plugin-openscap-configure-openscap-repo \

-- 
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] This thing itches me....

['Jason B. Nance' via Foreman users]

Shlomi, 

Now that this information has been collected what are the plans of use for it? 
Will RFEs be opened or something similar? 

Regards, 

j 



From: "Lachlan Musicman" <data...@gmail.com> 
To: foreman-users@googlegroups.com 
Sent: Wednesday, December 7, 2016 4:30:09 PM 
Subject: Re: [foreman-users] This thing itches me 

Ability to add a new Lifecycle stage to the middle of a Lifecycle Path. 
eg: 
Old 
Library -> Dev -> Prod 

New 
Library -> Dev -> UAT -> Prod 

cheers 
L. 

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

- Grace Hopper 

On 8 December 2016 at 01:51, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 



- Add ability to add config groups and parameters at the Host Collection level 
- Add ability to merge parameters that come from org/location/OS/host 
collection/host/etc,etc (like you can do with Class Parameters) 
- Performance improvements related to creating and promoting [Composite] 
Content View versions 
- Ability to go back to "normal" Foreman interface from the Dynflow console, or 
better integration (so that you can deal with failed tasks easier) 
- More consistency regarding version numbers (sometimes it is a string, 
sometimes it is an integer, why is the ".0" on there when that's never used, 
sorting in dropdown boxes like CV versions in Composite views, etc) 
- Add a parameter consumable by templates and Puppet for the FQDN of the 
capsule the host uses (similar to the puppetmaster parameter) 




From: "Shlomi Zadok" < [ mailto:shl...@ben-hanna.com | shl...@ben-hanna.com ] > 
To: "Foreman users" < [ mailto:foreman-users@googlegroups.com | 
foreman-users@googlegroups.com ] > 
Sent: Wednesday, December 7, 2016 6:08:51 AM 
Subject: [foreman-users] This thing itches me 

Hey all, 
I am trying to collect and learn about the things that mostly {piss you 
off,itch} on Foreman. 
It could be little things like a misplaced button or big things. Anything. 

So let's start a thread of what are the things that mostly piss you off in 
Foreman. 

Here are my contributions to the thread: 

* We need to add "compute resource" select to hostgroup, so when I create new 
host(s) I do not have to select a compute resource each time. 
* Associating provisioning templates to an operating system is complicated and 
can be simplified 


Now: it's your turn :) 

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 [ 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 [ 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 [ 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: Foreman 1.14.0-RC1 available for testing

['Jason B. Nance' via Foreman users]

> Looks like centos-release-scl-rh-2-2 has the wrong key? 

> nodejs-css-loader and foreman (two packages I picked at random) both use 
> PGP#f06d8950 but rpm -K for centos-release-scl-rh gives me PGP#f4a80eb5 


Release candidate packages aren't [re-]signed. 

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.

Re: [foreman-users] suppressing Server: WEBrick/1.3.1 (Ruby/2.0.0/2015-12-16) OpenSSL/1.0.1e

['Jason B. Nance' via Foreman users]

Hi Eamonn, 

~]# curl -I -L http://`hostname`:8000 
HTTP/1.1 404 Not Found 
Content-Type: text/html;charset=utf-8 
X-Cascade: pass 
Content-Length: 450 
X-Xss-Protection: 1; mode=block 
X-Content-Type-Options: nosniff 
X-Frame-Options: SAMEORIGIN 
Server: WEBrick/1.3.1 (Ruby/2.0.0/2015-12-16) OpenSSL/1.0.1e 
Date: Tue, 13 Dec 2016 14:18:10 GMT 
Connection: Keep-Alive 

In my experience the WEBrick service is not normally used with TFM (and I don't 
have anything listening on TCP:8000). Did someone on your team, by chance, 
enable the "puppetmaster" service thinking it was off in err? That service uses 
the embedded WEBrick server but TFM uses Passenger with httpd for Puppet 
typically. 

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.

Re: [foreman-users] [Katello 3.1] Stale package counts on repository

['Jason B. Nance' via Foreman users]

Hi John, 

> Sync: 
> Status: Success 
> Last Sync Date: 10 minutes 
> Created: 2016/12/12 12:18:20 
> Updated: 2016/12/12 13:24:46 
> Content Counts: 
> Packages: 0 
> Package Groups: 0 
> Errata: 0 

I see this happen sometimes when packages appear in multiple repos. It appears 
to only be an interface issue as the packages still "work". In my case it 
normally clears up in a day or so (when routine cleanup maintenance runs) but 
you can also force a clean up by setting "force_post_sync_actions" to "yes" 
under Settings -> Content and then re-running the sync. 

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.

Re: [foreman-users] Python API Question - Pagination

['Jason B. Nance' via Foreman users]

> Are there any examples out there for dealing with multi-page responses from a 
> python-requests-type query ? 

Hi Dan, 

Specific to Katello/TFM you can include URL parameters "page" and "per_page". 

(https://groups.google.com/forum/#!topic/foreman-users/k09MfRSant4) 

So you could do your initial query, check out the results to see if there are 
more results, then loop with addition queries to get the remaining pages. 

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.

Re: [foreman-users] Deleting smart class parameters when deleting a puppetclass

['Jason B. Nance' via Foreman users]

+1 for delete them given that no where else I can recall in TFM is there any 
sort of "undelete" or configuration version history (though I'd love to see the 
latter so that we can compare changes/rollback/etc). 

j 



From: "Greg Sutcliffe"  
To: "Foreman users"  
Sent: Thursday, December 8, 2016 10:50:45 AM 
Subject: Re: [foreman-users] Deleting smart class parameters when deleting a 
puppetclass 

Tricky question. I agree they're not so useful without a record of what class 
they were tied to, and worse, if you upload a new class of the same name, it 
may no longer accept those parameters, so it's questionable if they can be 
restored smoothly anyway. 

My gut feeling is to drop them - but before we go there, let me ask a UI 
question. Given the current import page already shows quite a lot of 
information, is there a good way to also show what parameter overrides will be 
deleted? 

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 [ 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] Lifecycle Environments ordering

['Jason B. Nance' via Foreman users]

You should add this request to the "this thing itches me" thread. I run into 
the same issue - spend the time getting lifecycles setup just as I want them, 
hosts added, content views, etc, and then the developers are like "oh, hey, we 
wan to add another environment in the string" 

As far as I know that means starting over and migrating hosts. :-\ 

j 



From: "Lachlan Musicman"  
To: foreman-users@googlegroups.com 
Sent: Tuesday, December 6, 2016 11:02:34 PM 
Subject: [foreman-users] Lifecycle Environments ordering 

Hola, 

Is there any way to reorder Lifecycle Environments after they've been created? 

EG: 

I created "Cluster Dev" and then "Cluster Prod" 

Library - Cluster Dev - Cluster Prod 

Now I realise I want a "Cluster UAT" that would go after Dev but before Prod 

Library - Cluster Dev - Cluster UAT - Cluster Prod 

Is that possible, or do I need to build a new LE? 

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

[foreman-users] Dozens of Package Profile Update tasks for a single host

['Jason B. Nance' via Foreman users]

Hello Everyone,

When I build a new host, restart Katello/TFM, and also on occasion I see dozens 
of "Package Profile Update for " tasks running all at the same time 
for the same host.  For example, if I build a new host call foo.bar.com, there 
will be a couple dozen "Package Profile Update for foo.bar.com" tasks.

Is this normal?  It seems to bog down pulp.

Regards,

j


Action:
Actions::Pulp::Consumer::GenerateApplicability
State: waiting for Pulp to start the task
Input:
{"uuids"=>["be86c791-5dd7-4b0a-a3f8-10a9aba9fc22"],
 "remote_user"=>"admin",
 "remote_cp_user"=>"admin"}
Output:
{"pulp_tasks"=>
  [{"exception"=>nil,
"task_type"=>
 
"pulp.server.managers.consumer.applicability.regenerate_applicability_for_consumers",
"_href"=>"/pulp/api/v2/tasks/0f70e8e1-97b4-46f0-8d5f-a55446fbffd5/",
"task_id"=>"0f70e8e1-97b4-46f0-8d5f-a55446fbffd5",
"tags"=>["pulp:action:content_applicability_regeneration"],
"finish_time"=>nil,
"_ns"=>"task_status",
"start_time"=>nil,
"traceback"=>nil,
"spawned_tasks"=>[],
"progress_report"=>{},
"queue"=>"reserved_resource_worke...@katello.ipa.centric.lab.dq",
"state"=>"waiting",
"worker_name"=>"reserved_resource_worke...@katello.ipa.centric.lab",
"result"=>nil,
"error"=>nil,
"_id"=>{"$oid"=>"5841ff9ebedbc883286e6109"},
"id"=>"5841ff9ebedbc883286e6109"}],
 "poll_attempts"=>{"total"=>22, "failed"=>0}}

-- 
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.1] syncing forge modules in an air-gapped environment

['Jason B. Nance' via Foreman users]

Hi JC, 

The missing link is pulp-puppet-module-builder, but you're going to need a Git 
repo (it can be local). Basically you want to grab the modules you want, unpack 
them, commit them to a repository, and run pulp-puppet-module-builder (which 
will repack them, put them in a directory you specify, and create 
PULP_MANIFEST). That process is creating a local "forge". Then you can tell 
Katello to sync your local "forge". 

Setting up a local git repo is as simple as: 

mkdir /path/to/foo 
cd /path/to/foo 
git init 
git checkout -b master 
cp /some/files /path/to/foo 
git add files 
git commit -m 'initial add' 

Then your Git URL for pulp-puppet-module-builder can be /path/to/foo or 
file:///path/to/foo. 

Regards, 

j 




From: "JC"  
To: "Foreman users"  
Sent: Tuesday, November 29, 2016 10:00:51 AM 
Subject: [foreman-users] [Katello 3.1] syncing forge modules in an air-gapped 
environment 

Hi all, 

I have two Katello 3.1 servers - K1 faces the internet, K2 is an air-gapped 
environment. 

K1 happily syncs with [ http://forge.puppetlabs.com/ | 
http://forge.puppetlabs.com ] . I then tarball and promote the content under 

/var/lib/pulp/published/puppet/http/repos/Default_Organization-Puppet_Forge-Forge/system
 

to K2, where it is published locally over http. 

My attempts to get K2 to sync with this content (via http:// or file:/// ) have 
been unsuccessful. K2 appeared to want modules.json , so I grabbed that ( [ 
http://forge.puppetlabs.com/modules.json | 
http://forge.puppetlabs.com/modules.json ] ), and K2 looked happier (it knows 
how many modules there are now), but still no dice. For each module it reports: 

"exception" => 'Module' object has no attribute 'filename'" 

I wondered whether I'm supposed to also provide a PULP_MANIFEST file, and 
whether pulp-puppet-module-builde r should be used, but that seems to want to 
face git (which I'm not using). 

Any pointers would be much appreciated. 

JC. 


-- 
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] [Bug 16853] SSH Host Keys Not Uploaded When Joining IPA Realm

['Jason B. Nance' via Foreman users]

OMG THANK YOU!  This works perfectly!

j


- Original Message -
From: "Tim" 
To: "Foreman users" 
Sent: Monday, November 28, 2016 4:38:13 PM
Subject: [foreman-users] [Bug 16853] SSH Host Keys Not Uploaded When Joining 
IPA Realm

I added the following to the kickstart before the freeipa/idm register section. 
The issue is the keys haven't been generated before the server is registered.

# Added to fix SSHFP DNS entries not being created. 
https://access.redhat.com/solutions/1320523

/usr/sbin/sshd-keygen

-- 
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] [Bug 16853] SSH Host Keys Not Uploaded When Joining IPA Realm

['Jason B. Nance' via Foreman users]

Hello everyone,

When I provision a new host that is joined to a FreeIPA realm its host key is 
not uploaded.  I opened bug 16853 for this issue:

http://projects.theforeman.org/issues/16853

Does anyone have any ideas on a workaround or resolution to this?

Thanks,

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.

[foreman-users] Where did the API docs go?

['Jason B. Nance' via Foreman users]

The API documentation seems to have disappeared.  This used to work:

https://theforeman.org/plugins/katello/3.1/api/index.html

Now it returns a 404, and I don't see a link to the API docs when browsing from 
the root of the documentation.

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.

Re: [foreman-users] Naming products and repos?

['Jason B. Nance' via Foreman users]

Here are a couple screen shots that show the layout of one of my Katello 
instances: 

Products: 

https://tresgeek.net/cloud/index.php/s/RgYDpYl09ePjqWm 

Content Views: 

https://tresgeek.net/cloud/index.php/s/MByLW0Ho99rIFOS 

(this instance doesn't have OEL, but it's pretty much the same as CentOS with 
some minor differences) 

I, too, struggled with how to organize my products. I landed on this for a 
couple reasons: 

1) I knew I was going to need/use CVs 
2) Grouping by vendor/upstream felt "right" 

Why CVs, you ask? For me it is to maintain consistency and give a path for 
rollbacks. Product repos are raw and versionless. You get what you get when you 
get it. CVs are basically snapshots or moments in time (handled via symlinks 
and database info). 

I classify systems as either non-prod or prod, so my process looks like this: 

Product repos are updated nightly. 
CV version is created and prompted to "non-prod" the day before non-prod 
patching. 
Non-prod systems patched. 
A few weeks later, that same CV version is prompted to "production" the day 
before production patching. 
Production systems patched. 

That gives me a few weeks of bake-in time for updates before they go to 
production. It also means that a server installed on Friday as has the same 
versions of the same packages that were installed on a server of the same 
environment on Monday. 
If an issue is discovered after patching, I can roll everything back to the 
previous known good CV version. 

I also make use of Composite Content Views, which are just a collection of 
specific versions of CVs. CCVs allow a couple things to happen: 

1) Share the same version of a CV across multiple different distros (for 
example, EPEL 7 is used by both CentOS 7 and OEL 7) 
2) Allows a "sub" CV version to get wonky without breaking the whole process 

Some elaboration on #2... My Katello box isn't always the happiest of things. 
Sometimes CV version creation/promotion fails. If it's the day before patching 
and my Software Collections CV version create/promote is failing and I don't 
have time to fix it, I don't want to have to delay patching (especially for 
such a "minor" repo in my environment). So with a CCV I can just use the last 
known good CV version of SCL in my CCV. 

There's a bit more to this as how CVs, lifecycle envs, host groups, and 
activate keys all relate, but I'll stop the fire hose here for now. :) 

TL;DR: CVs are about maintaining consistency and content flow through your 
environment (IMO). 

Clear as mud? 

j 



From: "Alan Evans"  
To: "Foreman users"  
Cc: ja...@tresgeek.net 
Sent: Thursday, November 10, 2016 12:41:04 PM 
Subject: Re: [foreman-users] Naming products and repos? 

Jason, 

I have considered going to a single "CentOS" product. I still haven't wrapped 
my head around content views. It seems like a needless layer of abstraction but 
maybe I just don't get it yet. 

Thanks for your thoughts, this is exactly the discussion I was hoping to have. 

-Alan 

On Wednesday, November 9, 2016 at 6:45:37 PM UTC-7, Jason B. Nance wrote: 


HI Alan, 

Regarding products, I organize by the upstream/vendor not by versions. For 
example, I have CentOS, OEL, and EPEL products. My content views are where I 
split up stuff into versions and such. 

Your examples look good to me. 

j 



From: "Alan Evans" < [ javascript-blocked: | alanw...@gmail.com ] > 
To: "Foreman users" < [ javascript-blocked: | forema...@googlegroups.com ] > 
Sent: Wednesday, November 9, 2016 5:19:54 PM 
Subject: [foreman-users] Naming products and repos? 

Is there any guide or are there any recommendations for naming/labeling 
products and repos? 

Is CentOS, CentOS 6, CentOS 6 x86_64 a product? 
What are people doing for CentOS/EPEL? 

If left to it's own devices katello just replaces spaces with underscores for 
product/repo labels. 

What about other "products?" 
Is Katello a product? Katello 3.2? 
Puppet? Puppet PC1? 
Puppet Enterprise? Puppet Enterprise 2016.4? or is the product "Puppet" with 
repos for the versions? 

I am leaning toward: 

Product: CentOS 6 (centos-6) 
Repo: CentOS 6 x86_64 OS - centos-6-x86_64-os = [ 
http://mirror.centos.org/centos/6/os/x86_64/ | 
http://mirror.centos.org/centos/6/os/x86_64/ ] 
Repo: CentOS 6 x86_64 Updates - centos-6-x86_64-updates = [ 
http://mirror.centos.org/centos/6/updates/x86_64/ | 
http://mirror.centos.org/centos/6/updates/x86_64/ ] 
- or more generally - 
Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = lower( [ 
http://mirror.centos.org/centos/$major/$repo/$arch/ | 
http://mirror.centos.org/centos/$major/$repo/$arch/ ] ) 

Product CentOS 7 (centos-7) 
Repo: CentOS $major $arch $repo - lower(centos-$major-$arch-$repo) = lower( [ 
http://mirror.centos.org/centos/$major/$repo/$arch/ | 
http://mirror.centos.org/centos/$major/$repo/$arch/ ] ) 

Product EPEL 6 (epel-6) 
Repo: EPEL $major $arch - lower(epel-$major-$arch) = [ 

Re: [foreman-users] [katello] modifying repository attributes in content views

['Jason B. Nance' via Foreman users]

On Thu, Nov 10, 2016 at 12:24 PM, 'Jason B. Nance' via Foreman users < [ 
mailto:foreman-users@googlegroups.com | foreman-users@googlegroups.com ] > 
wrote: 



Hi Tom, 

I don't believe that download policy is an attribute of a content view, only of 
a product repository, as packages aren't really owned by CVs, they are just 
referenced by CVs. So this change would really be at the product/repo level and 
affect consumers of that repo. You should be able to change the download policy 
of a repository at any time regardless of whether it is referenced via a CV or 
not and then initiate a sync (such as if you are moving from on demand to 
immediate). 

Sorry if I'm not following you, 

j 




> Each version of a content view has a reference to its own version of a 
> product repo. So for CV-1.0, there is a repo, and for CV-2.0 there is a repo. 
> My goal would be to allow the attributes of these separate repos to be 
> managed separately. How that management is presented to user user (eg. is it 
> tied to the content view, the lifecycle environment, or that version of a 
> repo) would be worth discussing. I'm interested, though, if anyone else has 
> seen the need for something like this. 

In your example of download policies how would this work, though? Each CV 
doesn't have its own copy of a package, right? I thought that CVs were 
basically just symlinks and database entries and that pulp was unaware of them. 

I don't mean to derail and I'm sorry if I'm focusing too much on one specific 
example. You noted download policy and http/https publishing. Is that where you 
would draw the line or would you also include mirror on sync, metadata, etc? 

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.

Re: [foreman-users] [katello] modifying repository attributes in content views

['Jason B. Nance' via Foreman users]

Hi Tom, 

I don't believe that download policy is an attribute of a content view, only of 
a product repository, as packages aren't really owned by CVs, they are just 
referenced by CVs. So this change would really be at the product/repo level and 
affect consumers of that repo. You should be able to change the download policy 
of a repository at any time regardless of whether it is referenced via a CV or 
not and then initiate a sync (such as if you are moving from on demand to 
immediate). 

Sorry if I'm not following you, 

j 



From: "Tom McKay"  
To: foreman-users@googlegroups.com 
Sent: Thursday, November 10, 2016 10:20:53 AM 
Subject: [foreman-users] [katello] modifying repository attributes in content 
views 

There are times when I wish I could edit the attributes of a repository in a 
specific content view and am wondering how hard this would be. 

For example, I sync RHEL-7.2 with a download policy of on demand. From there I 
craft a content view with specific filters and publish and promote it to my 
production lifecycle environment. At that point, I'd like to use inter-server 
sync (ISS) to export for use in another organization. However, ISS does not 
work with on demand. For my use case, I'd like to switch the download policy of 
the specific repo in the product content view to immediate, then sync it to 
pull down all the packages. 

Another use case would be creating unprotected custom product repos ("Publish 
via HTTP") but then when they make it to my production environment, switching 
them to protected HTTPS. 

Is manipulating aspects of repositories in content views something others would 
find useful? Is this a difficult thing to implement? 


-- 
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] Explanation of repo download policies

['Jason B. Nance' via Foreman users]

Hi Alan, 

> immediate - download files on sync 
> on_demand - download when a client requests a file the first time 
> background - doesn't immediate technically happen "in the background" 

I believe you are correct in your assessment here. In my opinion the trade offs 
would be: 

immediate - requires more disk space for packages that you may never 
install/update 
on_demand - potential delay the first time a package is requested, problems if 
the upstream happens to be down/corrupted when you need the package 
background - same issue as immediate plus a bit more work to have confidence in 
the current state of your product repos 

I use on_demand for my products (a full suite of CentOS 6/7, OEL 6/7, EPEL 6/7, 
etc) and have been happy with it. I like to keep my Katello server as small as 
I can because it is a VM, the current backup strategies aren't ideal, so 
snapshots are used a lot. 

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.

[foreman-users] LDAP users not showing up, partially functional

['Jason B. Nance' via Foreman users]

Hello,

I have configured my Katello 3.1 instance to use my FreeIPA instance for LDAP.  
I selected "automatically create accounts in Foreman" and "Usergroup sync".  
LDAP users don't show up under Administer -> Users.  They are able to login and 
manage CVs and such, but cannot set any of their user preferences (such as 
default Org), and cannot execute remote commands.  I have granted these users 
administrative privileges via an LDAP group.

Any ideas as to how to clear this up?

Thanks,

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.

[foreman-users] Workaround ideas for Puppet module adding issue

['Jason B. Nance' via Foreman users]

Hello everyone,

I have opened up http://projects.theforeman.org/issues/16309 in regards to an 
issue where you can't see the full list of available Puppet modules when you 
try to add one to a content view if there are too many.  That issue is starting 
to impact me more than expected and I'm looking for ideas for workarounds in 
the meantime.

Here are the basics:

Content View -> Puppet Modules -> Add New Module -> Filter (name = "foo" or 
author = "bar") -> Select A Version

After clicking the "Select A Verison" button, the list on the next page is 
truncated at 39 entries, ordered by author.  So if your module is number 40+ in 
the list it doesn't show up.  Any filter applied on this page is only on the 
current list.

For an example of this, sync Puppet Forge and then try and add the "ssh" 
module.  Since modules show up at least twice (explicit version + "Use Latest") 
there are over 39.  Alphabetically (by author) the module I want is low in the 
list, so it doesn't even show up.

Is there maybe a CLI command I could use?  I'm looking into the API as well...

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.

Re: [foreman-users] Failed to sync iso

['Jason B. Nance' via Foreman users]

Hi Denis, 

> im trying to sync http://oirase.annexia.org/virt-p2v/ 

That location is not a Yum repository (note how there isn't a "repodata" 
directory). 

> Repotype is file. 


The "file" type is when you would be referencing a location local to the 
Katello server itself. It is similar to putting the following in a browser: 

file:///opt/my/local/repo 

You can manually add each of those RPMs to a product on your Katello install, 
but they will not be automatically pulled/updated. 

I don't believe you can sync ISOs in this way. 

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.

Re: [foreman-users] Re: Foreman 1.13 install - puppet errors

['Jason B. Nance' via Foreman users]

It's good form and good karma to include specifics of what you did to get it 
working for the benefit of the herd... 




From: "Andrew Enstad"  
To: "Foreman users"  
Sent: Friday, October 14, 2016 10:12:03 AM 
Subject: [foreman-users] Re: Foreman 1.13 install - puppet errors 


Got it working. I Tried some different options with the foreman-installer and 
now Puppet is happy. 

On Thursday, October 13, 2016 at 4:35:10 PM UTC-5, Andrew Enstad wrote: 


Anyone else having issues with the install of Foreman 1.13? 
I have a Centos7 server that I have been trying to install Foreman 1.13, but it 
errors out when it tries to do the initial Puppet Run. 

Output from the foreman-installer: 

Running "puppet agent -t"... 
Warning: Unable to fetch my node definition, but the agent run will continue: 
Warning: Error 400 on SERVER: Failed to find  via exec: Execution of 
'/etc/puppet/node.rb ' returned 1: 
Info: Retrieving pluginfacts 
Info: Retrieving plugin 
Info: Loading facts 
Error: Could not retrieve catalog from remote server: Error 400 on SERVER: 
Failed when searching for node : Failed to find [ 
http://foreman.quicksand.identix.com/ | foreman.quicksand.identix.com ] via 
exec: Execution of '/etc/puppet/node.rb ' returned 1: 
Warning: Not using cache on failed catalog 
Error: Could not retrieve catalog; skipping run 
ERR: The puppet agent command has failed has failed. 

Output from /var/log/foreman/production.log: 

Oct 13 16:22:39 foreman puppet-master[7211]: Starting Puppet master version 
3.8.7 
Oct 13 16:22:39 foreman puppet-master[7226]: The environment must be purely 
alphanumeric, not '' 
Oct 13 16:22:56 foreman puppet-master[7226]: Failed to find  via 
exec: Execution of '/etc/puppet/node.rb ' returned 1: 
Oct 13 16:22:56 foreman puppet-agent[7261]: Unable to fetch my node definition, 
but the agent run will continue: 
Oct 13 16:22:56 foreman puppet-agent[7261]: Error 400 on SERVER: Failed to find 
 via exec: Execution of '/etc/puppet/node.rb ' returned 1: 
Oct 13 16:22:56 foreman puppet-agent[7261]: Retrieving pluginfacts 
Oct 13 16:22:56 foreman puppet-agent[7261]: Retrieving plugin 
Oct 13 16:22:57 foreman puppet-agent[7261]: Loading facts 
Oct 13 16:22:59 foreman puppet-master[7226]: Failed when searching for node 
: Failed to find  via exec: Execution of 
'/etc/puppet/node.rb ' returned 1: 
Oct 13 16:22:59 foreman puppet-master[7226]: Failed when searching for node 
: Failed to find  via exec: Execution of 
'/etc/puppet/node.rb ' returned 1: 
Oct 13 16:22:59 foreman puppet-agent[7261]: Could not retrieve catalog from 
remote server: Error 400 on SERVER: Failed when searching for node : 
Failed to find  via exec: Execution of '/etc/puppet/node.rb 
' returned 1: 
Oct 13 16:22:59 foreman puppet-agent[7261]: Not using cache on failed catalog 
Oct 13 16:22:59 foreman puppet-agent[7261]: Could not retrieve catalog; 
skipping run 







-- 
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] API to Get Hosts with "configuration_status_label=Active"

['Jason B. Nance' via Foreman users]

Hi Vishal, 

> I want an API query which returns hosts with 
> "configuration_status_label=Active" 

I believe the key is 'host.configuration_status_label' (vs just 
'configuration_status_label'), but I don't know if this is something that the 
search API can filter on or not. 

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.

Re: [foreman-users] [Katello 3.1]: getting puppet modules in an air-gapped environment?

['Jason B. Nance' via Foreman users]

JC, 

My suggestion for you would be to use pulp-puppet-module-builder to create a 
local "forge" with only the modules you are interested in that Katello can 
sync. You can find some info about it here: 

https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html/Puppet_Guide/sect-Red_Hat_Satellite-Puppet_Guide-Adding_Puppet_Modules_to_Red_Hat_Satellite_6-Adding_Puppet_Modules_from_a_Git_Repository.html
 

Regards, 

j 



From: "JC"  
To: "Foreman users"  
Sent: Wednesday, October 12, 2016 8:15:13 AM 
Subject: [foreman-users] [Katello 3.1]: getting puppet modules in an air-gapped 
environment? 

Hi folks, 
I'm running Katello 3.1 in an air-gapped environment. I have a Katello 2.4 
server connected to the internet which collects the repos needed by the 3.1 
server. I 'export' the content from the 2.4 server manually, then present it to 
the 3.1 server via http. This is fine for the yum repos, but now I want to sync 
the puppet modules from the forge also. 
I've siphoned off the /var/lib/pulp/content/puppet_modules tar.gz files and 
collected [ https://forge.puppet.com/modules.json | 
https://forge.puppet.com/modules.json ] . All of which are presented to the 3.1 
server via http. However, looking at the 3.1 webserver logs, Katello can't find 
the tar.gz files when I start a sync -- it appears to be looking, for example, 
for /puppet_module*/system/releases/{first letter of package}/{package 
owner}/{package}.tar.gz . It does know which files it wants and how many 
though. 

*puppet_module is where the modules.json file and the tar.gz files are stored. 

Any suggestions? I've seen some other methods for getting and presenting the 
content from forge, but I'd really like Katello to own them internally. 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 [ 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] how to tell discovery ISO to use DHCP automatically

['Jason B. Nance' via Foreman users]

>>"Unattended provisioning failed: unable to upload facts.  Check your
>> network credentials."

> That means your network configuration is perhaps incorrect. Check logs.

It seems that the problem is in my process.  I noticed that when I do 
everything with PXE that first the host boots with the default PXE 
configuration, which is loading the discovery image.  From there I can go into 
the UI/API, look at my discovered hosts, and say "provision".  That is creating 
a host-specific (well, MAC-specific) PXE configuration that includes a one-time 
use authentication key.  So when the kexec happens and the host reboots and 
does the PXE the second time it gets a different configuration (one that 
includes the authentication key that was just created) and the installation 
happens.

When booting from the ISO and doing the discovery, upon reboot (from the ISO 
again) the host doesn't have the authentication key, so it can't upload the 
facts.  :-\

Is it possible to do some sort of time-based whitelist by MAC or IP or just 
temporarily disable the auth?  Or is there another process I should be 
following?

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.

[foreman-users] how to tell discovery ISO to use DHCP automatically

['Jason B. Nance' via Foreman users]

Hello,

I'm attempting to using a bootable ISO to discover hosts (vs PXE).  I created a 
bootable ISO using https://github.com/theforeman/foreman-discovery-image, and 
changed my "append" line in isolinux/isolinux.cfg to say:

append initrd=initrd0.img root=live:CDLABEL=fdi rootfstype=auto ro 
rd.live.image acpi=force rd.luks=0 rd.md=0 rd.dm=0 ip=dhcp rd.neednet=1 
nomodeset proxy.url=https://katello.my.domain proxy.type=foreman

When the host boots, though, the FDI workflow starts by asking me if I want a 
manual network setup or DHCP.

Is there a way to boot from a CD/ISO and automatically use DHCP and register as 
a discovered host (similar to how the the PXE boot discovery works)?  Or, if 
not DHCP, a way for me to set static network configuration so that the 
discovery can happen without human intervention?

Thanks,

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.

Re: [foreman-users] Re: Foreman 1.13.0 released

['Jason B. Nance' via Foreman users]

Yamakasi, 


My suggestion would be to start a new email thread (instead of replying to the 
"release" email) and include your "foreman-installer" call as well as what 
version of TFM packages you have installed and your yum repository 
configuration. I've not yet attempted to use Puppet 4 with TFM. 

j 



From: "yamakasi 014"  
To: "Foreman users"  
Cc: ja...@tresgeek.net 
Sent: Thursday, October 6, 2016 2:06:37 PM 
Subject: Re: [foreman-users] Re: Foreman 1.13.0 released 

Hi Jason, 

Thanks, that works. It might be nice when it's added to the docs ? I wonder why 
it's not there actually. 

With the Puppet 4.x repo enabled I already was afraid that the following was 
going to happen: 


[ERROR 2016-10-06 20:59:20 verbose] Could not find user puppet 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/owner.rb:21:in 
`block in insync?' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/owner.rb:20:in 
`map!' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/type/file/owner.rb:20:in 
`insync?' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property.rb:277:in 
`safe_insync?' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:123:in
 `sync_if_needed' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:88:in
 `block in perform_changes' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:87:in
 `each' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:87:in
 `perform_changes' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/resource_harness.rb:21:in
 `evaluate' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:224:in 
`apply' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:240:in 
`eval_resource' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `call' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block 
(2 levels) in evaluate' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:386:in `block in 
thinmark' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:385:in `thinmark' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:163:in `block 
in evaluate' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/graph/relationship_graph.rb:118:in
 `traverse' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction.rb:154:in 
`evaluate' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:222:in 
`block in apply' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/log.rb:155:in 
`with_destination' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/transaction/report.rb:137:in 
`as_logging_destination' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/resource/catalog.rb:221:in 
`apply' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:171:in `block 
in apply_catalog' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:223:in `block in 
benchmark' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/2.1.0/benchmark.rb:294:in `realtime' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:222:in `benchmark' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:170:in 
`apply_catalog' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:343:in 
`run_internal' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/configurer.rb:221:in `block 
in run' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/context.rb:65:in `override' 
[ERROR 2016-10-06 20:59:20 verbose] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:241:in `override' 
[ERROR 2016-10-06 20:59:20 verbose] 

Re: [foreman-users] Re: Foreman 1.13.0 released

['Jason B. Nance' via Foreman users]

Hi Yamakasi, 

In CentOS those packages are provided by SCLo-RH, which is enabled with the 
centos-release-scl-rh package. Verify that you have installed: 

centos-release-scl 
centos-release-scl-rh 
foreman-release-scl 

...and their corresponding repositories enabled, and that you do not have the 
SoftwareCollections.org repositories enabled. Then clear your yum cache. 

Regards, 

j 



From: "yamakasi 014"  
To: "Foreman users"  
Cc: foreman-annou...@googlegroups.com, domi...@cleal.org 
Sent: Thursday, October 6, 2016 12:19:53 PM 
Subject: [foreman-users] Re: Foreman 1.13.0 released 

Great, I did a new CentOS 7 install and see this error mainly: 

[ERROR 2016-10-06 13:16:11 verbose] Package: 
tfm-rubygem-audited-activerecord-4.2.0-2.el7.noarch (foreman) 
[ERROR 2016-10-06 13:16:11 verbose] Requires: rh-ruby22-ruby(release) 
[ERROR 2016-10-06 13:16:11 verbose] Package: 
tfm-rubygem-ruby_parser-3.6.3-4.el7.noarch (foreman) 
[ERROR 2016-10-06 13:16:11 verbose] Requires: rh-ruby22-ruby(rubygems) 
[ERROR 2016-10-06 13:16:11 verbose] Package: 
tfm-rubygem-friendly_id-5.1.0-3.el7.noarch (foreman) 
[ERROR 2016-10-06 13:16:11 verbose] Requires: rh-ruby22-ruby(rubygems) 
[ERROR 2016-10-06 13:16:11 verbose] Package: 
tfm-rubygem-facter-2.4.0-3.el7.x86_64 (foreman) 
[ERROR 2016-10-06 13:16:11 verbose] Requires: rh-ruby22-ruby(rubygems) 
[ERROR 2016-10-06 13:16:11 verbose] Package: 
tfm-rubygem-rest-client-1.8.0-1.el7.noarch (foreman) 
[ERROR 2016-10-06 13:16:11 verbose] Requires: sclo-ror42-rubygem(mime-types) < 
3.0 
[ERROR 2016-10-06 13:16:11 verbose] Package: 
tfm-rubygem-deacon-1.0.0-1.el7.noarch (foreman) 
[ERROR 2016-10-06 13:16:11 verbose] Requires: rh-ruby22-ruby(rubygems) 

Right repo's are in place following the docs. 

What do do here ? 


Op donderdag 6 oktober 2016 11:01:18 UTC+2 schreef Dominic Cleal: 

Foreman 1.13.0 is now available, our latest major release featuring 
improved IPv6 support, configurable boot loaders for UEFI support, DHCP 
performance enhancements and much more. 

Thanks to the 94 contributors to this release, who helped write, fix and 
translate it, and to the testers who've helped during the release 
candidate phase. 

Installation quick start: 
[ https://theforeman.org/manuals/1.13/quickstart_guide.html | 
https://theforeman.org/manuals/1.13/quickstart_guide.html ] 

Upgrade instructions: 
[ https://theforeman.org/manuals/1.13/index.html#3.6Upgrade | 
https://theforeman.org/manuals/1.13/index.html#3.6Upgrade ] 

Release notes: 
[ https://theforeman.org/manuals/1.13/index.html#Releasenotesfor1.13 | 
https://theforeman.org/manuals/1.13/index.html#Releasenotesfor1.13 ] 


Headline features 
= 
Support for creating and managing IPv6 subnets and hosts with IPv6 
and/or IPv4 addresses is new in this release, enabling deployment of 
dual and even single-stack IPv6 hosts. 

During host creation with DHCP, the PXE boot loader (filename) specified 
in the DHCP reservation can now be changed from PXELinux to a number of 
other supported loaders, e.g. GRUB Legacy or GRUB 2 (for UEFI), or left 
unset altogether. 

Lots more features can be found listed in the release notes: 
[ https://theforeman.org/manuals/1.13/index.html#Releasenotesfor1.13 | 
https://theforeman.org/manuals/1.13/index.html#Releasenotesfor1.13 ] 

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

Our list of supported OSes has changed, so please check these when 
setting up new installations or upgrading. 


Downloads 
= 
Packages may be found in the 1.13 directories on both [ http://deb.foreman.org/ 
| deb.foreman.org ] 
and [ http://yum.theforeman.org/ | yum.theforeman.org ] , and tarballs are on [ 
http://downloads.theforeman.org/ | downloads.theforeman.org ] . 

The GPG key used for RPMs and tarballs has the following fingerprint: 
84E7 90DF FB1D 2EAE C429 C6CD 4EA2 F7E7 7DFE 6FC2 
( [ https://theforeman.org/security.html#GPGkeys | 
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 | 
http://projects.theforeman.org/projects/foreman/issues/new ] 
Proxy: [ http://projects.theforeman.org/projects/smart-proxy/issues/new | 
http://projects.theforeman.org/projects/smart-proxy/issues/new ] 
Installer: 
[ http://projects.theforeman.org/projects/puppet-foreman/issues/new | 
http://projects.theforeman.org/projects/puppet-foreman/issues/new ] 

-- 
Dominic Cleal 
[ javascript-blocked: | dom...@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 

Re: [foreman-users] Search filter in Foreman API

['Jason B. Nance' via Foreman users]

Hi Harish, 

> There is no direct API to get all the reports for a specific host. To get 
> this, i'm trying to use search filter like 
> https://puppetmaster/api/reports?search="host_name=Myhostname; with no 
> results. 

The key for filtering by host is 'host', not 'host_name'. You will want to 
ensure that you URL encode your query as well. 

> Also, please tell me, how to use sort by in Foreman API's. 

The parameter you want is "order" 
(http://www.katello.org/docs/3.1/api/apidoc/reports/index.html). You can see 
what options are available by logging into your Foreman instance, opening a 
host and clicking on "Reports". Once in there hover over the column headers to 
see the different options. For example, to order by "Last report" you would 
say: 

?order=reported+ASC=host+%3D+my.host.name 

(note the search parameter is URL encoded) 

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.

Re: [foreman-users] discovered repo not synching packages

['Jason B. Nance' via Foreman users]

Hi Jorick, 

> After doing a discovery on [ 
> https://fedorapeople.org/groups/katello/releases/yum/3.1/ | 
> "https://fedorapeople.org/groups/katello/releases/yum/3.1/; ] and adding the 
> different repo's in it, I have two repositories that are not syncing any 
> packages. The package count is 0 while there are multiple packages in it. 

I have found during my testing that it can be somewhat easy to temporarily get 
the UI out of sync with Pulp - meaning that Pulp is syncing packages but 
Katello is reporting 0 packages in a repository but /var/lib/pulp/ is 
populated - when going through multiple create/delete operations in a short 
period of time. I believe this happens because maintenance tasks aren't getting 
a chance to run (for example, to remove orphaned packages). 

For me the issue has cleared itself up within a day or so (after maintenance 
tasks have had a chance to run), but I have also been able to force a fix by 
setting "force_post_sync_actions" to "true" in Administer -> Settings -> 
Content, then syncing the repository in question. (credit goes to JSherrill for 
that idea) 

Outside of that, I would compare the "discovered" repo URL to your manual 
setting. 

Hope this helps, 

j 



From: "Jorick Astrego"  
To: foreman-users@googlegroups.com 
Sent: Thursday, October 6, 2016 3:16:54 AM 
Subject: [foreman-users] discovered repo not synching packages 



Hi, 

After doing a discovery on [ 
https://fedorapeople.org/groups/katello/releases/yum/3.1/ | 
"https://fedorapeople.org/groups/katello/releases/yum/3.1/; ] and adding the 
different repo's in it, I have two repositories that are not syncing any 
packages. The package count is 0 while there are multiple packages in it. 


The problematic repo's are: 




client el7 x86_64 


candlepin el7 x86_64 





BQ_BEGIN


2016-10-06 10:09:49 [app] [I] Started POST 
"/katello/api/v2/repositories/sync_complete?token=**" for 
**.***.***.** at 2016-10-06 10:09:49 +0200 
2016-10-06 10:09:49 [app] [I] Processing by 
Katello::Api::V2::RepositoriesController#sync_complete as */* 
2016-10-06 10:09:49 [app] [I] Parameters: {"call_report"=>"[FILTERED]", 
"event_type"=>"repo.sync.finish", "payload"=>{"importer_id"=>"yum_importer", 
"exception"=>nil, "repo_id"=>"Netbulae-Katello-candlepin_el7_x86_64", 
"traceback"=>nil, "started"=>"2016-10-06T08:09:21Z", 
"_ns"=>"repo_sync_results", "completed"=>"2016-10-06T08:09:49Z", 
"importer_type_id"=>"yum_importer", "error_message"=>nil, 
"summary"=>{"content"=>{"state"=>"FINISHED"}, "comps"=>{"state"=>"FINISHED"}, 
"purge_duplicates"=>{"state"=>"FINISHED"}, 
"distribution"=>{"state"=>"FINISHED"}, "errata"=>{"state"=>"FINISHED"}, 
"metadata"=>{"state"=>"FINISHED"}}, "added_count"=>0, "result"=>"success", 
"updated_count"=>0, "details"=>{"content"=>{"size_total"=>0, "items_left"=>0, 
"items_total"=>0, "state"=>"FINISHED", "size_left"=>0, 
"details"=>{"rpm_total"=>0, "rpm_done"=>0, "drpm_total"=>0, "drpm_done"=>0}, 
"error_details"=>nil}, "comps"=>{"state"=>"FINISHED"}, 
"purge_duplicates"=>{"state"=>"FINISHED"}, "distribution"=>{"items_total"=>0, 
"state"=>"FINISHED", "error_details"=>nil, "items_left"=>0}, 
"errata"=>{"state"=>"FINISHED"}, "metadata"=>{"state"=>"FINISHED"}}, 
"id"=>"57f606cd67e2350812c36e23", "removed_count"=>0}, 
"token"=>"**", "api_version"=>"v2", "repository"=>{}} 
2016-10-06 10:09:49 [app] [I] Sync_complete called for candlepin el7 x86_64, 
running after_sync. 
2016-10-06 10:09:49 [app] [I] Completed 200 OK in 36ms (Views: 0.3ms | 
ActiveRecord: 1.9ms) 

BQ_END


When I add the repo manually with [ 
https://fedorapeople.org/groups/katello/releases/yum/3.1/client/el7/x86_64/ | 
"https://fedorapeople.org/groups/katello/releases/yum/3.1/client/el7/x86_64/; ] 
it syncs perfectly. 









Met vriendelijke groet, With kind regards, 

Jorick Astrego 

Netbulae Virtualization Experts 

Tel: 053 20 30 270  i...@netbulae.euStaalsteden 4-3AKvK 
08198180 
Fax: 053 20 30 271  www.netbulae.eu 7547 TA Enschede
BTW NL821234584B01 




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

Re: [foreman-users] How to push patches from Foreman-Katello to the RHEL Clients

['Jason B. Nance' via Foreman users]

Hi Balaji, 

> Could someone please guide me how to push OS patches from Foreman-Katello to 
> the RHEL clients. 

Are you looking for information on how to sync and make packages available to 
your clients or on how to tell the clients to perform the updates? 

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.

Re: [foreman-users] Adding tftp / pxe target

['Jason B. Nance' via Foreman users]

It has become apparent to me that the bigger issue here is that the Yum repos 
I'm syncing for OEL from Oracle aren't kickstart trees, so they are missing 
files such as squashfs.img.  My first thought after that realization was to 
just slap the missing files into /var/lib/pulp/..., but that felt like a recipe 
for future problems.  Now the path I'm headed down is to mount the installation 
DVD and sync it.

If anyone has had to deal with OEL or just has another idea in general I'm open.

Big thanks to stbenjam in IRC for the info and ideas.

j


- Original Message -
From: "'Jason B. Nance' via Foreman users" <foreman-users@googlegroups.com>
To: foreman-users@googlegroups.com
Sent: Friday, September 16, 2016 2:30:53 PM
Subject: [foreman-users] Adding tftp / pxe target

Hello,

After I installed and configured (all via the web UI) Katello 3.1 / Foreman 
1.12 and synced CentOS 7 repositories it seems that all of the tftp/pxe stuff 
necessary to do pxe installs of CentOS was automagically setup for me.

For example, /var/lib/tftpboot/boot contains:

CentOS-7-x86_64-initrd.img
CentOS-7-x86_64-vmlinuz

...and 
/var/lib/pulp/published/yum/http/repos/My_Org/Library/custom/centos/c7/LiveOS/squashfs.img
 exists.

I'm trying to add pxe boot/install support for OEL 7.  I created similar 
products, content views, media, and OS as I have for CentOS.  I used host 
discovery to create a new host entry and selected the OEL stuff I setup.  
/var/lib/tftpboot/boot/OracleLinux-7-x86_64-initrd.img and 
OracleLinux-7-x86_64-vmlinuz where created for me, but they were 0 byte files.  
So I manually replaced those files with the appropriate ones from the OEL 
"boot" CD.

However, the installer now fails because 
/var/lib/pulp/published/yum/http/repos/My_Org/Library/custom/oel/o7/LiveOS/squashfs.img
 doesn't exist.

What is supposed to create those files?  Is there a hammer command I should run 
or something?

Thanks,

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.

Re: [foreman-users] [Re-]Added repo won't pull down packages

['Jason B. Nance' via Foreman users]

> Here's what I've tried:
> 
> Deleted the "EPEL 7" yum repo
> Ran "foreman-rake katello:delete_orphaned_content RAILS_ENV=production"
> Ran "pulp-admin orphan list" (it always reports 0 for everything)
> Ran "pulp-admin repo list" and make sure there were no "EPEL" repos listed
> Removed all directories with "epel" in the name in
> "/var/lib/pulp/published/yum/*" (recursively)
> Removed all references to "epel" in all "listing" files in
> "/var/lib/pulp/published/yum/*" (recursively)
> Rebooted three times for the lulz
> [Re-]Added EPEL 7 (with the same label "epel7-int")
> Ran manual sync, which indicated that there are no new packages

I just ran:

foreman-rake katello:reindex RAILS_ENV=production
foreman-rake katello:clean_backend_objects RAILS_ENV=production

And one or both of those commands cleaned up the issue.

*shrug*

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.