Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1401859

Summary: Satellite installer failed with error 'usr/sbin/foreman-rake db:seed returned 1' and proxy error
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: high    
Version: 6.3.0CC: bbuckingham, jyejare, kbidarka, stbenjam
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-09 14:36:59 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:

Comment 3 Jitendra Yejare 2016-12-06 10:56:20 UTC 
Even if the errors triggered due to low memory, Customer upgrading from 6.0/6.1 having < 8 GB memory will be in real trouble here. Customer will face these errors while running installer command for upgrade.
Comment 4 Stephen Benjamin 2016-12-06 16:12:33 UTC 
The system has almost 8GB of memory, we're fixing to check to be a little more flexible.  I don't think this is memory related.

It looks like perhaps something went wrong with cert setup. Seed failed because of this:

[ WARN 2016-12-06 03:40:44 main]  /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: There was an issue with the backend service candlepin: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed


Do you still have the beaker box? Is it happening on every install of this snap?
Comment 5 Jitendra Yejare 2016-12-09 11:12:03 UTC 
Hi BK,

Yes, I do have the beaker box, I can share the details in PM.

I didnt try installing this again and this was the first and last setup I tries this. :)
Comment 6 Stephen Benjamin 2017-01-09 14:36:59 UTC 
Hi - sorry, going to close it for now.  I don't see much in the logs to indicate what caused the certs to fail, and we've had a few snaps since the original bug report that were working.

If you end up with more info or still run into the problem let me know and I can try to take a deeper look.