[foreman-users] Foreman yum dependency after a Katello 3.4 -> 3.5 upgrade

2017-12-11 Thread Tony Coffman 
I did an update from Katello 3.4 -> 3.5 yesterday and ran into what looks 
like it might be a packaging issue.

The original symptom was that remote execution was broken. It took me a 
little while but then I realized that I still had the 1.15 remote execution 
packages installed instead of the 1.16 equivalents.

[root@rich-form-01-pv yum.repos.d]# rpm -qa | grep fm1_15
tfm-rubygem-dynflow-0.8.30-1.fm1_15.el7.noarch
tfm-rubygem-foreman_remote_execution-1.3.7-1.fm1_15.el7.noarch
tfm-rubygem-foreman_remote_execution_core-1.0.6-1.fm1_15.el7.noarch
tfm-rubygem-concurrent-ruby-edge-0.2.3-1.fm1_15.el7.noarch


I check and I did have the correct 1.16 repos defined but yum update showed 
everything as up to date.  When I tried to manually install the 1.16 
version, I got this

[root@rich-form-01-pv ~]# yum install 
https://yum.theforeman.org/plugins/1.16/el7/x86_64/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm
Loaded plugins: fastestmirror
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm  
  | 434 kB  00:00:00
Examining 
/var/tmp/yum-root-5i1ybr/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm:
 
tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch
/var/tmp/yum-root-5i1ybr/tfm-rubygem-foreman_remote_execution-1.3.3-1.fm1_16.el7.noarch.rpm:
 
does not update installed package.
Error: Nothing to do


So I ended up removing my remote 1.15 remote execution package and 
installing the 1.16 equivalents.  That got remote execution working but 
then I ran an orphan check as a sanity check and found some additional 
packages that don't seem to be right.

[root@rich-form-01-pv yum.repos.d]# package-cleanup --orphans
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.riverfrontnetworks.com
 * epel: mirror.steadfast.net
 * extras: mirror.beyondhosting.net
 * updates: mirror.rackspace.com
java-client-1.0-1.noarch
katello-client-bootstrap-1.4.0-2.el7.noarch
katello-default-ca-1.0-1.noarch
katello-server-ca-1.0-1.noarch
kernel-3.10.0-514.el7.x86_64
kernel-3.10.0-514.16.1.el7.x86_64
kernel-3.10.0-514.21.1.el7.x86_64
kernel-3.10.0-514.26.2.el7.x86_64
pulp-client-1.0-1.noarch
python-nectar-1.5.4-1.el7.noarch
rich-form-01-pv.ipa.snapbs.com-apache-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-foreman-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-foreman-proxy-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-foreman-proxy-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-puppet-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-broker-1.0-2.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-client-cert-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-router-client-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-qpid-router-server-1.0-1.noarch
rich-form-01-pv.ipa.snapbs.com-tomcat-1.0-1.noarch
tfm-rubygem-concurrent-ruby-edge-0.2.3-1.fm1_15.el7.noarch
tfm-rubygem-dynflow-0.8.30-1.fm1_15.el7.noarch
tfm-rubygem-net-ssh-4.0.1-2.el7.noarch
tfm-rubygem-safemode-1.3.2-1.el7.noarch
tfm-rubygem-scoped_search-4.1.2-1.el7.noarch

I don't understand the last 5 packages in this list.  Some of these 
definitely have 1.16 equivalents but it seems like some kind of dependency 
isn't right as I can't upgrade or remove and reinstall without blowing up a 
lot of packages.  I'm pretty sure when I did the 3.3 -> 3.4 upgrade the 
orphans list didn't have any Foreman or Katello packages (except certs).

Any ideas what may be going on with those packages during an upgrade?

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 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/Katello not displaying installable errata or packages in Content Hosts view

2017-08-30 Thread Tony Coffman 
I had reasonable success using this one-liner fix from the pulp team when I 
was stuck on 3.4.0.

https://github.com/pulp/pulp/pull/3047/

I had to force recalc errata applicability for some hosts to get them to 
show applicable packages after applying this fix, but once that was done, 
this kept the applicable packages view working until I could upgrade to 
3.4.3+ (where this simply works).

I would definitely update to the latest as soon as you can - there are tons 
of bugs fixed in current release including this.

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 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: PLP0034: The distributor indicated a failed response when publishing repository

2017-08-22 Thread Tony Coffman 
Is it possible we have a regression on this issue? I know it was fixed back 
in September 2016 but I ran into what looks like the same issue with 
Katello 3.4.4 today.

I pulled in a new version of Puppet stdlib a week or two ago when I 
published a new version of some Content Views.

Today, I promoted those CVs to an environment that needed to be synched to 
a capsule and I got this

PLP0034: The distributor 
3-C7-Staging-puppet-61a82fb3-e03e-4866-8903-b671fe1bd9d7 indicated a failed 
response when publishing repository 
3-C7-Staging-puppet-61a82fb3-e03e-4866-8903-b671fe1bd9d7.


The detailed error info from the capsule synch task looks like a duplicate 
unit name again. 

error:
code: PLP0034
data:
  distributor_id: 3-C7-Staging-puppet-61a82fb3-e03e-4866-8903-b671fe1bd9d7
  repo_id: 3-C7-Staging-puppet-61a82fb3-e03e-4866-8903-b671fe1bd9d7
  summary: duplicate unit names
description: The distributor 
3-C7-Staging-puppet-61a82fb3-e03e-4866-8903-b671fe1bd9d7
  indicated a failed response when publishing repository 
3-C7-Staging-puppet-61a82fb3-e03e-4866-8903-b671fe1bd9d7.
sub_errors: []

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

[foreman-users] Re: Host collections actions

2017-07-31 Thread Tony Coffman 
I reported this issue also.  Unfortunately - the fix didn't make it into 
Katello 3.4.3 but it looks like it should be in 3.4.4 when it releases.

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

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

2017-06-28 Thread Tony Coffman 
FYI - I opened an issue last week about this.

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






On Tuesday, June 27, 2017 at 5:40:00 PM UTC-4, Eric Helms wrote:
>
> I'll look into this discrepancy. This is likely due to the migration we 
> had to make and rebuild our RPM build server. Stay tuned.
>
> On Tue, Jun 27, 2017 at 4:53 PM, 'Jason B. Nance' via Foreman users <
> forema...@googlegroups.com > wrote:
>
>> 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: *matthew...@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 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 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.
>>
>
>
>
> -- 
> Eric D. Helms
> Red Hat Engineering
>

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

[foreman-users] Too many open files during a patching operation

2017-04-24 Thread Tony Coffman 
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 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] Runner error during Ansible playbook run from WebUI

2017-01-27 Thread Tony Coffman 
Thank you.  Both the workaround and the PR are working great for me.

On Friday, January 27, 2017 at 8:02:51 AM UTC-5, Daniel Lobato wrote:
>
> On 01/26, Tony Coffman wrote: 
> > I'm testing Katello 3.3 RC1 and attempting to integrate foreman_ansible, 
> > dynamic inventory, and the ansible proxy into my test scenario. 
>
>
> This looks like http://projects.theforeman.org/issues/18278, try 
> changing the verbosity level to 1. 
>
> I will release a patch for this ASAP (one that verifies the settings are 
> correct and allows to disable verbosity) 
>
> > 
> > I've imported my ansible roles and assigned parameters in Foreman and 
> from 
> > the command line all is well. 
> > 
> > I've run into a roadblock when I try to run the playbook in the WebUI. 
> > 
> > The error is Runner error: TypeError - no implicit conversion of nil 
> into 
> > String 
> > 
> > Here's the trace from the smart_proxy_dynflow_core.log.  Any help would 
> be 
> > greatly appreciated it. 
> > 
> > [2017-01-26 13:41:23.707 #2830] ERROR -- dynflow: error while 
> dispatching 
> > request to runner 285ec4a1-2bc8-4a98-bd96-7fad0a30d3de:TypeError no 
> > implicit conversion of nil into String: 
> > 
>  
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/command_runner.rb:8:in
>  
>
> > `spawn' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/command_runner.rb:8:in
>  
>
> > `initialize_command' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible_core-1.0.0/lib/foreman_ansible_core/playbook_runner.rb:21:in
>  
>
> > `block in start' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible_core-1.0.0/lib/foreman_ansible_core/playbook_runner.rb:20:in
>  
>
> > `chdir' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible_core-1.0.0/lib/foreman_ansible_core/playbook_runner.rb:20:in
>  
>
> > `start' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/dispatcher.rb:29:in
>  
>
> > `start_runner' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.17/lib/dynflow/actor.rb:6:in
>  
>
> > `on_message' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/context.rb:46:in
>  
>
> > `on_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/dispatcher.rb:22:in
>  
>
> > `on_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/executes_context.rb:7:in
>  
>
> > `on_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
>  
>
> > `pass' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.17/lib/dynflow/actor.rb:26:in
>  
>
> > `on_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
>  
>
> > `pass' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/awaits.rb:15:in
>  
>
> > `on_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
>  
>
> > `pass' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/sets_results.rb:14:in
>  
>
> > `on_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
>  
>
> > `pass' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:38:in
>  
>
> > `process_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:31:in
>  
>
> > `process_envelopes?' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:20:in
>  
>
> > `on_envelope' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
>  
>
> > `pass' 
> > 
> /opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/be

[foreman-users] Runner error during Ansible playbook run from WebUI

2017-01-26 Thread Tony Coffman 
I'm testing Katello 3.3 RC1 and attempting to integrate foreman_ansible, 
dynamic inventory, and the ansible proxy into my test scenario.

I've imported my ansible roles and assigned parameters in Foreman and from 
the command line all is well.

I've run into a roadblock when I try to run the playbook in the WebUI.

The error is Runner error: TypeError - no implicit conversion of nil into 
String

Here's the trace from the smart_proxy_dynflow_core.log.  Any help would be 
greatly appreciated it.

[2017-01-26 13:41:23.707 #2830] ERROR -- dynflow: error while dispatching 
request to runner 285ec4a1-2bc8-4a98-bd96-7fad0a30d3de:TypeError no 
implicit conversion of nil into String:
 
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/command_runner.rb:8:in
 
`spawn'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/command_runner.rb:8:in
 
`initialize_command'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible_core-1.0.0/lib/foreman_ansible_core/playbook_runner.rb:21:in
 
`block in start'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible_core-1.0.0/lib/foreman_ansible_core/playbook_runner.rb:20:in
 
`chdir'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman_ansible_core-1.0.0/lib/foreman_ansible_core/playbook_runner.rb:20:in
 
`start'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/dispatcher.rb:29:in
 
`start_runner'
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.17/lib/dynflow/actor.rb:6:in
 
`on_message'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/context.rb:46:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-core-0.1.1/lib/foreman_tasks_core/runner/dispatcher.rb:22:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/executes_context.rb:7:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
 
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/dynflow-0.8.17/lib/dynflow/actor.rb:26:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
 
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/awaits.rb:15:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
 
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/sets_results.rb:14:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
 
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:38:in
 
`process_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:31:in
 
`process_envelopes?'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/buffer.rb:20:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
 
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/termination.rb:55:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
 
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/removes_child.rb:10:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/abstract.rb:25:in
 
`pass'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/behaviour/sets_results.rb:14:in
 
`on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:161:in
 
`process_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:95:in
 
`block in on_envelope'
/opt/theforeman/tfm/root/usr/share/gems/gems/concurrent-ruby-edge-0.2.0/lib/concurrent/actor/core.rb:118:in
 
`block (2 levels) in schedule_execution'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
 
`block in synchronize'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
 
`synchronize'
/opt/rh/sclo-ror42/root/usr/share/gems/gems/concurrent-ruby-1.0.0/lib/concurrent/synchronization/mri_lockable_object.rb:38:in
 
`synchronize'

[foreman-users] Re: Katello Upgrade 2.4 -> 3.0 stuck at migrate_pulp

2016-07-02 Thread Tony Coffman 
198GB - about 20 content views.  2.4 -> 3.0 upgrade ran in just under 4 
hours.

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