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.
DescriptionGarik Khachikyan
2012-05-29 13:52:29 UTC
Description of problem:
as there is no feature request so far for making such a script for the DB reset let's drop katello-reset-dbs from the CFSE bits but leave it definitely for Katello.
For me the script itself is really fragile and could get easily broken and other side effects (or not cleaned content) could appear.
Version-Release number of selected component (if applicable):
recent gituhb + CFSE repos
How reproducible:
always
Steps to Reproduce:
1.
2.
3.
Actual results:
katello-reset-dbs is in CFSE repo
Expected results:
remove it from CFSE packaging but leave in Katello
Additional info:
sorry, this is useful for demo situations and users who wish to go back to the beginning state.
we are going to keep this script available. It is very clear what it does even if it is highly destructive it has its use for resetting your data to the start of the install.