Bug 1473532 - deleting organization does not delete its custom channel's packages
deleting organization does not delete its custom channel's packages
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Server (Show other bugs)
Unspecified Unspecified
unspecified Severity low
: ---
: ---
Assigned To: Tomáš Kašpárek
Red Hat Satellite QA List
Depends On:
  Show dependency treegraph
Reported: 2017-07-21 02:05 EDT by Jan Hutař
Modified: 2018-04-09 11:34 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2018-04-09 11:34:47 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jan Hutař 2017-07-21 02:05:29 EDT
Description of problem:
Deleting organization does not delete its custom channel's packages

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

How reproducible:

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
Comment 1 Jan Hutař 2017-07-21 02:06:35 EDT
Also on 5.8.0:

Comment 2 Tomas Lestach 2017-07-21 10:30:05 EDT
I'd say this is expected.
Comment 4 Tomas Lestach 2018-04-09 11:34:47 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.