Bug 1309486

Summary: Got an error attempting to delete a product
Product: Red Hat Satellite Reporter: mharris <mharris>
Component: RepositoriesAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: UnspecifiedCC: bbuckingham, chrobert, mharris, zhunting
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-31 21:40:37 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:
Attachments:
Description Flags
Output of foreman-debug none

Description mharris 2016-02-17 23:42:59 UTC
Created attachment 1128059 [details]
Output of foreman-debug

Description of problem:

We created a temporary product, and followed that by creating a temporary repository, as I was explaining the use of each to the customer, specifically for the purpose of using puppet modules.

Version-Release number of selected component (if applicable):
satellite 6.1.7

How reproducible:
Unable to test in mass as customer is attempting to setup new satellite server.

Steps to Reproduce:
1. Create new product
2. Create a puppet repo (I was syncing to localhost: file:///modules/)
3. Delete repo (after a full and successful sync)
4. Delete Product (Not assigned to any content views)

Actual results:
Unable to delete product, as /etc/puppet/environments/K{whatever is specific to this product} was already deleted, which it WAS.

Expected results:
Remove the product from Foreman.

Additional info:
Ended up manually deleting row from database, using katello-rake

Comment 1 Bryan Kearney 2016-07-26 19:04:35 UTC
Moving 6.2 bugs out to sat-backlog.

Comment 2 Brad Buckingham 2016-08-31 21:40:37 UTC
I was unable to reproduce the behavior described with Satellite 6.2.1.  I am going to close the bugzilla; however, please re-open if you see it after upgrading.