+++ This bug was initially created as a clone of Bug #517146 +++ Description of problem: If a user deletes an org from their Satellite, the Kickstart profiles that they have created will not be deleted from Cobbler, and can be viewed from another org. Version-Release number of selected component (if applicable): 530, Stage build How reproducible: Always Steps to Reproduce: 1. Create an org and grant it provisioning entitlements 2. Create several kickstart profiles under this org 3. Delete this org 4. Create another org and grant it provisioning entitlements 5. Login as the orgadmin for this new org Actual results: Old org's profiles can be viewed from the SDC of any Provisioning-entitled system Expected results: Old org's profiles cannot be viewed from the SDC of any Provisioning-entitled system Additional info: --- Additional comment from Clifford Perry on 2009-08-12 15:58:51 EDT --- punted for now - bad bug and we *need* to fix post 530 GA. --- Additional comment from Tony Fu on 2010-06-30 00:30:16 EDT --- User ssalevan's account has been closed --- Additional comment from Tony Fu on 2010-06-30 00:32:28 EDT --- User ssalevan's account has been closed --- Additional comment from Tony Fu on 2010-06-30 00:41:42 EDT --- User ssalevan's account has been closed --- Additional comment from Tasos Papaioannou on 2010-10-21 09:49:53 EDT --- Appears to be due to the fact that an orphaned cfg file is left behind after deletion of the first org's kickstart profile: # ll /var/lib/rhn/kickstarts/wizard [...] -rw-r--r-- 1 tomcat tomcat 8081 Oct 21 09:01 bz-517146-ks--43.cfg ^ cfg file for ks profile from deleted org #43. In the new org, this cfg file shows up as a non-Satellite-managed kickstart profile. The associated ks profile data in the database has been deleted; it's just the cfg file that needs to be deleted. --- Additional comment from Stephen Herr on 2012-11-21 14:29:54 EST --- *** Bug 837796 has been marked as a duplicate of this bug. *** --- Additional comment from Stephen Herr on 2012-11-26 13:45:17 EST --- No, this is actually due to the fact that the Cobbler profiles are not removed when the Org is deleted. $ cobbler profile list
Committed to Spacewalk master: 4532f5ab0389132ce041938ecbe02273cd6e8c56
I mean we need a similar routine for the API.
(In reply to comment #2) > I mean we need a similar routine for the API. You are right, I should put this functionality at the OrgFactory level so it is called no matter where the request originates from. I have reverted 4532f5ab0389132ce041938ecbe02273cd6e8c56 and committed a new fix to Spacewalk master: 04e048722f3c03209d77506be33e432e99970883
Marking bug as ON_QA since tonight's build of Spacewalk nightly is a release candidate for Spacewalk 1.9.
Spacewalk 1.9 has been released. https://fedorahosted.org/spacewalk/wiki/ReleaseNotes19