Project

General

Profile

Actions

Bug #23530

closed

foreman_openscap should not require puppet classes be imported

Added by Trey Dockendorf almost 6 years ago. Updated about 5 years ago.

Status:
Duplicate
Priority:
High
Assignee:
-
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

I just installed tfm-rubygem-foreman_openscap-0.7.13-1.fm1_15.el7.noarch on Foreman 1.15.6 and discovered I have to import Puppet classes in order to start adding content. I don't use that feature of Foreman, I define all classes via roles/profiles and Hiera. It would be handy if this class requirement was removed or made optional.

When I try to add a new policy after giving it a name and hitting "Next" I get this:

Unable to save
Puppet class foreman_scap_client does not have policies class parameter.

https://github.com/theforeman/foreman_openscap/blob/6aa3c8ced100e1ea2bf3423d76757d872c1a3e2b/app/models/concerns/foreman_openscap/openscap_proxy_core_extensions.rb#L71

As a work around I'm importing classes but I'd rather not pollute my instance of Foreman with Puppet classes when we don't want to support classes getting added via Foreman.


Related issues 1 (0 open1 closed)

Is duplicate of OpenSCAP - Feature #23950: Satellite should support SCAP reports without the need of puppet installed on hostsClosedOndřej PražákActions
Actions #1

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

  • Bugzilla link set to 1625752
Actions #2

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

  • Is duplicate of Feature #23950: Satellite should support SCAP reports without the need of puppet installed on hosts added
Actions #3

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

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF