Bug #20666
closedScap CLI policy update successful with no scap-profile
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
Updated by The Foreman Bot over 7 years ago
- Status changed from New to Ready For Testing
- Assignee set to Ondřej Pražák
- Pull request https://github.com/theforeman/foreman_openscap/pull/279 added
Updated by Ondřej Pražák over 7 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset foreman_openscap|2fda7db006d10aaa846ba280bdb10ac1eea53cec.
Updated by The Foreman Bot over 7 years ago
- Pull request https://github.com/theforeman/foreman_openscap/pull/283 added
Updated by Marek Hulán over 7 years ago
- Subject changed from Scap CLI policy update successful with no scap-profile to Scap CLI policy update successful with no scap-profile
- Translation missing: en.field_release set to 274
Updated by The Foreman Bot over 7 years ago
- Pull request https://github.com/theforeman/foreman_openscap/pull/287 added