Bug 1628380 - [OSP14] PEP8 tests fail on neutron.agent.linux.utils pylint
Summary: [OSP14] PEP8 tests fail on neutron.agent.linux.utils pylint
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 14.0 (Rocky)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 14.0 (Rocky)
Assignee: Assaf Muller
QA Contact: Roee Agiman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-09-12 20:51 UTC by Bernard Cafarelli
Modified: 2019-01-11 11:53 UTC (History)
4 users (show)

Fixed In Version: openstack-neutron-13.0.1-0.20180910090451.d48b0c1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-11 11:53:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 603041 0 None None None 2018-09-17 08:03:36 UTC
Red Hat Product Errata RHEA-2019:0045 0 None None None 2019-01-11 11:53:16 UTC

Description Bernard Cafarelli 2018-09-12 20:51:17 UTC 
Description of problem:
PEP8 tests always fail with recent builds

Version-Release number of selected component (if applicable):
Latest OSP14, 20180906.1 puddle

How reproducible:
100%

Backtrace:
Running pylint...
You can speed this up by running it on 'HEAD~[0-9]' (e.g. HEAD~1, this change only)...
************* Module neutron.agent.linux.utils
E:406,12: Too many positional arguments for unbound method call (too-many-function-args)
ERROR: InvocationError: '/usr/bin/sh ./tools/coding-checks.sh --pylint '
___________________________________ summary ____________________________________
ERROR:   pep8: commands failed
Comment 4 Bernard Cafarelli 2018-09-20 08:31:41 UTC 
Merged upstream in stable branch, get in latest import
Comment 8 errata-xmlrpc 2019-01-11 11:53:06 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/RHEA-2019:0045
Note You need to log in before you can comment on or make changes to this bug.