Description of problem: Deleting organization does not delete its custom channel's packages Version-Release number of selected component (if applicable): spacewalk-java-2.3.8-160.el6sat.noarch satellite-schema-5.7.0.32-1.el6sat.noarch spacewalk-backend-2.3.3-52.el6sat.noarch How reproducible: always Steps to Reproduce: 1. Create organization jhutar, no entitlements required, note down org ID 2. Login as that organization admin 3. Create channel jhutar-delme with architecture matching to the package you are going to push to it in a while 4. Push some package into it # rhnpush -u <user> -p <pass> -c jhutar-delme vim-go-1.8-3.el7.x86_64.rpm 5. Verify that package landed: # find /var/satellite/redhat/$ORG_ID/ -type f 6. Logout and login as satellite admin 7. Delete that organization Actual results: After deleting organization package is left behind. Have not tried, but `spacewalk-data-fsck` reports it. Expected results: Package should be removed from the disk
Also on 5.8.0: spacewalk-java-2.5.14-89.el6sat.noarch satellite-schema-5.8.0.31-1.el6sat.noarch spacewalk-backend-2.5.3-143.el6sat.noarch
I'd say this is expected.
We have re-reviewed this bug, as part of an ongoing effort to improve Satellite/Proxy feature and bug updates, review and backlog. This is a low priority bug and has no currently open customer cases. While this bug may still valid, we do not see it being implemented prior to the EOL of the Satellite 5.x product. As such, this is being CLOSED DEFERRED. Closing now to help set customer expectations as early as possible. You are welcome to re-open this bug if needed.