-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
State pkg.purged doesn't purge packages on at least Debian 8 to 11 #42306
Comments
@tkaehn Thanks for the report. So far I haven't been able to duplicate this particular issue if I rely on Salt to purge them. I do see the same results if I first use apt to remove them and then run the state. Were these packages previous removed manually prior to running the state? |
@garethgreenaway Yes, the packages were removed before (in this case by installing postfix in another state file) and it's the same behaviour here: An installed package is purged, a removed package is not. |
The issue applies for Salt 2017.7.0 as well. |
Still not fixed in 2017.7.1 |
All,
Due to a misconfiguration on our Office365 tenant, all email addressed to your Ruckus Wireless email address ([email protected]) were delivered to a catch all mailbox. This incident occurred between 11 PM to 8 AM (PST). IT is delivering these emails with a “Reply-all” rule to all individuals on the email chain. If you feel you are missing email attachments, please send email to [email protected].
We apologize for any inconvenience this may have caused.
Regards,
IT
From: Thomas Kähn [mailto:[email protected]]
Sent: Thursday, September 14, 2017 11:58 PM
To: saltstack/salt <[email protected]>
Cc: Subscribed <[email protected]>
Subject: Re: [saltstack/salt] State pkg.purged doesn't purge packages on at least Debian 8 and 9 (#42306)
Still not fixed in 2017.7.1
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#42306 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHusM_8JSuq8ONyZ-ep00GbsgzqpNScXks5sih_-gaJpZM4OYEkQ>.
|
Problem still exists in 2017.7.2. |
Problem still exists in 2018.3.0. @garethgreenaway the ticket is still labelled as "Info needed". Which info do you need? |
Problem still exists in 2019.2.0:
|
Any idea when this is going to be fixed? It's nearing its 2nd anniversary... |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Looks like today's "Stale Bot Day"... |
Thank you for updating this issue. It is no longer marked as stale. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Thank you for updating this issue. It is no longer marked as stale. |
@dmurphy18 can you follow up on this ticket, please? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue. |
Ping! |
Thank you for updating this issue. It is no longer marked as stale. |
stale bot is disabled so that won't be a problem any longer, kicking this back to triage and will follow up tomorrow. |
I thought it was going through another round of triage, but looks like it is still pending that task. I will follow up with getting it through triage again this week and check back on Friday 2020-04-17 |
Hitting this now. Package previously removed, but not purged. However pkg.purged is returning 'All specified packages are already absent' |
@tkaehn @biwhite This issue is for Python 2.7 which is no longer supported. But I tried with the current Salt 3005.1 minion (classic packaging) on Debian 10 (Debian 8 & 9 being EOL) which uses Python 3. Whatever the problem it appears to have been fixed
Hence closing this issue. Please open a new issue if this does not resolve the matter for you, given that this issue was originally with Python 2.7 on platforms which are End-Of-Life. Apologies for taking so long to resolve this issue. |
Unfortunately the problem isn't solved at all. A package that is installed is purged. However a package that has already been removed still isn't purged. Here are the steps to reproduce the problem:
|
Please re-open this issue. |
@tkae Well from #5503 and its associated #4972, looks like functionality was broken long ago circa 2016.11 or before, probably in the transition from apt.py module to aptpkg.py, which is very long ago. This will take some time to wade through to see the breakage, will re-open |
Looks like there is a problem in handling function _find_remove_targets given its comment about returning a dict, but it sometimes returns a state return object and other times a list, it and its usage needs to be refactored. Note that pkg.purge from execution module does purge packages which are removed. |
Steps to reproduce.
The same results on Debian or Ubuntu
pkg.purged should purge installed and removed packages on the machine similar to execution module command pkg.purge |
Description of Issue/Question
State pkg.purged doesn't purge packages on at least Debian 8 and 9
Steps to Reproduce Issue
Versions Report
The text was updated successfully, but these errors were encountered: