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.
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
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.
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