Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1464077 - Page remains in loading state when selecting packages from selected CV and from selected environment
Summary: Page remains in loading state when selecting packages from selected CV and fr...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.2.10
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-22 11:48 UTC by Nikhil Kathole
Modified: 2019-09-26 18:40 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-13 21:09:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
exception raised in production.log (22.28 KB, text/plain)
2017-06-22 11:48 UTC, Nikhil Kathole
no flags Details
screenshot of UI (63.27 KB, image/png)
2017-06-22 11:50 UTC, Nikhil Kathole
no flags Details

Description Nikhil Kathole 2017-06-22 11:48:57 UTC
Created attachment 1290661 [details]
exception raised in production.log

Description of problem:
I was trying to explore UI, created two environments, add package filter and promoted to new version. I was trying to see filtered packages by content view for promoted environment.The UI goes loading and raised error in production.log.



2017-06-22 05:31:41 0c3015b5 [app] [I] Processing by Katello::Api::V2::PackagesController#index as JSON
2017-06-22 05:31:41 0c3015b5 [app] [I]   Parameters: {"content_view_version_id"=>"3", "environment_id"=>"4", "library"=>"true", "page"=>"1", "search"=>"", "api_version"=>"v2"}
2017-06-22 05:31:41 0c3015b5 [app] [E] PG::Error: ERROR:  bind message supplies 2 parameters, but prepared statement "a151" requires 1
 | 
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:834:in `get_last_result'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:834:in `block in exec_cache'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract_adapter.rb:373:in `block in log'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activesupport-4.1.5/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract_adapter.rb:367:in `log'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:831:in `exec_cache'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql/database_statements.rb:138:in `exec_query'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/postgresql_adapter.rb:954:in `select'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/database_statements.rb:24:in `select_all'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/query_cache.rb:68:in `block in select_all'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/query_cache.rb:83:in `cache_sql'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/connection_adapters/abstract/query_cache.rb:68:in `select_all'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation/calculations.rb:262:in `execute_simple_calculation'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation/calculations.rb:224:in `perform_calculation'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation/calculations.rb:119:in `calculate'
 | /opt/rh/rh-ror41/root/usr/share/gems/gems/activerecord-4.1.5/lib/active_record/relation/calculations.rb:34:in `count'



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

How reproducible:
always

Steps to Reproduce:
1.create an environment 
2.create content views
3.add package filter of type include and promote to new version
4.go to lifecycle environment >> click promoted environment >> packages >> filter by content view.


Actual results:
UI remains in loading state and production.log is filled w/ above exception.

Expected results:
Page should load without exception

Additional info:

Comment 1 Nikhil Kathole 2017-06-22 11:50:11 UTC
Created attachment 1290662 [details]
screenshot of UI

Comment 3 Mike McCune 2017-06-30 17:48:30 UTC
Reproduced this on 6.2.10 as described in the bug.

Comment 6 Mike McCune 2017-09-13 21:09:30 UTC
We are going to include this as fixed in 6.3 so closing it out as CLOSED:NEXTRELEASE


Note You need to log in before you can comment on or make changes to this bug.