Bug 1573257 - atomic scan doesn't work with default or explicit openscap scanner configuration
Summary: atomic scan doesn't work with default or explicit openscap scanner configuration
Alias: None
Product: Fedora
Classification: Fedora
Component: atomic
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Daniel Walsh
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-30 15:46 UTC by Javier Ramirez
Modified: 2019-05-29 00:11 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-29 00:11:01 UTC
Type: Bug

Attachments (Terms of Use)

Description Javier Ramirez 2018-04-30 15:46:59 UTC
Description of problem:
After installing atomic tool on Fedora 28 scan feature does not work by default.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. dnf install atomic
2. sudo atomic scan list

Actual results:
$ sudo atomic scan --list
No scanners are configured for your system.

Expected results:
Scan to work

Additional info:
It worked after doing:
atomic install registry.access.redhat.com/rhel7/openscap

Comment 1 Brent Baude 2018-05-01 12:53:24 UTC
As you have noted, you must perform an install of the openscap image for this to work.

Comment 2 Ben Cotton 2019-05-02 19:22:32 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-05-29 00:11:01 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.