Bug 1782790

Summary: Plugins leave behind empty directories when upgraded
Product: Red Hat Satellite Reporter: Stefan Nemeth <snemeth>
Component: InstallationAssignee: Suraj Patil <supatil>
Status: NEW --- QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6.0CC: apatel, aupadhye, bkearney, egolov, ehelms, kgaikwad, saydas
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Stefan Nemeth 2019-12-12 10:48:27 UTC 
Description of problem:

In /opt/theforeman/tfm/root/usr/share/gems/gems

empty folders of older versions of gems are left after upgrades. 
In some cases it may happen, that older rubygem is not cleaned up and may cause issues. 

Add step for foreman-maintain, to "health check" this directory and ask user if he wants to cleanup old unused gems or not. (yes/no input)

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


How reproducible:

100%

Steps to Reproduce:
1. Install satellite 6.5
2. upgrade to 6.6 
3. ls /opt/theforeman/tfm/root/usr/share/gems/gems

Actual results:

Old directories are left and not deleted. 

Expected results:

Implement check, which will identify folders/rubygems which are not owned by any package.


Additional info:

To identify such gems

#cd /opt/theforeman/tfm/root/usr/share/gems/gems
#ls | xargs rpm -qf * | grep -i 'not owned by any package'
Comment 3 Suraj Patil 2020-05-12 11:48:25 UTC 
Created redmine issue https://projects.theforeman.org/issues/29739 from this bug
Comment 6 Eric Helms 2021-11-17 15:15:55 UTC 
Moving to packaging and updating the request to address this within packaging so this gets handled properly.
Comment 7 Evgeni Golov 2021-11-17 15:17:35 UTC 
Example from a 6.8 machine (but the problem is not version specific):

# ls -R foreman_templates-7.0.7/public/
foreman_templates-7.0.7/public/:
apipie-cache  assets  webpack

foreman_templates-7.0.7/public/apipie-cache:
plugin

foreman_templates-7.0.7/public/apipie-cache/plugin:

foreman_templates-7.0.7/public/assets:

foreman_templates-7.0.7/public/webpack:

# ls -R katello-3.14.0.32/public/
katello-3.14.0.32/public/:
apipie-cache  assets  webpack

katello-3.14.0.32/public/apipie-cache:
plugin

katello-3.14.0.32/public/apipie-cache/plugin:

katello-3.14.0.32/public/assets:

katello-3.14.0.32/public/webpack:
Comment 8 Bryan Kearney 2022-05-12 08:01:23 UTC 
Upstream bug assigned to supatil
Comment 9 Bryan Kearney 2022-05-12 08:01:26 UTC 
Upstream bug assigned to supatil
Comment 10 Bryan Kearney 2022-05-19 16:01:15 UTC 
Upstream bug assigned to supatil
Comment 11 Bryan Kearney 2022-05-19 16:01:18 UTC 
Upstream bug assigned to supatil
Comment 12 Bryan Kearney 2023-10-05 16:00:45 UTC 
Upstream bug assigned to supatil
Comment 14 Bryan Kearney 2024-03-28 16:01:46 UTC 
Upstream bug assigned to supatil