| 2019-10-17 13:42:32 |
Sorin Sbarnea |
bug |
|
|
added bug |
| 2019-10-17 13:57:57 |
wes hayutin |
tags |
promotion-blocker |
alert promotion-blocker |
|
| 2019-10-18 08:40:19 |
Sorin Sbarnea |
description |
All jobs using ansible-lint via pre-commit (aka tox-molecule-linters) got broken when a newer version of setuptools was released.
The bug itself is not caused by setuptools but by the ugly-hack present inside setup.py from the ansible-lint project.
I already proposed the PR to fix it but projects maintenance status is not one of the best right now, it may take more time to get it merged and a new release made.
Meanwhile I was able to find a workaround that looks like:
https://review.rdoproject.org/r/#/c/23215/4/tox.ini
Fixes need to be done in all repositories where we encounter them.
Upstream references:
* https://github.com/ansible/ansible-lint/issues/590
* https://github.com/pypa/setuptools/issues/1869
I will mark this as a promotion blocker because is high-likely that most CR would be blocked by the broken linters jobs until we implement workarounds everywhere. |
All jobs using ansible-lint via pre-commit (aka tox-molecule-linters) got broken when a newer version of setuptools was released.
The bug itself is not caused by setuptools but by the ugly-hack present inside setup.py from the ansible-lint project.
I already proposed the PR to fix it but projects maintenance status is not one of the best right now, it may take more time to get it merged and a new release made.
Meanwhile I was able to find a workaround that looks like:
https://review.rdoproject.org/r/#/c/23215/4/tox.ini
Fixes need to be done in all repositories where we encounter them.
Upstream references:
* https://github.com/ansible/ansible-lint/issues/590 <-- please comment here, and also cross post to #ansible-galaxy channel (they own the project)
There are already two PRs that are fixing the issue but they were not reviewed/merged/released.
* https://github.com/pypa/setuptools/issues/1869
I will mark this as a promotion blocker because is high-likely that most CR would be blocked by the broken linters jobs until we implement workarounds everywhere. |
|
| 2019-10-18 08:42:54 |
Sorin Sbarnea |
description |
All jobs using ansible-lint via pre-commit (aka tox-molecule-linters) got broken when a newer version of setuptools was released.
The bug itself is not caused by setuptools but by the ugly-hack present inside setup.py from the ansible-lint project.
I already proposed the PR to fix it but projects maintenance status is not one of the best right now, it may take more time to get it merged and a new release made.
Meanwhile I was able to find a workaround that looks like:
https://review.rdoproject.org/r/#/c/23215/4/tox.ini
Fixes need to be done in all repositories where we encounter them.
Upstream references:
* https://github.com/ansible/ansible-lint/issues/590 <-- please comment here, and also cross post to #ansible-galaxy channel (they own the project)
There are already two PRs that are fixing the issue but they were not reviewed/merged/released.
* https://github.com/pypa/setuptools/issues/1869
I will mark this as a promotion blocker because is high-likely that most CR would be blocked by the broken linters jobs until we implement workarounds everywhere. |
All jobs using ansible-lint via pre-commit (aka tox-molecule-linters) got broken when a newer version of setuptools was released.
The bug itself is not caused by setuptools but by the ugly-hack present inside setup.py from the ansible-lint project.
I already proposed the PR to fix it but projects maintenance status is not one of the best right now, it may take more time to get it merged and a new release made.
Meanwhile I was able to find a workaround that looks like:
https://review.rdoproject.org/r/#/c/23215/4/tox.ini
Fixes need to be done in all repositories where we encounter them.
Upstream references:
* https://github.com/ansible/ansible-lint/issues/590 <-- please comment here, and also cross post to #ansible-galaxy channel (they own the project)
There are already two PRs that are fixing the issue but they were not reviewed/merged/released.
* https://github.com/pypa/setuptools/issues/1869
I will mark this as a promotion blocker because is high-likely that most CR would be blocked by the broken linters jobs until we implement workarounds everywhere.
Temporary workarounds:
deps =
# workaround for https://github.com/ansible/ansible-lint/issues/590
virtualenv==16.3.0 # 16.7.6 not working
pre-commit
By pinning the virtualenv on tox.ini we can avoid this breakage, that is because newer virtualenv bring a newer setuptools, one that is not compatible with the dirty hacks made in setup.py of ansible-lint. |
|
| 2019-10-18 09:31:42 |
Sorin Sbarnea |
tripleo: status |
Triaged |
In Progress |
|
| 2019-10-23 07:13:09 |
Marios Andreou |
tags |
alert promotion-blocker |
ci promotion-blocker |
|
| 2019-10-24 09:56:37 |
OpenStack Infra |
bug watch added |
|
https://github.com/ansible/ansible-lint/issues/595 |
|
| 2019-10-24 09:56:37 |
OpenStack Infra |
bug watch added |
|
https://github.com/ansible/ansible-lint/issues/590 |
|
| 2019-11-26 16:54:30 |
Sorin Sbarnea |
tripleo: status |
In Progress |
Fix Released |
|
