Bug 1637644

Summary: --reset does not reset new MongoDB 3.4
Product: Red Hat Satellite Reporter: Chris Roberts <chrobert>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4Keywords: Regression, Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-10-10 15:29:20 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:

Description Chris Roberts 2018-10-09 16:13:09 UTC 
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
Comment 3 Brad Buckingham 2018-10-10 15:29:20 UTC 

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