[openstack-dev] [infra][devstack] stable/kilo devstack fails with pkg_resources.ContextualVersionConflict
mriedem at linux.vnet.ibm.com
Sat Apr 23 18:04:56 UTC 2016
On 4/23/2016 1:02 PM, Matt Riedemann wrote:
> On 4/22/2016 3:56 PM, Felipe Reyes wrote:
>> On Thu, 21 Apr 2016 15:12:53 +1000
>> Tony Breeds <tony at bakeyournoodle.com> wrote:
>>> On Tue, Apr 19, 2016 at 01:14:34PM +0200, Lajos Katona wrote:
>>>> In our internal CI system we realized that stable/kilo devstack
>>>> fails with the following stack trace:
>>>> It seems that the root cause is that testresources has a new
>>>> version 2.0.0 from 18 April.
>>>> I tried to find similar errors on openstack infra, but for me
>>>> http://logstash.openstack.org/ gives back no result.
>>>> I have a patch in requirements
>>>> (https://review.openstack.org/307174) but I got the same error for
>>>> those runs.
>>> Thanks for you help!
>>>> Could somebody help to find a solution for this?
>>> This should be resolved now, with the release of oslo.db 1.7.5
>> I'm experiencing this same problem in stable/liberty for heat, I
>> pushed a patch for review at https://review.openstack.org/#/c/309570/ .
>> But I'm getting an error with the 'releasenotes' tox environment:
>> 2016-04-22 19:58:15.356 | + tox -v -ereleasenotes
>> 2016-04-22 19:58:15.656 | using tox.ini:
>> 2016-04-22 19:58:15.657 | ERROR: unknown environment 'releasenotes'
>> Am I doing something wrong?
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> There are a few issues here:
> 1. Heat on stable/liberty apparently runs the releasenotes job but
> doesn't have the releasenotes target in it's tox.ini. So either backport
> that or exclude running the releasenotes job for Heat on stable/liberty
> (in the project-config repo). That might be fixed now actually:
Sorry, this is actually oslo.db that's failing on stable/liberty because
of the releasenotes job, not Heat.
> 2. Heat is also apparently not using upper-constraints when running
> tests in stable/liberty (or stable/mitaka or master for that matter). We
> aren't going to cap testresources<2.0 in global-requirements in
> stable/liberty because it's already effectively capped at 1.0.0 in
> upper-constraints in stable/liberty:
More information about the OpenStack-dev