Project

Profile

Help

Maintenance. Planio will be undergoing a scheduled maintenance this weekend. Between Saturday, July 24 at 9:00 UTC and Sunday, July 25, 22:00 UTC your account might observe occasional downtimes which may last up to several minutes in some cases.

Story #4944

As a user, I can uninstall plugin and remove all the relevant data

Added by ttereshc about 2 years ago. Updated 3 months ago.

Status:
CLOSED - WONTFIX
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Currently there is no way to uninstall a plugin together with removing data related to it.

If there is a need for that or not is still a question.
At the very least, let's document how to do it manually (if possible) or just state the fact that it's not supported.

Use cases to cover:
- install a plugin, do nothing (no sync, upload, etc), uninstall the plugin
- install a plugin, use it, uninstall the plugin

History

#1 Updated by ttereshc about 2 years ago

  • Description updated (diff)

#2 Updated by mdepaulo@redhat.com about 2 years ago

As a sysadmin at my last job, we only used Pulp as part of Satellite.
(We were phasing out rsync scripts from other parts of our environment.)

If we had used Pulp directly:
1. The inability to uninstall plugins would not be a big deal. Assuming they don't slow down Pulp (despite having no content), complicate the UI, etc.
2. If we did uninstall it, we would definitely want to cleanup the disk space / content (either at plugin uninstall time, or after).
3. If we did uninstall it, we would have only a small preference for it to cleanup the database. But it wouldn't be a big deal. We would never poke around in the database to see if it was removed. And we would only really care if we suspected that Pulp was not working because of the plugin having been previously installed. We would definitely care if we reinstalled it (much) later, and it didn't work. Compare this to how on Windows, when you uninstall an app, it usually has lots of leftover state in the registry. Leftover "cruft" is a fact of life, especially on Windows. And you eliminate cruft by rebuilding the server, including the application state.

Also, the inability to uninstall the file plugin specifically would be OK with us, assuming the above from #1. We would probably use for testing purposes if we suspected the other plugin we needed was not working. We would treat it like a reference plugin.

#3 Updated by dkliban@redhat.com 10 months ago

  • Status changed from NEW to CLOSED - WONTFIX

#4 Updated by Ben.Stanley 3 months ago

I have now found myself in a difficult situation, where I have accidentally installed a plugin (pulp-cookbook) on pulpcore 3.12.1. However, the installation failed with the following error: File "/usr/local/lib/pulp/lib64/python3.6/site-packages/pulpcore/app/apps.py", line 65, in init, self.version, AttributeError: 'PulpCookbookPluginAppConfig' object has no attribute 'version'", "", "During handling of the above exception, another exception occurred:", "", ... It seems that the pulp-cookbook is not compatible with pulpcore 3.12.1 and that I should not have attempted to install it. Now that I have accidentally attempted to install it, how can I uninstall it?

#5 Updated by Ben.Stanley 3 months ago

I don't know if I did this correctly, but I have removed pulp-cookbook by removing the directories /usr/local/lib/pulp/lib64/python3.6/site-packages/pulp_cookbook /usr/local/lib/pulp/lib64/python3.6/site-packages/pulp_cookbook-0.1.0b8.dist-info After removing these directories, I can now run the ansible installer again to install additional packages (e.g. pulp-2to3-migration plugin).

#6 Updated by bmbouter 3 months ago

I just now saw this, and what you did is probably ok too. Another option would have been to activate the virtualenv that the python packages are installed into, e.g. source /usr/local/lib/pulp/bin/activate and then pip uninstall pulp-cookbook.

Please register to edit this issue

Also available in: Atom PDF