Description of problem: When we provision a system using the schedule provision page or thru bare metal, a system record is created in cobbler associating the system to a particular profile. These system records never get deleted even if we delete the system in satellite. Satellite needs to clean up the mess it created for we might end up with too many wasted/orphaned system records lingering around in cobbler. Version-Release number of selected component (if applicable): sat 530 How reproducible: always Steps to Reproduce: 1. Register a system with Provisioning entitielment. 2. On the provisioning schedule page, schedule a KS or click " create cobbler system record" 3. Delete the system. 4. Ssh to the satellite host and type cobbler system list Actual results: we still see the system profile name in the system list implying an orphaned system record Expected results: No system record Additional info: Note we reuse system records if you reregistered the same system over and over again.. So the deletion logic has to be vary of this, as in if you had 1 system re registered 5 times it'd be associated to the same system record. WHen you delete the duplicate ones we'd have to ensure that we are not deleting the wrong system record..
This was fixed in upstream within the Bug 509563.
This issue is resolved with the release of RHN Satellite 5.5. As of September 20th 2012, RHN Satellite 5.5 has been generally available. Release Notes and other 5.5 documentation can be found here: https://access.redhat.com/knowledge/docs/Red_Hat_Network_Satellite/ The associated Errata for the 5.5 release are: 5.5 Satellite GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1296.html 5.5 Upgrade Errata - http://rhn.redhat.com/errata/RHEA-2012-1298.html 5.5 RHN Proxy GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1297.html 5.5 RHN Tools GA Errata - http://rhn.redhat.com/errata/RHEA-2012-1299.html Regards, Clifford - Engineering Manager, Satellite