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 1342577 - Running satellite-installer --reset fails
Summary: Running satellite-installer --reset fails
Keywords:
Status: CLOSED DUPLICATE of bug 1321951
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: Unspecified
Assignee: Stephen Benjamin
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-03 14:51 UTC by Kedar Bidarkar
Modified: 2019-04-01 20:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-07 12:19:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Kedar Bidarkar 2016-06-03 14:51:37 UTC 
Description of problem:

Currently running "satellite-installer --reset" fails with the below error.

[DEBUG 2016-06-03 10:36:48 main] Hook /usr/share/katello-installer-base/hooks/post/10-post_install.rb returned nil
[DEBUG 2016-06-03 10:36:48 main] Hook /usr/share/katello-installer-base/hooks/post/30-upgrade.rb returned nil
[ INFO 2016-06-03 10:36:48 main] All hooks in group post finished
[DEBUG 2016-06-03 10:36:48 main] Exit with status code: 6 (signal was 6)
[ERROR 2016-06-03 10:36:48 main] Errors encountered during run:
[ERROR 2016-06-03 10:36:48 main]  /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
[ERROR 2016-06-03 10:36:48 main]  /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]


Version-Release number of selected component (if applicable):
sat62-snap(GA)-114.1

How reproducible:


Steps to Reproduce:
1. Run "satellite-installer --reset"
2.
3.

Actual results:
/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
 /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]


Expected results:

Running "satellite-installer --reset" succeeds.

Additional info:
Comment 2 Roman Plevka 2016-06-03 16:05:04 UTC 
WORKAROUND:

move out the following file /opt/theforeman/tfm/root/usr/share/gems/gems/katello-3.0.0.41/db/seeds.d/108-ensure_sync_notification.rb

The reset (db:seed) will succeed but obviously the `ensure_sync_notification` step will be skipped
Comment 4 Brad Buckingham 2016-06-06 15:52:31 UTC 
This may be a duplicate of bug 1321951; however, assigning to Stephen to confirm, in case the root cause is different.
Comment 6 Stephen Benjamin 2016-06-07 12:19:51 UTC 
Yes, looks like the same issue.

*** This bug has been marked as a duplicate of bug 1321951 ***
Note You need to log in before you can comment on or make changes to this bug.