This content has been marked as final. Show 4 replies
sometimes some entries in Run History Log prohibit the deletion of the Plugin. Have a look in the log if any deployment artefacts remain there, remove them and try again to delete the plugin.
Thanks for your reply. I have tried deleting them and still get the same results. I'm considering removing it from the database itself, but there are too many foreign key restraints.
Any other ideas?
deleting directly from the DB is not a good idea, you could damage a lot more things.... Did you really check that all objects/virtual hosts/system services from the plugin have been delete everywhere? Maybe you defined a specific Host Type which is still existing somewhere?
If nothing works, you should re-install the system or recover an older backup. In Plugin development in general it is sometimes faster to fall back to an old backup version (you could use a snapshot with ZFS or anything) during your test cycles. Have you already thought about that?
I see what you mean. Thank you.
I have a few backups but none of them are old enough to predate the installation of the plugin.
I'm pretty sure the plugin has been un-installed from all hosts and I've deleted the run history for the last year.
I guess you are correct in indicating that backups should be taking at all times when planning for a plugin installation.