Tuesday, 2017-03-14

*** jamielennox is now known as jamielennox|away00:58
*** jamielennox|away is now known as jamielennox01:12
*** gouthamr has quit IRC02:33
*** yfried has joined #openstack-shade06:00
yfriedhi, I'm having trouble with shade requirements for the last week06:30
yfriedanyone seeing something similar?06:30
yfriedanyone seeing issues with shade and pbr?06:42
*** yfried has quit IRC08:27
*** yfried has joined #openstack-shade08:27
*** ioggstream has joined #openstack-shade08:37
*** yolanda has quit IRC08:37
*** yolanda has joined #openstack-shade08:42
*** cdent has joined #openstack-shade11:09
*** ioggstream has quit IRC11:23
*** Matias_ has quit IRC11:44
*** Matias_ has joined #openstack-shade11:45
*** gouthamr has joined #openstack-shade12:52
-openstackstatus- NOTICE: Gerrit is going to be restarted due to performance problems13:41
*** ChanServ changes topic to "Gerrit is going to be restarted due to performance problems"13:41
*** yfried has quit IRC13:45
-openstackstatus- NOTICE: Gerrit has been successfully restarted13:47
*** ChanServ changes topic to "Gerrit has been successfully restarted"13:47
*** ChanServ changes topic to "Gerrit is going to be restarted due to performance problems"13:53
-openstackstatus- NOTICE: Gerrit has been successfully restarted13:53
*** IRCFrEAK has joined #openstack-shade14:12
*** IRCFrEAK has quit IRC14:14
*** yfried has joined #openstack-shade15:33
clarkbyfried: possibly you are caught in the release of pbr 2.0 if shade has/had a pin for <2.015:38
clarkbyfried: are you using latest shade?15:38
yfriedclarkb: "pip install shade"15:44
yfriedclarkb: I saw a recent fix was merged. when will it be released?15:44
clarkbyfried: https://git.openstack.org/cgit/openstack-infra/shade/tree/requirements.txt?h=1.16.0&id=6ff03db0a8f71781645111f2de664d2bfaf25aca ya that has the pin and thats the last commit that was tagged15:45
clarkbmordred: ^ you'll want to make a shade release soon/now to fix the pbr issue15:45
yfriedclarkb: mordred: yes please15:45
yfriedwe had a pretty bad week due to this bug15:46
yfriedI've been getting angry demands to drop shade from our project15:48
clarkbyfried: a simple workaround is to install pip<2.0 first15:49
clarkber15:49
clarkbpbr<2.015:49
yfriedclarkb: not helping15:50
yfriedclarkb: clients will later kill the command line due to conflicts15:50
clarkbyfried: the clients should still work with older pbr though15:51
* clarkb is testing locally really quick15:51
clarkbyfried: yes worked fine locally15:51
clarkbpip install 'pbr<2.0' && pip install shade15:51
yfriedclarkb: we have a CLI tool and it's entrypoint is validating deps15:51
clarkbyfried: yes pbr 1.x is a valid dep15:52
clarkbnothing has a pbr >2.0 pin15:52
clarkb(or if it does thats a new bug15:52
yfriedclarkb: https://github.com/openstack/python-cinderclient/blob/master/requirements.txt#L415:53
clarkbugh15:53
* clarkb cries15:53
yfriedclarkb: we've had several like this15:53
clarkbI guess thats how we "fixed" things15:54
yfriedclarkb: basically, any new openstack pkg release is now killing us15:54
clarkbdhellmann: FYI ^ that was probably the wrong way to fix pbr15:54
clarkbdhellmann: since it means there is no range that straddles the old and new working sets with pbr15:54
dhellmann?15:54
* dhellmann reads scrollback15:54
clarkbdhellmann: tldr is when we had pbr 2.0 release we should only have removed the upper pin on PBR not also moved the lower pin to be >= 2.015:54
dhellmannyeah, we were just discussing whether we needed to remove the cap on pbr in stable/ocata15:55
clarkbdhellmann: yes the cap should be removed everywhere imo15:55
clarkbbut the lower bound should never have been pushed up to >= 2.015:55
yfriedclarkb: https://storyboard.openstack.org/#!/story/200091515:55
dhellmannI raised it in #openstack-requirements but most of that team seems to be offline atm and I didn't want to take any action without consulting them15:55
clarkbdhellmann: because now you either work with 1.x on old code XOR work with 2.x on new code15:55
dhellmannyeah, I don't think there's really any reason we needed to update to >=2.015:56
clarkbideally we would hvae let new code work with 1.x too to avoid the problem yfried is running into15:57
dhellmannoh, except some projects wanted to start using the sphinx warning setting, and I'm not sure if earlier versions of pbr passed that through properly15:57
clarkbdhellmann: it doesn't matter for testing though15:57
clarkbsince testing will always install latest15:57
clarkb(if this was a functional issue for installations then ya I would worry about it)15:57
dhellmannwe can try resetting that lower bound.15:57
dhellmannwe don't really have a good way to signal the expected version of pbr other than the g-r list, though, do we? it's not constrained.15:58
clarkbcorrect, you can't really constrain it because setup.py pulls it in as an install requires15:58
clarkbyfried: fwiw this issue affected all of openstack so dropping shade wouldn't have completely avoided the problem for you15:59
yfriedclarkb: shouldn't shade req be managed by global req?15:59
clarkbyfried: I'm not sure but thats orthogonal, pbr isn't managed by constraints and isn't really even managed by g-r16:00
clarkbsince pbr is an install requires it happens outside of all that managment16:00
yfriedclarkb: I don't want to drop shade, it's key for our ansible works, but I have some opposition...16:00
clarkb(which is why we had problems with the 2.0 release)16:00
dhellmanncan we not just release a version of shade that doesn't have the cap?16:02
clarkbdhellmann: we can and thats likely the simple fix. I just wanted to make sure release team saw that bumping up lower bound was problematic16:03
clarkbwe really need to have ranges that overlap when making these transitions16:03
dhellmannyeah16:03
yfriedclarkb: so, what's the ETA on a working shade?16:13
clarkbyfried: I'd have to defer to mordred on that. I don't know what the current delta is between HEAD and previous release16:14
yfriedmordred: ?16:15
clarkbyou can propose the change to the requirements repo as a start16:16
clarkber releases repo16:16
yfriedclarkb: sorry?16:37
yfriedclarkb: what is this?16:37
clarkbyfried: well I thought that shade was managed by the release team but I'm not seeing it in the releases repo16:38
clarkbyfried: much of openstack releases are managed by the openstack/releases repo. You push metadata there then automated jobs created tags and do release things16:38
clarkbbut doesn't look like shade is there so mordred would ideally make the tag and push it (on whatever commit is most appropriate)16:39
*** mgagne_ is now known as mgagne18:05
*** Matias_ has quit IRC20:32
Shrewsyup, mordred is the only one that has the shade release powerz20:50
openstackgerritMorgan Fainberg proposed openstack-infra/shade master: change test_endpoints to use requests mock  https://review.openstack.org/44454121:21
*** gouthamr has quit IRC21:25
notmorganmordred: sigh...21:55
notmorganmordred: so yeah endpoints are about the sloppiest junk in keystone21:55
notmorganmordred: looks like v2 is region, v3 is region *and* region_id and that looks like it's a typo and should have only been region_id21:56
notmorganalso the api-spec says region_id.21:56
*** cdent has quit IRC21:57
openstackgerritMorgan Fainberg proposed openstack-infra/shade master: change test_endpoints to use requests mock  https://review.openstack.org/44454122:01
*** gouthamr has joined #openstack-shade22:18
openstackgerritMorgan Fainberg proposed openstack-infra/shade master: Convert simple role crud to requests mock  https://review.openstack.org/44567322:32
*** ChanServ changes topic to "#openstack-shade"22:42

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!