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.

Description of problem:
--reset is not clearing mongo correctly, so when the user runs reset and tries to create a new product/repo we get an error in the webui/api from Katello because that already exists.

Version-Release number of selected component (if applicable):
Katello 3.7
Mongo 3.4
Satellite 6.4

How reproducible:


Steps to Reproduce:
1. Install 6.4
2. Add a product and repo
3. run --reset as installer flag and then try to make a product/repo with the same name.

Actual results:
Error saying a repo with that name already exists, nothing in katello db but looking at mongo [db.repos.find()] we see the repo is still there

Expected results:
For it to clear the db so I can make a new product/repo with the same name

Additional info:

Working on fixing this and will have a PR up soon, talked to mmccune and he suggests we target 6.4.Z

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