Bug 1323687

Summary: 500 Internal Server Error on Enabling RH repositories
Product: Red Hat Satellite Reporter: Roman Plevka <rplevka>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Roman Plevka <rplevka>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, mmccune
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-04 15:09:24 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:
Attachments:
Description Flags
/var/log/foreman/production.log none

Description Roman Plevka 2016-04-04 12:34:04 UTC 
Description of problem:
Trying to enable a rhel repo results in error 500.
(see whole traceback from production.log in attachments) 

Version-Release number of selected component (if applicable):
# rpm -qa | grep satellite
satellite-6.2.0-6.1.beta.el6sat.noarch

How reproducible:
everytime on snap 6.1

Steps to Reproduce:
1. upload a manifest
2. try to enable a rhel repo from Red Hat Repositories

Actual results:
Actions::Katello::RepositorySet::EnableRepository task results in:
500 Internal Server Error

Expected results:
repo enabled, and RH product created

Additional info:
Comment 1 Roman Plevka 2016-04-04 12:40:33 UTC 
Created attachment 1143349 [details]
/var/log/foreman/production.log
Comment 3 Roman Plevka 2016-04-04 14:33:17 UTC 
Note, this only happens on el6 version. el7 seems to be fine
Comment 4 Mike McCune 2016-04-04 15:09:24 UTC 
This is caused by 1321644, dead pulp_workers and celery processes. Closing as a dupe

*** This bug has been marked as a duplicate of bug 1321644 ***
Comment 5 Brad Buckingham 2016-04-04 15:36:22 UTC 
Updating the 'duplicate' that this bug is marked against.  The issue here appears to be related to the same as bug 1323509.

*** This bug has been marked as a duplicate of bug 1323509 ***