Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[dev.icinga.com #10035] Icinga2 is not cleaned properly when doing apt-get prune icinga2 #3339

Closed
icinga-migration opened this issue Aug 28, 2015 · 7 comments
Labels
area/setup Installation, systemd, sample files bug Something isn't working

Comments

@icinga-migration
Copy link

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10035

Created by Trefex on 2015-08-28 16:30:20 +00:00

Assignee: formorer
Status: Resolved (closed on 2015-09-06 20:11:43 +00:00)
Target Version: (none)
Last Update: 2015-09-06 20:11:43 +00:00 (in Redmine)

Icinga Version: 2.3.8-1
Backport?: Not yet backported
Include in Changelog: 1

When doing a apt-get prune icinga2 followed by an apt-get autoremove, the following icinga2 entries still remain on the machine.

./etc/bash_completion.d/icinga2
./etc/init.d/icinga2
./etc/default/icinga2
./etc/logrotate.d/icinga2

I suppose these should be added to the cleanup.

@icinga-migration
Copy link
Author

Updated by gbeutner on 2015-08-29 10:01:17 +00:00

  • Category changed from Installation to Packages
  • Status changed from New to Assigned
  • Assigned to set to formorer

@icinga-migration
Copy link
Author

Updated by formorer@formorer.de on 2015-08-30 19:57:53 +00:00

On Sat, 29 Aug 2015, development@icinga.org wrote:

Issue #10035 has been updated by gunnarbeutner.

Category changed from Installation to Packages
Status changed from New to Assigned
Assignee set to formorer


Bug #10035: Icinga2 is not cleaned properly when doing apt-get prune icinga2
https://dev.icinga.org/issues/10035#change-42475

* Author: Trefex
* Status: Assigned
* Priority: Normal
* Assignee: formorer
* Category: Packages
* Target version:
* Icinga Version: 2.3.8-1
* Package Repository:
* Backport?: TBD
* Include in Changelog: Yes

When doing a apt-get prune icinga2 followed by an apt-get autoremove, the following icinga2 entries still remain on the machine.

./etc/bash_completion.d/icinga2
./etc/init.d/icinga2
./etc/default/icinga2
./etc/logrotate.d/icinga2

I suppose these should be added to the cleanup.
Nope. those are configfiles. Unless you do an explicit purge, they won't get
removed.

Btw. a command like apt-get prune doesn't exist, I guess you meaned apt-get
remove.

Alex

@icinga-migration
Copy link
Author

Updated by Trefex on 2015-08-30 20:42:11 +00:00

Hi,

Sorry, I meant apt-get purge, not prune... :)

Best,

@icinga-migration
Copy link
Author

Updated by formorer@formorer.de on 2015-08-30 20:49:52 +00:00

On Sun, 30 Aug 2015, development@icinga.org wrote:

Issue #10035 has been updated by Trefex.

Hi,

Sorry, I meant apt-get purge, not prune... :)
what are the exact commands you typed?

Alex

@icinga-migration
Copy link
Author

Updated by Trefex on 2015-08-30 20:58:11 +00:00

apt-get purge icinga2

@icinga-migration
Copy link
Author

Updated by formorer@formorer.de on 2015-08-30 21:01:17 +00:00

On Sun, 30 Aug 2015, development@icinga.org wrote:

Issue #10035 has been updated by Trefex.

apt-get purge icinga2
That won't purge any of the packages containing configuration. Let me guess,
the command you missed to tell me was apt-get autoremove? Which also doesn't
do a purge on the packages it removes. Therefore all configuration files will
stay.

Everything works as designed.

Alex

@icinga-migration
Copy link
Author

Updated by formorer on 2015-09-06 20:11:43 +00:00

  • Status changed from Assigned to Resolved

Works as designed, therefore I'll close the bug now.

@icinga-migration icinga-migration added bug Something isn't working area/setup Installation, systemd, sample files labels Jan 17, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/setup Installation, systemd, sample files bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant