Project

General

Profile

Actions
Copy link

Feature #25671

open

Allow openscap plugin to be uninstalled

Added by Ondřej Pražák over 5 years ago. Updated over 5 years ago.

Status:
Needs design
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
hard
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

This will require a design of how exactly the plugins should be uninstalled and likely additional support from core. Steps to completely remove the plugin will include steps on server, proxy and clients as well. The following list is probably not complete.

server:
  • drop tables
  • remove reports and associated information about rules and results that we store in core's tables
  • remove compliance status
  • remove openscap proxy from hosts/hostgroups
  • remove foreman_scap_client Puppet class from hosts/hostgroups
proxy:
  • disable and remove smart_proxy_openscap + dependencies
  • clean up reports and spool on proxy
client:
  • remove foreman_scap_client + dependencies, config and cron

Related issues 1 (1 open — 0 closed)

Related to OpenSCAP - Bug #25763: Removing a content host should purge away SCAP config from the hostNeeds designActions
Actions
Copy link
 #1

Updated by Marek Hulán over 5 years ago

We should first implement the rake task for cleaning up the data, similarly to how foreman_templates or foreman_virt_who_configure plugins do it. The rest should most likely be added to foreman-maintain that as part of uninstallation would use this rake task.

Actions
Copy link
 #2

Updated by Ondřej Pražák over 5 years ago

  • Related to Bug #25763: Removing a content host should purge away SCAP config from the host added
Actions
Copy link

Also available in: Atom PDF