Bug 1387166 - oscap-docker man page inconsistence
Summary: oscap-docker man page inconsistence
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: openscap
Version: 7.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Jan Černý
QA Contact: Matus Marhefka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-20 09:32 UTC by Matus Marhefka
Modified: 2017-08-01 08:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 08:45:48 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2291 0 normal SHIPPED_LIVE openscap bug fix update 2017-08-01 12:38:59 UTC

Description Matus Marhefka 2016-10-20 09:32:59 UTC 
Description of problem:
oscap-docker man page incorrectly states that for compliance scan
of image/container, OSCAP_ARGUMENTS are not mandatory (they are enclosed
in brackets). Usage should rather have the following form:

oscap-docker image IMAGE_NAME OSCAP_ARGUMENT [OSCAP_ARGUMENT...]
oscap-docker container CONTAINER_NAME OSCAP_ARGUMENT [OSCAP_ARGUMENT...]


Version-Release number of selected component (if applicable):
openscap-utils-1.2.10-2.el7

How reproducible:
always

Steps to Reproduce:
1. man 8 oscap-docker

Actual results:


Expected results:


Additional info:
Comment 2 Jan Černý 2016-10-20 13:27:43 UTC 
Fixed upstream in https://github.com/OpenSCAP/openscap/commit/9ae71db8011864545ab37e7ce37c71a7459db44d
Comment 4 Matus Marhefka 2017-04-26 12:00:23 UTC 
VERIFIED as fixed for openscap-utils-1.2.14-1.el7
Comment 5 errata-xmlrpc 2017-08-01 08:45:48 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2291
Note You need to log in before you can comment on or make changes to this bug.