Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1315894 - katello-remove does not remove many things
Summary: katello-remove does not remove many things
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installation
Version: 6.1.7
Hardware: x86_64
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: Chris Roberts
QA Contact: Bruno Rocha
URL: http://projects.theforeman.org/issues...
Whiteboard:
: 1320234 1339371 (view as bug list)
Depends On:
Blocks: GSS_Sat6Beta_Tracker, GSS_Sat6_Tracker
TreeView+ depends on / blocked
 
Reported: 2016-03-08 22:18 UTC by Chris Roberts
Modified: 2019-09-25 20:40 UTC (History)
8 users (show)

Fixed In Version: katello-3.0.0-5
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1342496 (view as bug list)
Environment:
Last Closed: 2016-07-27 11:26:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14125 0 Normal Closed katello-remove does not remove many things 2020-01-14 15:53:16 UTC

Description Chris Roberts 2016-03-08 22:18:44 UTC 
Description of problem:
katello-remove should remove /etc/gutterball directory

How reproducible:


Steps to Reproduce:
1. install sat 6.1
2. katello-remove
3. dir is still present

Actual results:
rw-r--r--. 1 root   root    974 Mar  8 16:12 gutterball.conf.rpmsave

Expected results:
/etc/gutterball to be removed

Additional info:

marking as 6.2, tested with latest snap and still keeps directory
Comment 2 Bryan Kearney 2016-03-09 21:08:51 UTC 
Upstream bug component is Installer
Comment 3 Mike McCune 2016-04-13 17:02:26 UTC 
From https://bugzilla.redhat.com/show_bug.cgi?id=1320234 more things to consider:

"""
Install 6.2 and remove katello after playing around. 

After katello-remove, try to re install satellite with regular instructions). Install fails with below error as its not able to clean old ssl certificates. 

---
Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
 /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
 Proxy pman05.perf.lab.eng.bos.redhat.com cannot be registered (422 Unprocessable Entity): Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([OpenSSL::SSL::SSLError]: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verif...) for proxy https://pman05.perf.lab.eng.bos.redhat.com:8443/features Please check the proxy is configured and running on the host.
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[pman05.perf.lab.eng.bos.redhat.com]/ensure: change from absent to present failed: Proxy pman05.perf.lab.eng.bos.redhat.com cannot be registered (422 Unprocessable Entity): Unable to communicate with the proxy: ERF12-2530 [ProxyAPI::ProxyException]: Unable to detect features ([OpenSSL::SSL::SSLError]: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verif...) for proxy https://pman05.perf.lab.eng.bos.redhat.com:8443/features Please check the proxy is configured and running on the host.
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[pman05.perf.lab.eng.bos.redhat.com]: Failed to call refresh: Proxy pman05.perf.lab.eng.bos.redhat.com cannot be registered 
---


Had to remove /etc/foreman-installer manually to start fresh install

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


How reproducible:


Steps to Reproduce:
1. Install 6.2 and remove using katello-remove
2. Try to reinstall again
"""
Comment 4 Mike McCune 2016-04-13 17:02:58 UTC 
*** Bug 1320234 has been marked as a duplicate of this bug. ***
Comment 5 Pradeep Kumar Surisetty 2016-04-15 07:39:31 UTC 
similar one with capsule-remove also

https://bugzilla.redhat.com/show_bug.cgi?id=1327442
Comment 6 Bryan Kearney 2016-05-17 14:19:43 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14125 has been closed
Comment 7 Stephen Benjamin 2016-05-24 20:26:56 UTC 
*** Bug 1339371 has been marked as a duplicate of this bug. ***
Comment 8 Bruno Rocha 2016-06-29 21:59:25 UTC 
The original bug is fixed
The /etc/gutterball is being removed.

re-installation worked without errors


Full log privatelly attached


Tested after re-install:

[root@ibm-x3550m3-06 ~]# hammer -u admin -p changeme ping
candlepin:      
    Status:          ok
    Server Response: Duration: 48ms
candlepin_auth: 
    Status:          ok
    Server Response: Duration: 45ms
pulp:           
    Status:          ok
    Server Response: Duration: 50ms
foreman_tasks:  
    Status:          ok
    Server Response: Duration: 915ms
Comment 10 Bryan Kearney 2016-07-27 11:26:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2016:1501
Note You need to log in before you can comment on or make changes to this bug.