Bug 1108190

Summary:	Increase pool size for Sequel
Product:	Red Hat Satellite	Reporter:	Og Maciel <omaciel>
Component:	Installation	Assignee:	Ivan Necas <inecas>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Corey Welton <cwelton>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.0.3	CC:	bbuckingham, cwelton, jmontleo
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/6193
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-02 14:06:34 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Og Maciel 2014-06-11 14:32:07 UTC

Description of problem:

I created 3 different content views, each one containing the following RHEL products:

1. RHEL 5Server RPMs x86_64/i386 + katello-agent + motd puppet module
2. RHEL 6Server RPMs x86_64/i386 + SCL 6Server RPMs x86_64 + katello-agent + motd puppet module
3. RHEL 7Server RPMs x86_64 SCL 7Server RPMs x86_64 + katello-agent + motd puppet module

After publishing each one of them via the web ui, I immediately promoted all 3 of them at the same time.

Two of the promotions completed but one of them stopped responding and never completed.

Looking though logs the following stacktrace was found:

Sequel::PoolTimeout (Sequel::PoolTimeout)
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/connection_pool/threaded.rb:100:in `hold'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/database/connecting.rb:236:in `synchronize'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/adapters/postgres.rb:719:in `literal_string_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:88:in `literal_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:478:in `complex_expression_sql_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/adapters/shared/postgres.rb:1089:in `complex_expression_sql_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/sql.rb:94:in `to_s_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:1100:in `literal_expression_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:95:in `literal_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:486:in `block in complex_expression_sql_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:484:in `each'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:484:in `complex_expression_sql_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/adapters/shared/postgres.rb:1089:in `complex_expression_sql_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/sql.rb:94:in `to_s_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:1100:in `literal_expression_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:95:in `literal_append'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:1332:in `select_where_sql'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:848:in `block in clause_sql'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:848:in `each'
/opt/rh/ruby193/root/usr/share/gems/gems/sequel-3.45.0/lib/sequel/dataset/sql.rb:848:in `clause_sql'


On IRC it has been mentioned that since we have increased the pool size for active record, that we should also do the same for Sequel.


Version-Release number of selected component (if applicable):

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.7-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.7-1.el6_5.noarch
* candlepin-tomcat6-0.9.7-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.6.0.14-1.el6sat.noarch
* foreman-compute-1.6.0.14-1.el6sat.noarch
* foreman-gce-1.6.0.14-1.el6sat.noarch
* foreman-libvirt-1.6.0.14-1.el6sat.noarch
* foreman-ovirt-1.6.0.14-1.el6sat.noarch
* foreman-postgresql-1.6.0.14-1.el6sat.noarch
* foreman-proxy-1.6.0.6-1.el6sat.noarch
* foreman-selinux-1.6.0-4.el6sat.noarch
* foreman-vmware-1.6.0.14-1.el6sat.noarch
* katello-1.5.0-25.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.5-1.el6sat.noarch
* katello-installer-0.0.45-1.el6sat.noarch
* openldap-2.4.23-32.el6_4.1.x86_64
* pulp-katello-0.3-3.el6sat.noarch
* pulp-nodes-common-2.4.0-0.18.beta.el6sat.noarch
* pulp-nodes-parent-2.4.0-0.18.beta.el6sat.noarch
* pulp-puppet-plugins-2.4.0-0.18.beta.el6sat.noarch
* pulp-puppet-tools-2.4.0-0.18.beta.el6sat.noarch
* pulp-rpm-plugins-2.4.0-0.18.beta.el6sat.noarch
* pulp-selinux-2.4.0-0.18.beta.el6sat.noarch
* pulp-server-2.4.0-0.18.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch
* rubygem-hammer_cli-0.1.1-3.el6sat.noarch
* rubygem-hammer_cli_foreman-0.1.1-8.el6sat.noarch
* rubygem-hammer_cli_foreman_tasks-0.0.3-2.el6sat.noarch
* rubygem-hammer_cli_katello-0.0.4-5.el6sat.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Ivan Necas 2014-06-12 14:08:37 UTC

The issue should be fixed as part of http://projects.theforeman.org/issues/6193

Comment 3 Ivan Necas 2014-06-13 14:17:58 UTC

Fixed in foreman-tasks-0.6.1 with dynflow-0.7.1

Comment 5 Corey Welton 2014-06-19 14:05:26 UTC

I am marking this verified, because I have seen the change made in the code. As such, the resolution itself ("Increase pool size") has been completed.  If the symptom continues to arise, we can re-open or open a new bz for further investigation.

VERIFIED in Satellite-6.0.3-RHEL-6-20140618.0

Comment 6 Bryan Kearney 2014-07-02 14:06:34 UTC

This was delivered with 6.0.3, which is the Satellite 6 Beta.