Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Doug Hellmann]

Excerpts from Tony Breeds's message of 2017-03-02 19:41:17 +1100:
> On Thu, Mar 02, 2017 at 06:24:32PM +1100, Tony Breeds wrote:
> 
> > I know I'm talking to myself .
> 
> Still.
> 
> > A project on $branch without constraints is going to get pbr 2.0.0 and then 
> > hit
> > version conflicts with projects that have pbr <2.0.0 caps *anyway* 
> > regardless
> > of what hacking says right?
> > 
> > So removing the pbr cap in hacking doesn't make things worse for stable
> > branches but it does make things better for master?
> 
> I think the 0.10.3 hacking release is the best way forward but in the mean 
> time
> a quick project by project fix is to just update hacking.
> 
> See Ian's patch at: https://review.openstack.org/#/c/440010/
> 
> I'm a little unwilling to create all the updates but I make look at that 
> after dinner.
> 
> Yours Tony.

Rico Lin was very busy:
https://review.openstack.org/#/q/status:open+topic:bug/1668848

Let's see if we can get those approved and avoid a patch release of
hacking.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Tony Breeds]

On Thu, Mar 02, 2017 at 06:24:32PM +1100, Tony Breeds wrote:

> I know I'm talking to myself .

Still.

> A project on $branch without constraints is going to get pbr 2.0.0 and then 
> hit
> version conflicts with projects that have pbr <2.0.0 caps *anyway* regardless
> of what hacking says right?
> 
> So removing the pbr cap in hacking doesn't make things worse for stable
> branches but it does make things better for master?

I think the 0.10.3 hacking release is the best way forward but in the mean time
a quick project by project fix is to just update hacking.

See Ian's patch at: https://review.openstack.org/#/c/440010/

I'm a little unwilling to create all the updates but I make look at that after 
dinner.

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Tony Breeds]

On Thu, Mar 02, 2017 at 06:07:47PM +1100, Tony Breeds wrote:
> On Thu, Mar 02, 2017 at 05:01:43PM +1100, Tony Breeds wrote:
> 
> > And yes there are now plenty of pep8 jobs that are failing with PBR 2.0.0
> > 
> > We can't revert the requirements change that landed which means that 
> > projects
> > using old hacking versions are going to need an update :(
> 
> One option may be to release 0.10.3 of hacking that removes the cap on pbr.  I
> think this would fix the issues on master but I *think* it will cause problems
> on ,at least, stable/mitaka where 0.10.x is still the preferred version.
> 
> For projects that have constraints support things will be fine as the version
> selected for PBR will come from upper-constraints.txt and hacking from
> requirements so those projects will get pbr == 1.8.1 and hacking 0.10.3 
> #winning.
> 
> For projects that don't have constraints support which is still quite a few[1]
> they'll end up with pbr 2.0.0 which will almost certainly break things.
> Probably not in behaviour but more likely with similar VersionConflicts.

I know I'm talking to myself .

A project on $branch without constraints is going to get pbr 2.0.0 and then hit
version conflicts with projects that have pbr <2.0.0 caps *anyway* regardless
of what hacking says right?

So removing the pbr cap in hacking doesn't make things worse for stable
branches but it does make things better for master?

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Tony Breeds]

On Thu, Mar 02, 2017 at 05:01:43PM +1100, Tony Breeds wrote:

> And yes there are now plenty of pep8 jobs that are failing with PBR 2.0.0
> 
> We can't revert the requirements change that landed which means that projects
> using old hacking versions are going to need an update :(

One option may be to release 0.10.3 of hacking that removes the cap on pbr.  I
think this would fix the issues on master but I *think* it will cause problems
on ,at least, stable/mitaka where 0.10.x is still the preferred version.

For projects that have constraints support things will be fine as the version
selected for PBR will come from upper-constraints.txt and hacking from
requirements so those projects will get pbr == 1.8.1 and hacking 0.10.3 
#winning.

For projects that don't have constraints support which is still quite a few[1]
they'll end up with pbr 2.0.0 which will almost certainly break things.
Probably not in behaviour but more likely with similar VersionConflicts.

Yours Tony.

[1] http://lists.openstack.org/pipermail/openstack-dev/2017-March/113175.html


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Tony Breeds]

On Thu, Mar 02, 2017 at 04:41:14PM +1100, Tony Breeds wrote:
> On Thu, Mar 02, 2017 at 03:48:05PM +1100, Ian Wienand wrote:
> > On 03/02/2017 01:13 AM, Doug Hellmann wrote:
> > > Tony identified caps in 5 OpenStack community projects (see [1]) as well
> > > as powervm and python-jsonpath-rw-ext. Pull requests to those other
> > > projects are linked from the bug [2].
> > 
> > > [1] https://review.openstack.org/#/q/topic:bug/1668848
> > 
> > Am I nuts or was pbr itself the only one forgotten?
> 
> Your quite right.  That points out that there are probably lots of repos still
> with an old hacking that need to be updated.

And yes there are now plenty of pep8 jobs that are failing with PBR 2.0.0

We can't revert the requirements change that landed which means that projects
using old hacking versions are going to need an update :(

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Tony Breeds]

On Thu, Mar 02, 2017 at 03:48:05PM +1100, Ian Wienand wrote:
> On 03/02/2017 01:13 AM, Doug Hellmann wrote:
> > Tony identified caps in 5 OpenStack community projects (see [1]) as well
> > as powervm and python-jsonpath-rw-ext. Pull requests to those other
> > projects are linked from the bug [2].
> 
> > [1] https://review.openstack.org/#/q/topic:bug/1668848
> 
> Am I nuts or was pbr itself the only one forgotten?

Your quite right.  That points out that there are probably lots of repos still
with an old hacking that need to be updated.

/me goes to write a script that check that thing.

> I filed
> 
>  https://review.openstack.org/#/c/440010
> 
> under the same topic

Thanks

Yours Tony.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Ian Wienand]

On 03/02/2017 01:13 AM, Doug Hellmann wrote:

Tony identified caps in 5 OpenStack community projects (see [1]) as well
as powervm and python-jsonpath-rw-ext. Pull requests to those other
projects are linked from the bug [2].



[1] https://review.openstack.org/#/q/topic:bug/1668848


Am I nuts or was pbr itself the only one forgotten?

I filed

 https://review.openstack.org/#/c/440010

under the same topic

-i

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Matt Riedemann]

On 3/1/2017 8:13 AM, Doug Hellmann wrote:

Excerpts from Sean Dague's message of 2017-03-01 07:57:31 -0500:

On 03/01/2017 12:26 AM, Tony Breeds wrote:

Hi All,
Earlier today the release team tagged PBR 2.0.0.  The reason for the major
version bump is because warnerrors has been removed in favor of
warning-is-error from sphinx >= 1.5.0.

It seems that several projects outside both inside and outside OpenStack have
capped pbr <2.0.0 so we can't actually use this release yet.  The requirements
team will work with all projects to remove the cap of pbr in those projects.

The good news is that projects using upper-constraints.txt are insulated from
this and shouldn't be affected[1].  However upper-constraints.txt isn't being 
used
by all projects and *those* projects will start seeing

ContextualVersionConflicts: (pbr 2.0.0 in gate logs.  It's recommended that
those projects add a local ban for pbr and associate it with:
https://bugs.launchpad.net/openstack-requirements/+bug/1668848

Then once the situation is resolved we can unwind and remove the temporary caps.

Yours Tony.

[1] There is at least 1 corner case where the coverage job installed directly
from a git URL and therefore that wasn't protected.


So, I feel like we hit a similar issue around Vancouver with a pbr bump.
Can we stop capping pbr per rule now?


Tony identified caps in 5 OpenStack community projects (see [1]) as well
as powervm and python-jsonpath-rw-ext. Pull requests to those other
projects are linked from the bug [2].

The sqlalchemy-migrate 0.11.0 release should fix that library. The
release team will prioritize releases for the other dependencies today
as they come in.

Doug

[1] https://review.openstack.org/#/q/topic:bug/1668848
[2] https://bugs.launchpad.net/openstack-requirements/+bug/1668848

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



nova-specs was also broken, the fix is here for anyone that needs to 
recheck or rebase nova-specs changes:


https://review.openstack.org/#/c/439878/

--

Thanks,

Matt Riedemann

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Tim Burke]

On Mar 1, 2017, at 4:57 AM, Sean Dague  wrote:

> I also wonder if we can grant the release team +2 permissions on
> everything in OpenStack so that fixes like this can be gotten in quickly
> without having to go chase a bunch of teams.

I would be very much opposed to this. Isn't this why we have cross-project 
liaisons, defaulting back to the PTLs? Ultimately, project teams need to own 
the change and its repercussions. As we've seen with things like eventlet, 
requirements changes have ripple effects, and the project teams are best-suited 
to foresee those consequences within their own domain.

Tim__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Davanum Srinivas]

On Wed, Mar 1, 2017 at 2:12 PM, Doug Hellmann  wrote:
> Excerpts from Doug Hellmann's message of 2017-03-01 14:04:19 -0500:
>> Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100:
>> > On 2017-03-01 17:13, Doug Hellmann  wrote:
>> > > Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
>> > >> On 2017-03-01 06:26, Tony Breeds  wrote:
>> > >>> Hi All,
>> > >>> Earlier today the release team tagged PBR 2.0.0.  The reason for 
>> > >>> the major
>> > >>> version bump is because warnerrors has been removed in favor of
>> > >>> warning-is-error from sphinx >= 1.5.0.
>> > >>
>> > >> Can we change the sphinx==1.3.6 line in upper-constraints now?
>> > >
>> > > We're currently running into failures updating requirements because of
>> > > the pbr cap in several libraries.
>> > >
>> > > I see requestsexceptions, sqlalchemy-migrate, yaql, fairy-slipper,
>> > > pypowervm, gnocchiclient, reno, and aodhclient mentioned in
>> > > http://logs.openstack.org/88/439588/2/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/97625f3/console.html
>> > > for example.
>> > >
>> > > I'm working on reno right now.
>> >
>> > thanks
>> >
>> > fairy-slipper is retired, let's remove it -
>> > https://review.openstack.org/439769
>> >
>> > Andreas
>>
>> Based on the nature of the failures, I think we're going to have to get
>> releases of all of the other projects up, and then prepare one patch in
>> the requirements repo to update constraints all at one time.
>>
>> Doug
>
> Most of the projects involved are trying to take action, but I haven't
> seen any updates on the pypowervm pull request in
> https://github.com/powervm/pypowervm/pull/1
>
> Can someone contact that team and ask them to merge it and push a new
> release?

Done. over on #openstack-nova

[11:40:49]  thorst : Anyone around to merge this PR and cut a
release for pypowervm? https://github.com/powervm/pypowervm/pull/1
[11:41:20]  dims: Yeah, we're working on getting a new rev of
that.  It'd be pypowervm 1.0.0.4.1 to take in the new req.  adreznec
is working on it.
[11:41:32]  great thanks thorst and adreznec
[11:41:42]  dims: thorst Yep, just working on that now
[11:41:44]  thx for letting us know!


>
> Doug
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Davanum Srinivas :: https://twitter.com/dims

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Doug Hellmann]

Excerpts from Doug Hellmann's message of 2017-03-01 14:04:19 -0500:
> Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100:
> > On 2017-03-01 17:13, Doug Hellmann  wrote:
> > > Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
> > >> On 2017-03-01 06:26, Tony Breeds  wrote:
> > >>> Hi All,
> > >>> Earlier today the release team tagged PBR 2.0.0.  The reason for 
> > >>> the major
> > >>> version bump is because warnerrors has been removed in favor of
> > >>> warning-is-error from sphinx >= 1.5.0.
> > >>
> > >> Can we change the sphinx==1.3.6 line in upper-constraints now?
> > > 
> > > We're currently running into failures updating requirements because of
> > > the pbr cap in several libraries.
> > > 
> > > I see requestsexceptions, sqlalchemy-migrate, yaql, fairy-slipper,
> > > pypowervm, gnocchiclient, reno, and aodhclient mentioned in
> > > http://logs.openstack.org/88/439588/2/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/97625f3/console.html
> > > for example.
> > > 
> > > I'm working on reno right now.
> > 
> > thanks
> > 
> > fairy-slipper is retired, let's remove it -
> > https://review.openstack.org/439769
> > 
> > Andreas
> 
> Based on the nature of the failures, I think we're going to have to get
> releases of all of the other projects up, and then prepare one patch in
> the requirements repo to update constraints all at one time.
> 
> Doug

Most of the projects involved are trying to take action, but I haven't
seen any updates on the pypowervm pull request in
https://github.com/powervm/pypowervm/pull/1

Can someone contact that team and ask them to merge it and push a new
release?

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Doug Hellmann]

Excerpts from Andreas Jaeger's message of 2017-03-01 19:50:51 +0100:
> On 2017-03-01 17:13, Doug Hellmann  wrote:
> > Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
> >> On 2017-03-01 06:26, Tony Breeds  wrote:
> >>> Hi All,
> >>> Earlier today the release team tagged PBR 2.0.0.  The reason for the 
> >>> major
> >>> version bump is because warnerrors has been removed in favor of
> >>> warning-is-error from sphinx >= 1.5.0.
> >>
> >> Can we change the sphinx==1.3.6 line in upper-constraints now?
> > 
> > We're currently running into failures updating requirements because of
> > the pbr cap in several libraries.
> > 
> > I see requestsexceptions, sqlalchemy-migrate, yaql, fairy-slipper,
> > pypowervm, gnocchiclient, reno, and aodhclient mentioned in
> > http://logs.openstack.org/88/439588/2/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/97625f3/console.html
> > for example.
> > 
> > I'm working on reno right now.
> 
> thanks
> 
> fairy-slipper is retired, let's remove it -
> https://review.openstack.org/439769
> 
> Andreas

Based on the nature of the failures, I think we're going to have to get
releases of all of the other projects up, and then prepare one patch in
the requirements repo to update constraints all at one time.

Doug

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Andreas Jaeger]

On 2017-03-01 17:13, Doug Hellmann  wrote:
> Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
>> On 2017-03-01 06:26, Tony Breeds  wrote:
>>> Hi All,
>>> Earlier today the release team tagged PBR 2.0.0.  The reason for the 
>>> major
>>> version bump is because warnerrors has been removed in favor of
>>> warning-is-error from sphinx >= 1.5.0.
>>
>> Can we change the sphinx==1.3.6 line in upper-constraints now?
> 
> We're currently running into failures updating requirements because of
> the pbr cap in several libraries.
> 
> I see requestsexceptions, sqlalchemy-migrate, yaql, fairy-slipper,
> pypowervm, gnocchiclient, reno, and aodhclient mentioned in
> http://logs.openstack.org/88/439588/2/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/97625f3/console.html
> for example.
> 
> I'm working on reno right now.

thanks

fairy-slipper is retired, let's remove it -
https://review.openstack.org/439769

Andreas
-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Doug Hellmann]

Excerpts from Andreas Jaeger's message of 2017-03-01 16:22:24 +0100:
> On 2017-03-01 06:26, Tony Breeds  wrote:
> > Hi All,
> > Earlier today the release team tagged PBR 2.0.0.  The reason for the 
> > major
> > version bump is because warnerrors has been removed in favor of
> > warning-is-error from sphinx >= 1.5.0.
> 
> Can we change the sphinx==1.3.6 line in upper-constraints now?

We're currently running into failures updating requirements because of
the pbr cap in several libraries.

I see requestsexceptions, sqlalchemy-migrate, yaql, fairy-slipper,
pypowervm, gnocchiclient, reno, and aodhclient mentioned in
http://logs.openstack.org/88/439588/2/check/gate-requirements-tox-py27-check-uc-ubuntu-xenial/97625f3/console.html
for example.

I'm working on reno right now.

Doug

> 
> Andreas
> 
> > It seems that several projects outside both inside and outside OpenStack 
> > have
> > capped pbr <2.0.0 so we can't actually use this release yet.  The 
> > requirements
> > team will work with all projects to remove the cap of pbr in those projects.
> > 
> > The good news is that projects using upper-constraints.txt are insulated 
> > from
> > this and shouldn't be affected[1].  However upper-constraints.txt isn't 
> > being used
> > by all projects and *those* projects will start seeing
> > 
> > ContextualVersionConflicts: (pbr 2.0.0 in gate logs.  It's recommended that
> > those projects add a local ban for pbr and associate it with:
> > https://bugs.launchpad.net/openstack-requirements/+bug/1668848
> > 
> > Then once the situation is resolved we can unwind and remove the temporary 
> > caps.
> > 
> > Yours Tony.
> > 
> > [1] There is at least 1 corner case where the coverage job installed 
> > directly
> > from a git URL and therefore that wasn't protected.
> > 
> > 
> > 
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > 
> 

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Andreas Jaeger]

On 2017-03-01 06:26, Tony Breeds  wrote:
> Hi All,
> Earlier today the release team tagged PBR 2.0.0.  The reason for the major
> version bump is because warnerrors has been removed in favor of
> warning-is-error from sphinx >= 1.5.0.

Can we change the sphinx==1.3.6 line in upper-constraints now?

Andreas

> It seems that several projects outside both inside and outside OpenStack have
> capped pbr <2.0.0 so we can't actually use this release yet.  The requirements
> team will work with all projects to remove the cap of pbr in those projects.
> 
> The good news is that projects using upper-constraints.txt are insulated from
> this and shouldn't be affected[1].  However upper-constraints.txt isn't being 
> used
> by all projects and *those* projects will start seeing
> 
> ContextualVersionConflicts: (pbr 2.0.0 in gate logs.  It's recommended that
> those projects add a local ban for pbr and associate it with:
> https://bugs.launchpad.net/openstack-requirements/+bug/1668848
> 
> Then once the situation is resolved we can unwind and remove the temporary 
> caps.
> 
> Yours Tony.
> 
> [1] There is at least 1 corner case where the coverage job installed directly
> from a git URL and therefore that wasn't protected.
> 
> 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


-- 
 Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi
  SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
   GF: Felix Imendörffer, Jane Smithard, Graham Norton,
   HRB 21284 (AG Nürnberg)
GPG fingerprint = 93A3 365E CE47 B889 DF7F  FED1 389A 563C C272 A126


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Doug Hellmann]

Excerpts from Sean Dague's message of 2017-03-01 07:57:31 -0500:
> On 03/01/2017 12:26 AM, Tony Breeds wrote:
> > Hi All,
> > Earlier today the release team tagged PBR 2.0.0.  The reason for the 
> > major
> > version bump is because warnerrors has been removed in favor of
> > warning-is-error from sphinx >= 1.5.0.
> > 
> > It seems that several projects outside both inside and outside OpenStack 
> > have
> > capped pbr <2.0.0 so we can't actually use this release yet.  The 
> > requirements
> > team will work with all projects to remove the cap of pbr in those projects.
> > 
> > The good news is that projects using upper-constraints.txt are insulated 
> > from
> > this and shouldn't be affected[1].  However upper-constraints.txt isn't 
> > being used
> > by all projects and *those* projects will start seeing
> > 
> > ContextualVersionConflicts: (pbr 2.0.0 in gate logs.  It's recommended that
> > those projects add a local ban for pbr and associate it with:
> > https://bugs.launchpad.net/openstack-requirements/+bug/1668848
> > 
> > Then once the situation is resolved we can unwind and remove the temporary 
> > caps.
> > 
> > Yours Tony.
> > 
> > [1] There is at least 1 corner case where the coverage job installed 
> > directly
> > from a git URL and therefore that wasn't protected.
> 
> So, I feel like we hit a similar issue around Vancouver with a pbr bump.
> Can we stop capping pbr per rule now?

Tony identified caps in 5 OpenStack community projects (see [1]) as well
as powervm and python-jsonpath-rw-ext. Pull requests to those other
projects are linked from the bug [2].

The sqlalchemy-migrate 0.11.0 release should fix that library. The
release team will prioritize releases for the other dependencies today
as they come in.

Doug

[1] https://review.openstack.org/#/q/topic:bug/1668848
[2] https://bugs.launchpad.net/openstack-requirements/+bug/1668848

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Hayes, Graham]

On 01/03/2017 13:00, Sean Dague wrote:
> On 03/01/2017 12:26 AM, Tony Breeds wrote:
>> Hi All,
>> Earlier today the release team tagged PBR 2.0.0.  The reason for the 
>> major
>> version bump is because warnerrors has been removed in favor of
>> warning-is-error from sphinx >= 1.5.0.
>>
>> It seems that several projects outside both inside and outside OpenStack have
>> capped pbr <2.0.0 so we can't actually use this release yet.  The 
>> requirements
>> team will work with all projects to remove the cap of pbr in those projects.
>>
>> The good news is that projects using upper-constraints.txt are insulated from
>> this and shouldn't be affected[1].  However upper-constraints.txt isn't 
>> being used
>> by all projects and *those* projects will start seeing
>>
>> ContextualVersionConflicts: (pbr 2.0.0 in gate logs.  It's recommended that
>> those projects add a local ban for pbr and associate it with:
>> https://bugs.launchpad.net/openstack-requirements/+bug/1668848
>>
>> Then once the situation is resolved we can unwind and remove the temporary 
>> caps.
>>
>> Yours Tony.
>>
>> [1] There is at least 1 corner case where the coverage job installed directly
>> from a git URL and therefore that wasn't protected.
>
> So, I feel like we hit a similar issue around Vancouver with a pbr bump.
> Can we stop capping pbr per rule now?
>
> I also wonder if we can grant the release team +2 permissions on
> everything in OpenStack so that fixes like this can be gotten in quickly
> without having to go chase a bunch of teams.

That sounds like a good idea to me.

>   -Sean
>


__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Sean Dague]

On 03/01/2017 12:26 AM, Tony Breeds wrote:
> Hi All,
> Earlier today the release team tagged PBR 2.0.0.  The reason for the major
> version bump is because warnerrors has been removed in favor of
> warning-is-error from sphinx >= 1.5.0.
> 
> It seems that several projects outside both inside and outside OpenStack have
> capped pbr <2.0.0 so we can't actually use this release yet.  The requirements
> team will work with all projects to remove the cap of pbr in those projects.
> 
> The good news is that projects using upper-constraints.txt are insulated from
> this and shouldn't be affected[1].  However upper-constraints.txt isn't being 
> used
> by all projects and *those* projects will start seeing
> 
> ContextualVersionConflicts: (pbr 2.0.0 in gate logs.  It's recommended that
> those projects add a local ban for pbr and associate it with:
> https://bugs.launchpad.net/openstack-requirements/+bug/1668848
> 
> Then once the situation is resolved we can unwind and remove the temporary 
> caps.
> 
> Yours Tony.
> 
> [1] There is at least 1 corner case where the coverage job installed directly
> from a git URL and therefore that wasn't protected.

So, I feel like we hit a similar issue around Vancouver with a pbr bump.
Can we stop capping pbr per rule now?

I also wonder if we can grant the release team +2 permissions on
everything in OpenStack so that fixes like this can be gotten in quickly
without having to go chase a bunch of teams.

-Sean

-- 
Sean Dague
http://dague.net

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [all] PBR 2.0.0 release *may* cause gate failures

[Tony Breeds]

Hi All,
Earlier today the release team tagged PBR 2.0.0.  The reason for the major
version bump is because warnerrors has been removed in favor of
warning-is-error from sphinx >= 1.5.0.

It seems that several projects outside both inside and outside OpenStack have
capped pbr <2.0.0 so we can't actually use this release yet.  The requirements
team will work with all projects to remove the cap of pbr in those projects.

The good news is that projects using upper-constraints.txt are insulated from
this and shouldn't be affected[1].  However upper-constraints.txt isn't being 
used
by all projects and *those* projects will start seeing

ContextualVersionConflicts: (pbr 2.0.0 in gate logs.  It's recommended that
those projects add a local ban for pbr and associate it with:
https://bugs.launchpad.net/openstack-requirements/+bug/1668848

Then once the situation is resolved we can unwind and remove the temporary caps.

Yours Tony.

[1] There is at least 1 corner case where the coverage job installed directly
from a git URL and therefore that wasn't protected.


signature.asc
Description: PGP signature
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev