[foreman-users] Katello inter sync option

2016-07-27 Thread Unix SA

Hello,

I am following procedure below to sync contents from my upstream satellite 
to downstream.

https://access.redhat.com/documentation/en/red-hat-satellite/6.2-beta/paged/content-management-guide/appendix-c-synchronizing-content-between-satellite-servers

now after updating my organization to URL mention in document, i am able to 
sync one CV

""

$ hammer organization update \
--name "Mega Subsidiary" \
--redhat-repository-url \
http://megacorp.com/pub/cdn-latest

Organization updated
"""

but for another CV, the URL is different, do i have to update URL everytime 
when i want to sync different CVs ? or am i missing something?


Procedure i followed is:-
1) set export path to /var/lib/html/pub/export
2) set selinux permissions
3) set "immediate" for my RHEL7 kickstart repository 
4) export repository with "hammer repository export --id 2 --export-to-iso 
0" 
5) in downstream URL update manifest with URL 
"https://upstream/pub/export/ORG-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_Kickstart_x86_64_7_2/ORG/Library/";

sync works for "kickstart" , but then how to sync for "rpm repository" now 
as URL will be different for it?

Regards,
DJ

-- 
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 inter sync option

2016-07-27 Thread Chris Duryee


On 07/27/2016 04:38 AM, Unix SA wrote:
> 
> Hello,
> 
> I am following procedure below to sync contents from my upstream satellite 
> to downstream.
> 
> https://access.redhat.com/documentation/en/red-hat-satellite/6.2-beta/paged/content-management-guide/appendix-c-synchronizing-content-between-satellite-servers
> 
> now after updating my organization to URL mention in document, i am able to 
> sync one CV
> 
> ""
> 
> $ hammer organization update \
> --name "Mega Subsidiary" \
> --redhat-repository-url \
> http://megacorp.com/pub/cdn-latest
> 
> Organization updated
> """
> 
> but for another CV, the URL is different, do i have to update URL everytime 
> when i want to sync different CVs ? or am i missing something?
> 
> 
> Procedure i followed is:-
> 1) set export path to /var/lib/html/pub/export
> 2) set selinux permissions
> 3) set "immediate" for my RHEL7 kickstart repository 
> 4) export repository with "hammer repository export --id 2 --export-to-iso 
> 0" 
> 5) in downstream URL update manifest with URL 
> "https://upstream/pub/export/ORG-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_Kickstart_x86_64_7_2/ORG/Library/";
> 
> sync works for "kickstart" , but then how to sync for "rpm repository" now 
> as URL will be different for it?
> 
> Regards,
> DJ
> 

Typically, the easiest way to do this is to create a single CV that has
all the content you'd like to export. That way if you export multiple
items, the CDN url on the downstream server stays the same.

-- 
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] undefined method `join' for #, receiving salt states from smartproxy

2016-07-27 Thread Tom K.
Hi,

I've a running Foreman 1.11.3 and a Smartyproxy 1.11.3 on 2 different 
machines. The Smartproxy serves the salt-api/saltmaster. Now, if I query 
from Foreman the states of the Saltmaster SmartyProxy, nothing happens. 

Sometimes a popup appears with the message 

Error: ERF12-4701 [ProxyAPI::ProxyException]: Unable to fetch Salt states 
list ([ProxyAPI::ProxyException]: ERF12-7301 [ProxyAPI::ProxyException]: 
Unable to fetch Salt environments list ([RestCli...) for proxy 
https:/fosp-saltmaster-001:8443/salt/


In the *forman-proxy.log* on the smartproxy tells me 

E, [2016-07-27T10:05:26.163632 #2422] ERROR -- : undefined method `join' 
for # (NoMethodError)
/usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/showexceptions.rb:37:in 
`rescue in call'
/usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/showexceptions.rb:21:in 
`call'
/usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:124:in `call'
/usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:1417:in `block in 
call'
/usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:1499:in `synchronize'
/usr/share/gems/gems/sinatra-1.3.5/lib/sinatra/base.rb:1417:in `call'
/usr/share/gems/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/usr/share/gems/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/usr/share/gems/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/usr/share/gems/gems/rack-1.6.4/lib/rack/builder.rb:153:in `call'
/usr/share/gems/gems/rack-1.6.4/lib/rack/handler/webrick.rb:88:in `service'
/usr/share/ruby/webrick/httpserver.rb:138:in `service'
/usr/share/ruby/webrick/httpserver.rb:94:in `run'
/usr/share/ruby/webrick/server.rb:295:in `block in start_thread'



The */var/log/foreman/production.log* throws

2016-07-27 10:10:48 [app] [W] ProxyAPI operation FAILED
 | ProxyAPI::ProxyException: ERF12-4701 [ProxyAPI::ProxyException]: Unable 
to fetch Salt states list ([ProxyAPI::ProxyException]: ERF12-7301 
[ProxyAPI::ProxyException]: Unable to fetch Salt environments list 
([RestCli...) for proxy https:/fosp-saltmaster-001:8443/salt/
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/lib/proxy_api/salt.rb:43:in
 
`rescue in states_list'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/lib/proxy_api/salt.rb:35:in
 
`states_list'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/controllers/foreman_salt/state_importer.rb:16:in
 
`fetch_states_from_proxy'
 | 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_salt-5.0.1/app/controllers/foreman_salt/salt_modules_controller.rb:60:in
 
`import'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/action_controller/metal/implicit_render.rb:4:in
 
`send_action'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/abstract_controller/base.rb:189:in
 
`process_action'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/action_controller/metal/rendering.rb:10:in
 
`process_action'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/actionpack-4.1.5/lib/abstract_controller/callbacks.rb:20:in
 
`block in process_action'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in
 
`call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:113:in
 
`call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
 
`block in halting_and_conditional'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
 
`call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
 
`block in halting_and_conditional'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
 
`call'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
 
`block in halting_and_conditional'
 | 
/opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/callbacks.rb:149:in
 
`call'




What's my problem? What can I do... I've really no idea


Thanks,

Tom

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


[foreman-users] foreman 1.11.3: 'attached_devices' key is no longer present in $foreman_interfaces global variable

2016-07-27 Thread herwig . bogaert
Hi 

I use the $foreman_interfaces global variable in the puppet manifests that 
configure the network interfaces of a host.

After upgrading to foreman 1.11.3 (from foreman 1.9) the 'attached_devices' 
key is no longer present in the $foreman_interfaces hash for interfaces of 
type bond.

In the example below, the comparison is shown between the interface 
information obtained from the API and the information stored in the 
$foreman_interfaces variable for the same host. The 'attached_devices' are 
absent in the latter. 

API: (https://foreman.dg.viaa.be/api/hosts/73/interfaces)

...

{... ,

"mac":"00:0a:f7:4a:3e:60", "ip":"10.9.136.65", "type":"bond", 
"name":"dg-qas-tra-01.dg.viaa.be", "virtual":true, "identifier":"bond0", 
"managed":true, "mode":"balance-alb", 

"bond_options":"miimon=100", "primary":true, "provision":true, "id":102, 
*"attached_devices":"p1p1,p1p2"*

}

...

output of 'notify { $foreman_interfaces:}':
Notice: {
"mac"=>"00:0a:f7:4a:3e:60", "ip"=>"10.9.136.65", "type"=>"Bond", 
"name"=>"dg-qas-tra-01.dg.viaa.be", "attrs"=>{}, "virtual"=>true, 
"link"=>true, "identifier"=>"bond0", "tag"=>"", "attached_to"=>"", 
"managed"=>true, "mode"=>"balance-alb", "bond_options"=>"miimon=100", 
"primary"=>true, "provision"=>true, "subnet"=>{.}
}


The same problem occurs when defining a new bond interface on a machine in 
foreman 1.11.3 so it is not a migration problem.


-- 
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 capsule content sync super slow?

2016-07-27 Thread Eric D Helms
Dylan,

Are you able to determine the network traffic between the server and
capsule? In general I think there are two possibilities, slow transfer of
data to the Capsule or slowness on the Capsule itself. I would recommend
checking the network speeds and the Capsule resources to see if its
constrained I/O wise or processes are eating the CPU.


Eric

On Tue, Jul 26, 2016 at 10:52 PM, Dylan Baars  wrote:

> Hi all,
>
> we have a katello 3.0.1 install with a katello capsule in our DMZ.
>
> we've noticed if we publish/promote content, the main katello server does
> this reasonably quickly, but tasks (to sync content) on the capsule are
> taking hours to complete to match the change on the main server. Does
> anyone know why this is? Can it be improved?
>
> Thanks!
> Dylan
>
> --
> You received this message because you are subscribed to the Google Groups
> "Foreman users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to foreman-users+unsubscr...@googlegroups.com.
> To post to this group, send email to foreman-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/foreman-users.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Eric D. Helms
Red Hat Engineering
Ph.D. Student - North Carolina State University

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


[foreman-users] Foreman Proxy is not recognized

2016-07-27 Thread Sai Krishna
Hello,

I have installed complete foreman on a separate vm, I have puppet master on 
other vm. I have installed foreman proxy on master server so that all the 
content which is on puppet master will be available on foreman. I'm seeing 
the foreman proxy service is running on puppet master. but when am trying 
to add that puppet master as smart proxy from foreman interface in the 
dropdown menu select "Smart Proxies", "New Proxy", URL with port "Submit". 
Please find the attachment for error.

*Unable to save *
- Unable to communicate with the proxy: ERF12-2530 
[ProxyAPI::ProxyException]: Unable to detect features 
([RestClient::SSLCertificateNotVerified]: SSL_connect returned=1 errno=0 
state=SSLv3 read server certificate B: certificate verif...) for proxy 
https://nyrh146.sample.com:8443/features
- Please check the proxy is configured and running on the host

Can anyone please guide me with the steps to configure puppet master with 
foreman so that all the content in master is available in foreman and can 
work from foreman and use foreman as CA.

Thank you 
Sai Krishna

-- 
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] Thank you from the Satellite Team

2016-07-27 Thread Bryan Kearney

Foreman Community:

Today Red Hat released Satellite 6.2. The official press release will go 
out tomorrow, but you can read about the release at [1]. This version of 
Satellite is based off of Foreman 1.11 and several of the plugins. The 
success of Red Hat Satellite is based on the hard work and collaboration 
of the Foreman Community. We appreciate all your effort, and are proud 
to be members of the community. Thank you for all the work, and we look 
forward to a successful 1.13!


-- bk

Bryan Kearney
Satellite Team
bkear...@redhat.com


[1] https://access.redhat.com/blogs/1169563/posts/2464761

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


[foreman-users] Re: Foreman Proxy is not recognized

2016-07-27 Thread Sai Krishna
I have changed the /etc/foreman-proxy/settings.yml file. I have change 
trusted host and foreman_url from puppetmaster to foremanvers FQDN. is this 
a wrong move ?

# the hosts which the proxy accepts connections from
# commenting the following lines would mean every verified SSL connection 
allowed
:trusted_hosts:
  - foremansever.com

# Endpoint for reverse communication
:foreman_url: https://foremanserver.com

I have generated new smart proxy certificates from foreman server and 
replaced the /etc/puppetlabs/ssl/certs/ca.pem, puppetserver.pem, 
/etc/puppetlabs/ssl/private_keys/puppetserver.pem
 
Still do I need to change anything. Please advice. 

Sai Krishna

-- 
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] Things missing from The Foreman UI, how to fix?

2016-07-27 Thread Alan Evans

I have noticed all of the sudden some things are missing from the UI.

1. On the host detail page (https://foreman/hosts/foo.example.com> I can no 
longer preview the classes
2. On the host edit page (https://foreman/hosts/foo.example.com/edit) I can 
no longer assign classes
3. On the host edit page (https://foreman/hosts/foo.example.com/edit) the 
puppet master dropdown is missing, and sometimes the puppet CA dropdown is 
missing also.

There are two things I can think that might have caused this.

1. I just updated from 1.11.1 to 1.12.1
2. I vaguely recall disabling/changing something recently in order to hide 
the classes tab on the edit page.

We're not using foreman as an ENC (mostly not anyway) and I think I 
remember using deface or something else to try to hide the classes from the 
edit screen.  The problem is I don't remember where that was?

Foreman 1.12.1
Ubuntu 14.04

Please help,
-Alan

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


[foreman-users] Re: Foreman Proxy is not recognized

2016-07-27 Thread Sai Krishna
using foreman - installer in interactive mode enabled puppet and foreman 
proxy and configured according 
to https://theforeman.org/manuals/1.12/index.html#3.2.3InstallationScenarios 
| setting up foreman with external puppet master.

Preparing installation Done
  Something went wrong! Check the log for ERROR-level output
  * Foreman Proxy is running at https://puppetserver.com:8443
  The full log is at /var/log/foreman-installer/foreman.log

[ INFO 2016-07-27 16:13:21 main] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:128:in 
`run'
[ INFO 2016-07-27 16:13:21 main] 
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:72:in 
`execute'
[ INFO 2016-07-27 16:13:21 main] /opt/puppetlabs/bin/puppet:5:in `'
[ INFO 2016-07-27 16:13:21 main] Puppet has finished, bye!
[ INFO 2016-07-27 16:13:21 main] Executing hooks in group post
[DEBUG 2016-07-27 16:13:21 main] Hook 
/usr/share/foreman-installer/hooks/post/10-post_install_message.rb returned 
nil
[ INFO 2016-07-27 16:13:21 main] All hooks in group post finished
[DEBUG 2016-07-27 16:13:21 main] Exit with status code: 1 (signal was 1)

*[ERROR 2016-07-27 16:13:21 main] Errors encountered during run:*
*[ERROR 2016-07-27 16:13:21 main]  Evaluation Error: Error while evaluating 
a Function Call, undefined class/module HighLine:: at 
/usr/share/gems/gems/kafo-0.9.1/modules/kafo_configure/manifests/init.pp:14:3 
on node puppetserver.com*

[DEBUG 2016-07-27 16:13:21 main] Cleaning /tmp/d20160727-13857-1irv5ck
[DEBUG 2016-07-27 16:13:21 main] Cleaning 
/tmp/kafo_hiera20160727-13857-16fcv4y
[DEBUG 2016-07-27 16:13:21 main] Cleaning /tmp/default_values.yaml

Please advice


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


[foreman-users] Re: Foreman Proxy is not recognized

2016-07-27 Thread Dylan Baars
Hi Sai,

your SSL error sounds exactly like this 
issue: http://projects.theforeman.org/issues/15530

For my proxy, settings.yml as this as trusted hosts and reverse 
communications entries:

# the hosts which the proxy accepts connections from
# commenting the following lines would mean every verified SSL connection 
allowed
:trusted_hosts:
  - mainformanserver.com
  - foremanproxy.com

# Endpoint for reverse communication
:foreman_url: https://mainforemanserver.com

It is worth checking you can connect the proxy via HTTP - so in 
settings.yml make sure :http_port: is configured - e.g.
:http_port: 8000

and then try adding the smart proxy via that address - 
http://foremanproxy.com:8000/

Hope that helps
Dylan



-- 
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 capsule content sync super slow?

2016-07-27 Thread Dylan Baars
Hi Eric,

I see celery and mongod on the capsule using a lot of CPU time (celery 
seems to jump between 50-100%, and has been going for 435:32.54) and mongod 
~30-40%, 286:18.74. Here's current memory usage on the box

free -h
  totalusedfree  shared  buff/cache   
available
Mem:   5.7G3.5G166M 37M2.0G   
 1.9G
Swap:  7.8G2.4G5.4G

and current IO
[root@wellcapsuleext foreman-proxy]# sar
Linux 3.10.0-327.el7.x86_64 (wellcapsuleext.niwa.co.nz) 07/28/2016 
 _x86_64_(6 CPU)

12:00:01 AM CPU %user %nice   %system   %iowait%steal 
%idle
12:10:01 AM all  0.76  0.03  0.41  0.02  0.00 
98.78
12:20:01 AM all  1.11  0.03  0.51  0.01  0.00 
98.35
12:30:01 AM all  0.94  0.03  0.46  0.01  0.00 
98.57
12:40:01 AM all  0.77  0.03  0.41  0.01  0.00 
98.78
12:50:01 AM all  1.09  0.03  0.50  0.02  0.00 
98.37
01:00:01 AM all  0.95  0.03  0.47  0.01  0.00 
98.54
01:10:01 AM all  0.74  0.03  0.39  0.01  0.00 
98.83
01:20:01 AM all  1.07  0.02  0.48  0.02  0.00 
98.40
01:30:01 AM all  0.92  0.03  0.45  0.06  0.00 
98.54
01:40:01 AM all  0.77  0.03  0.41  0.01  0.00 
98.79
01:50:01 AM all  1.07  0.03  0.49  0.01  0.00 
98.41
02:00:01 AM all  1.00  0.03  0.49  0.08  0.00 
98.41
02:10:01 AM all  0.76  0.03  0.40  0.01  0.00 
98.81
02:20:01 AM all  1.09  0.02  0.50  0.01  0.00 
98.38
02:30:01 AM all  0.94  0.03  0.45  0.01  0.00 
98.57
02:40:02 AM all  0.79  0.03  0.42  0.01  0.00 
98.76
02:50:01 AM all  1.09  0.03  0.50  0.02  0.00 
98.36
03:00:01 AM all  0.93  0.03  0.46  0.01  0.00 
98.57
03:10:01 AM all  0.79  0.03  0.40  0.01  0.00 
98.77
03:20:01 AM all  1.09  0.03  0.50  0.01  0.00 
98.37
03:30:01 AM all  0.96  0.02  0.50  0.01  0.00 
98.51
03:40:01 AM all  1.15  0.06  1.96  1.39  0.00 
95.44
03:50:01 AM all  1.08  0.00  0.43  0.18  0.00 
98.31
04:00:01 AM all  0.99  0.00  0.40  0.18  0.00 
98.43
04:10:01 AM all  0.75  0.03  0.41  0.02  0.00 
98.80
04:20:01 AM all  1.06  0.03  0.50  0.03  0.00 
98.39
04:30:01 AM all  0.93  0.03  0.47  0.01  0.00 
98.56
04:40:01 AM all  0.74  0.03  0.39  0.02  0.00 
98.83
04:50:01 AM all  1.09  0.03  0.51  0.05  0.00 
98.33
05:00:01 AM all  0.91  0.03  0.45  0.02  0.00 
98.60
05:10:01 AM all  0.76  0.03  0.41  0.02  0.00 
98.79
05:20:01 AM all  1.06  0.03  0.49  0.02  0.00 
98.41
05:30:01 AM all  0.93  0.03  0.47  0.02  0.00 
98.55
05:40:01 AM all  0.74  0.02  0.40  0.02  0.00 
98.82
05:50:01 AM all  1.08  0.03  0.52  0.04  0.00 
98.34
06:00:01 AM all  0.96  0.02  0.47  0.03  0.00 
98.52
06:10:01 AM all  0.74  0.02  0.41  0.01  0.00 
98.81
06:20:01 AM all  1.06  0.03  0.49  0.01  0.00 
98.41

06:20:01 AM CPU %user %nice   %system   %iowait%steal 
%idle
06:30:01 AM all  0.93  0.02  0.46  0.01  0.00 
98.58
06:40:01 AM all  0.75  0.03  0.40  0.01  0.00 
98.81
06:50:02 AM all  1.07  0.02  0.50  0.02  0.00 
98.38
07:00:01 AM all  0.96  0.02  0.46  0.01  0.00 
98.54
07:10:02 AM all  0.77  0.02  0.42  0.01  0.00 
98.78
07:20:01 AM all  1.06  0.03  0.48  0.01  0.00 
98.42
07:30:01 AM all  0.94  0.03  0.47  0.01  0.00 
98.56
07:40:01 AM all  0.78  0.03  0.41  0.01  0.00 
98.77
07:50:01 AM all  1.06  0.03  0.50  0.01  0.00 
98.41
08:00:02 AM all  0.96  0.03  0.47  0.01  0.00 
98.53
08:10:01 AM all  0.75  0.02  0.40  0.01  0.00 
98.82
08:20:01 AM all  1.08  0.03  0.49  0.01  0.00 
98.40
08:30:02 AM all 10.48  0.02  2.18  1.58  0.00 
85.73
08:40:02 AM all  9.51  0.02  2.08  1.99  0.00 
86.40
08:50:01 AM all 10.7

[foreman-users] Re: Foreman Proxy is not recognized

2016-07-27 Thread Sai Krishna

>
> Hi Dylan,
>

Appreciate your reply.

# http is disabled by default. To enable, uncomment 'http_port' setting
# https is enabled if certificate, CA certificate, and private key are 
present in locations specifed by
# ssl_certificate, ssl_ca_file, and ssl_private_key correspondingly
# default values for https_port is 8443
:https_port: 8443  

this was the intial setting I have changed it to 8000 but still facing same 
error.

Please advice.
Sai Krishna

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


[foreman-users] Re: Foreman Proxy is not recognized

2016-07-27 Thread Dylan Baars
No you don't want to change the https port, you want to enable http

so you'll have

:https_port: 8443
:http_port: 8000

you then need to restart the proxy (systemctl restart foreman-proxy), make 
sure the local firewall has that port open -

firewall-cmd --permanent --zone=public --add-port="8000/tcp"
firewall-cmd --complete-reload

and then try and connect via the GUI. Note this is just to test that 
foreman can actually contact the proxy, you'll still have to figure out the 
certificates issue (which I went into in quite a lot of detail in the 
ticket, http://projects.theforeman.org/issues/15530)

Dylan

On Thursday, July 28, 2016 at 9:57:40 AM UTC+12, Sai Krishna wrote:
>
> Hi Dylan,
>>
>
> Appreciate your reply.
>
> # http is disabled by default. To enable, uncomment 'http_port' setting
> # https is enabled if certificate, CA certificate, and private key are 
> present in locations specifed by
> # ssl_certificate, ssl_ca_file, and ssl_private_key correspondingly
> # default values for https_port is 8443
> :https_port: 8443  
>
> this was the intial setting I have changed it to 8000 but still facing 
> same error.
>
> Please advice.
> Sai Krishna
>

-- 
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] yum update, package fails "requested range not satisfiable"

2016-07-27 Thread Dylan Baars
Hi,

we have synced (and been syncing) the Jenkins LTS release for RH for months 
now, which is this repo http://pkg.jenkins-ci.org/redhat-stable/
They have added a new RPM, jenkins-2.7.1-1.1.noarch.rpm 
 and 
our local katello has synced that, however now when trying to run a "yum 
update" I get 

jenkins-2.7.1-1.1.noarch.rpm   FAILED
https://wellkatello.niwa.local/pulp/repos/NIWA/Dev-Server/CentOS7_Server/custom/Jenkins/Jenkins_LTS/jenkins-2.7.1-1.1.noarch.rpm:
 
[Errno 14] HTTPS Error 416 - Requested Range Not Satisfiable ] 
 0.0 B/s |0 B  --:--:-- ETA
Trying other mirror.


Error downloading packages:
  jenkins-2.7.1-1.1.noarch: [Errno 256] No more mirrors to try.

I can manually download the file from the pkg.jenkins-ci.org repo and do a 
"yum localinstall" - works fine. What's happening with the above?

Dylan

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


[foreman-users] Katello pulp weird disk usage

2016-07-27 Thread Dylan Baars
We are monitoring disk usage of our katello server using LibreNMS, and 
noticed this today - this is a graph for */var/lib/pulp*


and for the equivalent time period,* /var/lib/mongodb*


Does anyone know why this might be happening? This was directly after a 
reboot of the server

Thanks :-)
Dylan

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


[foreman-users] Re: Katello capsule content sync super slow?

2016-07-27 Thread Dylan Baars
Hi Eric,

I noticed our main katello server was swapping like crazy

[root@wellkatello salt]# free -h

  totalusedfree  shared  buff/cache   
available

Mem:15G 14G457M155M594M
510M

Swap:  2.9G2.9G168K 


and in /var/log/messages getting this (plus a lot more output)


Jul 28 09:51:38 wellkatello.niwa.local kernel: Out of memory: Kill process 
5419 (ruby) score 34 or sacrifice child

Jul 28 09:51:38 wellkatello.niwa.local kernel: Killed process 5419 (ruby) 
total-vm:1952116kB, anon-rss:642768kB, file-rss:0kB

Something seems to be consuming a lot of memory! Since rebooting at 10am 
(~5 hours ago) we've gone from this

[root@wellkatello ~]# free -h

  totalusedfree  shared  buff/cache   
available

Mem:15G4.3G9.7G 46M1.2G 
10G

Swap:  2.9G  0B2.9G

[root@wellkatello ~]# 


which is what was available straight after booting + waiting for 
katello/foreman services to start, to this


[root@wellkatello salt]# free -h

  totalusedfree  shared  buff/cache   
available

Mem:15G 13G650M 61M837M   
 1.0G

Swap:  2.9G855M2.1G

Not sure if this is related to the slow capsule sync? 

-- 
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 inter sync option

2016-07-27 Thread Unix SA
Well that's not the right way, if it allows to export CV version, it should 
allow different CVs, also i dont want to mix my contents in single CVs as 
there are different people manage their own CVs, also why i will include my 
RHEL6.5 and RHEL7 in single content view?

Regards,
DJ

On Wednesday, 27 July 2016 18:36:36 UTC+5:30, Chris Duryee wrote:
>
>
>
> On 07/27/2016 04:38 AM, Unix SA wrote: 
> > 
> > Hello, 
> > 
> > I am following procedure below to sync contents from my upstream 
> satellite 
> > to downstream. 
> > 
> > 
> https://access.redhat.com/documentation/en/red-hat-satellite/6.2-beta/paged/content-management-guide/appendix-c-synchronizing-content-between-satellite-servers
>  
> > 
> > now after updating my organization to URL mention in document, i am able 
> to 
> > sync one CV 
> > 
> > "" 
> > 
> > $ hammer organization update \ 
> > --name "Mega Subsidiary" \ 
> > --redhat-repository-url \ 
> > http://megacorp.com/pub/cdn-latest 
> > 
> > Organization updated 
> > """ 
> > 
> > but for another CV, the URL is different, do i have to update URL 
> everytime when i want to sync different CVs ? or am i missing something? 
> > 
> > 
> > Procedure i followed is:- 
> > 1) set export path to /var/lib/html/pub/export 
> > 2) set selinux permissions 
> > 3) set "immediate" for my RHEL7 kickstart repository 
> > 4) export repository with "hammer repository export --id 2 
> --export-to-iso 
> > 0" 
> > 5) in downstream URL update manifest with URL 
> > "
> https://upstream/pub/export/ORG-Red_Hat_Enterprise_Linux_Server-Red_Hat_Enterprise_Linux_7_Server_Kickstart_x86_64_7_2/ORG/Library/";
>  
>
> > 
> > sync works for "kickstart" , but then how to sync for "rpm repository" 
> now 
> > as URL will be different for it? 
> > 
> > Regards, 
> > DJ 
> > 
>
> Typically, the easiest way to do this is to create a single CV that has 
> all the content you'd like to export. That way if you export multiple 
> items, the CDN url on the downstream server stays the same. 
>

-- 
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 Bonding interfaces using Foreman ver. 1.8.0‏

2016-07-27 Thread nilelinux
Hi All,
 
Please I have installed Foreman version 1.8.0 on CentOS 7.1.  I 
could provision CentOS  to a HP blade server which has 6 NICs but I don't 
know how to configure Bonding on these interfaces. I would like to use 
Forman to configure Bonding as the following:-
 
Eth0 and Eth1 for Bond1 in VLAN 2  with subnet 192.168.2.0/24.
Eth2 and Eth3 for Bond2 in VLAN 3 with subnet 192.168.3.0/24 .
Eth4 and Eth5 for Bond3 in VLAN 4 with subnet 192.168.4.0/24 . 
 
 As I am new in Foreman technology, Could you simplify how to configure the 
Foreman to auto-configure the bonding.
 
 *Best Regards,*

*Mostafa Yasin*

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