RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
In --help dialog, there no difference between --scanner and --scan_type explanation. 

[dahaic@dhcp-24-168 ~]$ atomic scan --help
[...]
  --scanner {openscap}  define the intended scanner
  --scan_type SCAN_TYPE
                        define the intended scanner
[...]

Version-Release number of selected component (if applicable):
atomic-1.10.5-7.el7.x86_64

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:

$ atomic scan --help
[...]
  --scanner {openscap}  define the intended scanner
  --scan_type SCAN_TYPE
                        define the intended scanner
[...]

Expected results:
$ atomic scan --help
[...]
  --scanner {openscap}  define the intended scanner
  --scan_type SCAN_TYPE
                        define the intended scan type
[...]

Additional info:
It's slightly confusing as it is now.

Fixed upstream with https://github.com/projectatomic/atomic/pull/532

Fixed in atomic-1.11

# rpm -q atomic
atomic-1.12.2-2.el7.x86_64

# atomic scan -h|grep -E "(scanner|scan_type)"
usage: atomic scan [-h] [--scanner {openscap}] [--scan_type SCAN_TYPE]
  --scanner {openscap}  define the intended scanner
  --scan_type SCAN_TYPE
  --list                List available scanners

(In reply to Alex Jia from comment #5)
> # rpm -q atomic
> atomic-1.12.2-2.el7.x86_64
> 

# atomic scan -h|grep -iE "(scanner|scan_type|scan type)"
usage: atomic scan [-h] [--scanner {openscap}] [--scan_type SCAN_TYPE]
  --scanner {openscap}  define the intended scanner
  --scan_type SCAN_TYPE
                        define the intended scan type
  --list                List available scanners

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://rhn.redhat.com/errata/RHBA-2016-2628.html