Bug #20666: Scap CLI policy update successful with no scap-profile - OpenSCAP - Foreman

Actions

Copy link

Bug #20666

closed

Scap CLI policy update successful with no scap-profile

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

Status:

Closed

Priority:

Normal

Assignee:

Ondřej Pražák

Target version:

foreman_openscap 0.7.5

Difficulty:

Triaged:

Bugzilla link:

1482548

Pull request:

https://github.com/theforeman/foreman_openscap/pull/279, https://github.com/theforeman/foreman_openscap/pull/283, https://github.com/theforeman/foreman_openscap/pull/287

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Description

Steps to Reproduce:
policy info --id 5
Id: 5
Name: test1
Created at: 2017-08-17 13:26:59 UTC
Period: monthly
Weekday:
Cron line:
Scap content Id: 4
Scap Content profile Id: 23
Tailoring file Id: 1
Tailoring file profile Id: 52
Locations:
Default Location
Organizations:
Default Organization

hammer> policy update --id 5 --scap-content-id 3
Policy updated

policy info --id 5
Id:                        5
Name:                      test1
Created at:                2017-08-17 13:26:59 UTC
Period:                    monthly
Weekday:                   
Cron line:                 
Scap content Id:           3
Scap Content profile Id:   23
Tailoring file Id:         1
Tailoring file profile Id: 52
Locations:                 
    Default Location
Organizations:             
    Default Organization

Here, the weird part , scap-content 3 , doesn't have a profile-id 23

Actual results:
Scap policy was updated without scap-profile-id parameter

Expected results:
Scap policy update should not be updated with scap-profile parameter