I partially agree. Originally, this risk level was supposed to indicate what was checked - and basically saying "Ok, this seems to be safe". However, this was based on assumption we will have some separate report of risks. Nowadays, just info message should be enough and much less confusing. Therefore ack for devel side.

Moving to Petr, however, it would require checking all scripts for existance of "none" risk usage.

(In reply to Ondrej Vasik from comment #3)
> Moving to Petr, however, it would require checking all scripts for existance
> of "none" risk usage.

JFTR; bug 1356057 is the one to track removal of NONE usage from modules.

Not removed; still present in

 *  common.sh (Bash API)

 *  tests (created "manually" using echo),

 *  more places:

        @fullmoon|work:~/vcs.ipu/preupgrade-assistant((2.1.8))$ grep _none_ -r
        common.sh:303:log_none_risk() {
        preuputils/xml_utils.py:179:        check_func = {'log_': ['log_none_risk', 'log_slight_risk',
        @fullmoon|work:~/vcs.ipu/preupgrade-assistant((2.1.8))$ grep NONE -r
        tests/FOOBAR6_7/dummy/needs_inspection/dummy_failed.sh:5:echo "INPLACERISK: NONE: This is None Risk"
        tests/FOOBAR6_7/dummy/needs_inspection/solution.txt:3:INPLACERISK: NONE: None inplace risk
        tests/test_inplace_risks.py:87:        temp_file = self._copy_xccdf_file(b'INPLACERISK: NONE: Test None Inplace risk')
        common.sh:307:    log_risk "NONE" "$1"
        preup/cli.py:103:                 "0 ... NONE, SLIGHT risks were detected." + "\n" * 20 +
        preup/xccdf.py:28:            'NONE:': 0,
        preup/report_parser.py:40:        of NONE, SLIGHT or MEDIUM risk
        preup/report_parser.py:222:        NEEDS_INSPECTION in case that risks are NONE or SLIGHT
        man/preupg.1:58:Return values are 0 for NONE, SLIGHT risks or 1 for MEDIUM, HIGH risks or 2 for EXTREME risk.
        preup_ui/xmlrpc_backend/views.py:53:  <meta name="robots" content="NONE,NOARCHIVE" />
        @fullmoon|work:~/vcs.ipu/preupgrade-assistant((2.1.8))$ 

    (not all places are necessarily be relevant but you get the point)

preupgrade-assistant-2.1.9-1.el6:  this time it's wiped out properly. :)

(Also from modules, as tracked by bug 1356057)

(Well, except it's still mentioned in one note in the manpage, but since the manpage is so obsolete and incomplete it's ready for rewrite, that should not block us.)

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-2616.html