Friday, 2016-07-15

prometheanfiretonyb: can you +w this https://review.openstack.org/34234400:04
prometheanfiretonyb: it's blocking everything in requirements00:04
*** coolsvap has joined #openstack-requirements00:28
coolsvapprometheanfire, hey00:44
prometheanfirecoolsvap: thanks :D00:44
coolsvapthanks for?00:45
coolsvapprometheanfire, you could have acked https://review.openstack.org/#/c/342344/00:46
patchbotcoolsvap: patch 342344 - requirements - Remove mistral-extra from projects list00:46
prometheanfirecoolsvap: I did...00:48
coolsvapprometheanfire, W+ i meant00:48
prometheanfireI was going to +W it if no one responded by the time I slept00:48
coolsvapoh ok00:48
prometheanfire:D00:48
prometheanfireI'd rather do it right if possible00:49
coolsvapyes00:49
coolsvapwe need better handling of projects removing requirements jobs00:50
prometheanfireya, it's annoying, odyssey4me was saying that we doc the need to order the removal, but project-config doesn't00:51
prometheanfirewell addition/removal00:51
prometheanfirenot that I think that'd help much, at least at first00:51
prometheanfireit's just not something people think about much00:52
coolsvapsince we have voting gate on it is00:53
prometheanfirecross project gates could be nice :P00:53
coolsvaphaha yes but still we might need some intelligence in our gates to handle this kinda situation00:54
prometheanfirewell, the error was fairly obvious, so the bot that says this is a known bug could help maybe00:55
coolsvapon the other hand i think it is better as it is, just we need better watch and documentation in project-config00:57
prometheanfireya01:14
coolsvapprometheanfire, i think we are good for https://review.openstack.org/341323/ today's results look good01:21
coolsvapstill waiting for couple of projects jenkins jobs01:21
prometheanfireya, was thinking so01:24
prometheanfirehave been watching01:25
openstackgerritMerged openstack/requirements: Remove mistral-extra from projects list  https://review.openstack.org/34234401:33
coolsvapnova is still not happy01:53
coolsvapprometheanfire, https://review.openstack.org/#/c/341323/02:38
patchbotcoolsvap: patch 341323 - requirements - Updated from generate-constraints02:38
coolsvapand https://review.openstack.org/#/c/341509/02:39
patchbotcoolsvap: patch 341509 - requirements - Add all openstack-ansible repositories to projects...02:39
prometheanfirecoolsvap: nova not happy?02:41
prometheanfireso why +2?02:41
coolsvapprometheanfire, nova failures do not entirely seem related to u-c02:47
coolsvaplet me confirm have you seen logs http://logs.openstack.org/45/303345/155/check/gate-nova-python27-db/70e814a/console.html02:48
coolsvapsimilar tests have been passed in glance & designate02:54
tonybLooks like oslo.context broke nova to me.  Tracking back the change to see if it was intentional03:00
prometheanfiretonyb: oh, nice03:02
prometheanfireiirc context broke things recently03:02
tonybIe48fedb8092e33e9645a37ea3fe44b88d34ad3b8 broke it03:02
tonybbnow to work out how to handle that ...03:02
prometheanfirewhich review is that?03:03
coolsvapin trove03:03
prometheanfireah03:03
tonybthat Change ID is in oslo.context03:04
coolsvaptonyb, https://review.openstack.org/#/c/341543/03:05
patchbotcoolsvap: patch 341543 - requirements - update constraint for oslo.context to new release ...03:05
prometheanfireya, was reading that03:06
tonybright.03:06
coolsvapso there was a request expedite since trove was broken03:06
tonybso we can't expidite it03:06
coolsvaphmm yes03:06
prometheanfireya, unreviewed and rechecked03:06
coolsvapprometheanfire, recheck will not provide any different update afaics03:07
prometheanfireI thought it was failing because of the projects thing03:08
coolsvapprometheanfire, this is failing https://review.openstack.org/#/c/303345/03:09
patchbotcoolsvap: patch 303345 - nova - [WIP] Testing latest u-c03:09
prometheanfireI get that03:10
tonybSo we need to find and example of the trove failure to verify that u-c will fix them03:11
tonybcan eitehr of you look for that?03:11
tonybI'll try to work out how to handle this in nova03:11
prometheanfireok03:12
coolsvapsure03:12
tonybThis will probably come up if other projects are doign very careful checking of the context03:12
tonybAlso https://review.openstack.org/#/c/335549/7 "#winner of bext commit message ever"03:15
patchbottonyb: patch 335549 - nova - DO NOT MERGE - ROOAAAAAARRRR ! Testing live migrat...03:15
prometheanfirelol03:15
prometheanfirehttps://review.openstack.org/342509 should be failing soon in trove03:18
prometheanfireand is a small change, so should work as a good test for us03:18
coolsvaptrove failures are mostly due to versioning03:19
coolsvaphttp://logs.openstack.org/09/342509/1/check/gate-trove-python34-db/643e2f8/console.html#_2016-07-15_02_07_21_38306803:19
tonybcoolsvap: Are you sure those are releasted to the context change?03:22
prometheanfire2016-07-15 02:07:22.220766 | oslo.context==2.5.0  # git sha 061741203:22
prometheanfirecontext change is 2.6.0 I thought03:22
coolsvapso tonyb there are couple of changes submitted in nova03:23
coolsvaprelated to the oslo.context change03:23
coolsvaphttps://review.openstack.org/34190503:23
coolsvaphttps://review.openstack.org/#/c/340195/03:23
patchbotcoolsvap: patch 340195 - cinder - Use to_policy_values for enforcing policy03:23
coolsvapprometheanfire, trove will not have 2.6.003:24
prometheanfirelet me get this straigt then03:25
prometheanfireoslo.context updated, adding a value03:25
prometheanfirethis caused nova to fail03:25
prometheanfirenot sure what to do about trove, why is it failing03:26
tonybprometheanfire: (when using the new 2.6.0 release)03:26
prometheanfiretonyb: trove?03:26
prometheanfireor nova03:26
coolsvaphttps://bugs.launchpad.net/neutron/+bug/160208103:26
openstackLaunchpad bug 1602081 in OpenStack Compute (nova) "Use oslo.context's policy dict" [Undecided,In progress] - Assigned to Jamie Lennox (jamielennox)03:26
tonybprometheanfire: All O knwo abotu trove is: Any chance we could expedite this change?  The Trove gate is broken since we don't use upper-contraints when we build our guest image so there's now an API mismatch ...03:27
prometheanfireya03:27
prometheanfireoh, I didn't see that second part03:27
prometheanfireafter 'since'03:27
prometheanfireok03:27
tonybprometheanfire: which matches the log that coolsvap posted but it lacks details to work out which version of oslo.context is the problem03:27
prometheanfirean error on their part is not an emergency on ours03:28
prometheanfireso, focusing on nova et all...03:28
tonybprometheanfire: Right but we have to balance the needs of trove, nova, oslo and keystone here03:28
prometheanfireright03:28
coolsvaptonyb, yes the trove failures are not sufficient to relate to oslo.context03:28
tonybso undertanding *excatly* what has broken in trove will help us to fix it in nova03:29
prometheanfiretonyb: from the sounds of it, it was the introduction of the new policy value (as far as nova/neutron go)03:30
tonybprometheanfire: neutron?03:31
prometheanfiresorry, the bug03:31
prometheanfirehttps://bugs.launchpad.net/neutron/+bug/160208103:31
openstackLaunchpad bug 1602081 in OpenStack Compute (nova) "Use oslo.context's policy dict" [Undecided,In progress] - Assigned to Jamie Lennox (jamielennox)03:31
coolsvaptonyb, the bug cross-project03:32
coolsvaphttp://logs.openstack.org/36/318436/53/check/gate-glance-python34-db/4441178/console.html#_2016-07-14_10_15_15_25904103:33
tonybcoolsvap: okay, that bug report is a feature/bp tracker not an actual things went bad when .... bug reports03:33
prometheanfireright, related though, tangentially03:33
tonybprometheanfire: Sure it describes what keystone need to do and how they'er doing it.03:33
prometheanfirecoolsvap: the result is success there03:35
coolsvapyes03:35
prometheanfireok?03:35
coolsvapbut http://logs.openstack.org/45/303345/155/check/gate-nova-python27-db/70e814a/console.html#_2016-07-15_00_41_17_16545103:36
coolsvapit seems like a false success in glance :/03:37
openstackgerritMerged openstack/requirements: Block futurist 0.15.0  https://review.openstack.org/34244703:38
tonybokay so I have a hack for nova03:39
prometheanfirecoolsvap: so, it seems like what happened is that context 2.6.0 added a value that breaks things before downstream consumers could consume03:40
tonybcoolsvap: or they're not as 'detailed' in what a context shoudl look like03:40
tonybprometheanfire: more or less yes03:40
prometheanfirewhy is https://review.openstack.org/#/c/341905/ not good then (at least to fix nova)03:40
patchbotprometheanfire: patch 341905 - nova - Use to_policy_values for policy credentials03:40
prometheanfireif we don't want to wait for projects to fix themselves we can mask (temp)03:40
tonybprometheanfire: becuse that's workin on polcu from context not the context itself03:41
prometheanfireso it requires the new context to work?03:41
prometheanfirehttps://review.openstack.org/#/c/341895/ too03:42
patchbotprometheanfire: patch 341895 - nova - Pass kwargs through to base context03:42
tonybso we need to a) idetify projects that break with 2.6.0 ; b) add shims to them to work with 2.5.0 and 2.6.0 ; c) merge the 2.6.0 u-c change ; d) bump the minium in g-r to 2.6.0 and e) remove items from 'a'03:42
tonybprometheanfire: I'll tidy up my hack and publish ASAP03:44
tonybwe still need to grok the trove breakage but that's less critical03:44
prometheanfirewe can also a) idetify projects that break with 2.6.0; b) mask 2.6.0; c) add shims to them to work with 2.5.0 and 2.6.0; d) unmask 2.6.0 and bump gr/uc03:44
tonybprometheanfire: Ummm what does "mask 2.6.0" mean?03:46
openstackgerritMerged openstack/requirements: Add all openstack-ansible repositories to projects.txt  https://review.openstack.org/34150903:46
prometheanfiretonyb: sorry, gentoo speak03:47
prometheanfireadd !=2.6.0 to oslo.context in gr03:47
tonybprometheanfire: Sure we can do that but my gut tells me it wont work03:49
prometheanfirethe only reason I advocate for it is that it will unbreak things quicker03:50
prometheanfireI haven't seen any ml activity about the oslo.context breakage, should we start one asking?03:50
prometheanfireI'm not sure about your gut :P03:50
* coolsvap brb03:52
tonybprometheanfire: We shoudl probably say something on the m/l  I'll do it after I finish this nova patch03:54
tonybprometheanfire: I'll also ponder the masking approach try to undertsand what my gut is saying ... it could be I need lunch03:55
prometheanfireit's a bit late here, brushing teeth now :P03:56
prometheanfireit's why I'm a bit thick atm03:56
tonybprometheanfire: rest well04:07
coolsvapprometheanfire, see you tomorrow04:08
coolsvaptonyb, yes let us know once you do04:08
prometheanfirelol04:08
prometheanfireI'm not dead yet04:08
coolsvapprometheanfire, i was away04:09
coolsvap:)04:09
prometheanfire:P04:09
prometheanfirewell, nn now :P04:17
prometheanfiretonyb: I'll check for the email in the morn04:17
tonybprometheanfire: :)04:18
coolsvaptonyb, i think there is a series of ROOAAAAAARRRR commits in nova04:20
coolsvapall are different04:21
tonybcoolsvap: Yeah I see that but the one with the T-Rex as the commit message spoke to me04:21
coolsvap:)04:21
*** coolsvap_ has joined #openstack-requirements04:42
*** coolsvap has quit IRC04:48
*** coolsvap_ has quit IRC04:48
*** coolsvap_ has joined #openstack-requirements04:49
*** coolsvap_ is now known as coolsvap04:49
openstackgerritTony Breeds proposed openstack/requirements: Bump olso.context minimum to 2.6.0  https://review.openstack.org/34260304:59
*** coolsvap has quit IRC05:42
*** coolsvap has joined #openstack-requirements05:42
*** openstackgerrit has quit IRC06:33
*** openstackgerrit has joined #openstack-requirements06:33
coolsvaptonyb, https://review.openstack.org/#/c/332409/06:38
patchbotcoolsvap: patch 332409 - requirements (stable/mitaka) - update constraint for python-glanceclient to new r...06:38
tonybcoolsvap: Hmm I wonder why that isn't in my review queue?06:39
coolsvaptonyb, #openstack-nova06:41
*** coolsvap_ has joined #openstack-requirements06:51
*** coolsvap_ has quit IRC06:52
*** coolsvap has quit IRC07:31
*** coolsvap has joined #openstack-requirements07:31
*** coolsvap has quit IRC07:37
*** coolsvap has joined #openstack-requirements07:37
openstackgerritVipin Balachandran proposed openstack/requirements: Bump oslo.vmware to 2.11.0  https://review.openstack.org/34265307:45
openstackgerritRenat Akhmerov proposed openstack/requirements: Add "mistral-lib" to the list of projects  https://review.openstack.org/34267808:47
*** rcarrillocruz has joined #openstack-requirements08:58
rcarrillocruzheya folks08:58
rcarrillocruzany core mind checking https://review.openstack.org/#/c/341542/ to approve?08:59
patchbotrcarrillocruz: patch 341542 - requirements - update constraint for oslo.config to new release 3...08:59
rcarrillocruzi'm seeing packaging issues on oslo-config 3.12:08:59
rcarrillocruzhttp://paste.openstack.org/show/532918/08:59
coolsvaprcarrillocruz, just a min checking the paste provided09:01
rcarrillocruz++09:01
rcarrillocruzthat nova-api log, corresponding to failures on tests like:09:02
coolsvaprcarrillocruz, have you tested with 3.1309:02
rcarrillocruzhttp://logs.openstack.org/23/322823/10/check/gate-ansible-role-cloud-launcher-dsvm-ansible-func-centos-7/e00cf86/console.html09:02
rcarrillocruzi've rechecked with a depends-on the requirements bump09:03
rcarrillocruzit's ongoing09:03
rcarrillocruzhttps://review.openstack.org/34209909:03
rcarrillocruzon check running tests now...09:03
coolsvaprcarrillocruz, would you mind if i wait for another 20-25 mins to verify?09:05
rcarrillocruznot at all, thx09:05
coolsvaprcarrillocruz, i will ack as soon as I verify09:05
rcarrillocruzcoolsvap: the test got past the oslo-config issue, but now fails with oslo-utils :/09:26
rcarrillocruzhttp://paste.openstack.org/show/533028/09:26
rcarrillocruzi just added https://review.openstack.org/#/c/342155/1 to the dependency chain of my change09:27
patchbotrcarrillocruz: patch 342155 - requirements - update constraint for oslo.utils to new release 3....09:27
rcarrillocruzyep09:27
coolsvaprcarrillocruz, can you add https://review.openstack.org/#/c/341323/ as dependency09:28
patchbotcoolsvap: patch 341323 - requirements - Updated from generate-constraints09:28
coolsvap?09:28
rcarrillocruzyep, already did and pushed to the gates09:29
coolsvaprcarrillocruz, the patch i mentioned has all the u-c updates but lets see the resutls with only oslo.utils09:32
rcarrillocruz++09:32
rcarrillocruzif it fails with the individual deps, i'll push a new patchset with 34132309:34
openstackgerritBalazs Gibizer proposed openstack/requirements: Bump oslo versioned object version to latest  https://review.openstack.org/34270409:35
coolsvaptonyb, still around?09:38
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/requirements: Updated from generate-constraints  https://review.openstack.org/34132309:41
rcarrillocruzcoolsvap: so yeah, now complaining about oslo-i18n09:54
rcarrillocruzi'll put as dep the big change you pasted earlier09:54
rcarrillocruzsec09:54
rcarrillocruzcoolsvap: on your latest patchset, oslo-utils is not on 3.1609:55
rcarrillocruzyou want to amend?09:55
coolsvaprcarrillocruz, wait09:56
coolsvaprcarrillocruz, can you add two dependent changes09:56
rcarrillocruzwhich ones09:56
coolsvapi just amended it to exclude oslo.context09:56
coolsvap341323 and 34215509:57
rcarrillocruzk09:57
coolsvapi am checking for nova failures09:57
rcarrillocruzpushed for tests...09:58
coolsvaprcarrillocruz, thanks09:59
rcarrillocruzoh10:01
rcarrillocruzit seems i can't10:01
rcarrillocruzcos the deps are unmergeable10:01
rcarrillocruzThis change or one of its cross-repo dependencies was unable to be automatically merged with the current state of its repository. Please rebase the change and upload a new patchset.10:01
rcarrillocruz?10:01
rcarrillocruzcoolsvap: ^10:02
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/requirements: Updated from generate-constraints  https://review.openstack.org/34132310:04
coolsvaprcarrillocruz, alright let me update oslo.utils10:05
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/requirements: Updated from generate-constraints  https://review.openstack.org/34132310:06
coolsvaprcarrillocruz, ^^10:06
rcarrillocruzthx, now it's running tests10:07
coolsvapprometheanfire, ping once you are online10:23
coolsvaptoabctl, please do not approve any of the u-c changes10:27
toabctlcoolsvap, did I?10:27
coolsvaptoabctl, just a side note10:28
toabctlcoolsvap, ok. thanks10:28
coolsvapi just saw a +2 so wanted to tell you10:28
toabctlcoolsvap, and why not?10:28
coolsvapthere is an issue due to oslo.context10:28
toabctlok. good to know.10:28
coolsvapdebugging that10:28
openstackgerritValeriy Ponomaryov proposed openstack/requirements: Bump manilaclient version  https://review.openstack.org/34272710:37
rcarrillocruzcoolsvap: getting failures now due to pytz10:45
rcarrillocruzIOError: [Errno 2] No such file or directory: '/usr/local/lib/python2.7/dist-packages/pytz-2016.6.dist-info/METADATA'10:45
rcarrillocruzper pypi, there's pytz-2016.6.110:45
coolsvaprcarrillocruz, you will need to submit change for g-r and u-c10:47
coolsvapuc is at pytz===2016.410:47
coolsvapit might get updated in next u-c update10:48
rcarrillocruzlet me see10:48
coolsvapbut g-r is at pytz>=2013.610:48
coolsvaphttps://github.com/openstack/requirements/blob/master/global-requirements.txt#L21510:48
openstackgerritRicardo Carrillo Cruz proposed openstack/requirements: Bump pytz version to 2016.6.1 on g-r and u-r  https://review.openstack.org/34273310:51
rcarrillocruzcoolsvap: ^ let  me know it looks good10:51
rcarrillocruznot sure if i should have two different changes10:51
coolsvaprcarrillocruz, one change is good10:52
rcarrillocruz++10:52
coolsvapbecause it validates g-r & u-c values10:52
coolsvapdims, prometheanfire have a look at https://review.openstack.org/#/c/341323/ whenever you are online, I updated it to exclude oslo.context, futurist and included oslo.utils which was breaking for rcarrillocruz11:25
patchbotcoolsvap: patch 341323 - requirements - Updated from generate-constraints11:25
coolsvapwe can keep the oslo.context in check till we get the updates from tonyb and jamielennox11:26
rcarrillocruzcoolsvap: change 342733 passed check tests11:43
coolsvaprcarrillocruz, yes11:44
coolsvapdims, thx11:50
dimscoolsvap : thank you for keeping an eye on these!11:56
rcarrillocruzdims: could you also please check https://review.openstack.org/#/c/342733/ ?11:59
patchbotrcarrillocruz: patch 342733 - requirements - Bump pytz version to 2016.6.1 on g-r and u-r11:59
dimsrcarrillocruz : needs some context in the commit message (why it's being updated etc)12:00
coolsvaprcarrillocruz, sorry I missed the commit message since i already knew the context12:03
odyssey4mehmm a question for you all12:12
odyssey4meobviously all projects make use of pip, and therefore setuptools and sometimes wheel12:12
odyssey4mewe have all experienced issues where the latest versions of these packages break things12:12
odyssey4meis there a reason why we do not include the versions of these in upper-constraints?12:13
coolsvapodyssey4me, seems like a fair point to me but from what I have seen in my experience with requirements, 1] upper constraints are adoption is very less 2] various projects are not very keen on using upper-constraints for different reasons, primary being end users are likely not going to adapt12:19
odyssey4mecoolsvap we (OpenStack-Ansible) use them heavily, and many other deployers who build from source do the same - also, packagers are using them too12:20
coolsvapinternally i am not sure how many infra projects use u-c12:20
odyssey4mewhether the projects actually use them or not is really for them to decide - it gives us a known, tested upper limit - that's why we use it12:21
odyssey4meit's equivalent to pinning, but without pinning12:21
coolsvapodyssey4me, I am pretty much up for it, I am adding this to weekly meeting agenda12:21
coolsvapwill you be able to join for sometime next meeting?12:21
odyssey4meanyway, so the point is that I'd like to have those packages in u-c so that we can ensure they're pinned to an upper bound for any particular requirements SHA12:22
coolsvapWednesdays @ 12:00 UTC12:22
odyssey4meyes, I can make that12:22
coolsvapcool I will add it first thing in agenda to free you up early12:22
dimsodyssey4me : because some of these tools are baked into the image built by infra folks. we can talk to lifeless and dhellmann for history...12:23
dimsand ttx of course12:24
* coolsvap back later12:30
*** coolsvap is now known as coolsvap|afk12:43
openstackgerritMerged openstack/requirements: Updated from generate-constraints  https://review.openstack.org/34132312:47
openstackgerritBalazs Gibizer proposed openstack/requirements: Bump oslo versioned object version to latest  https://review.openstack.org/34270413:29
prometheanfirecoolsvap|afk: ?14:08
prometheanfireodyssey4me: submit a review :P14:10
odyssey4meprometheanfire I'll be at the meeting to discuss it before I put that effort in.14:12
prometheanfireodyssey4me: ok14:14
prometheanfireodyssey4me: I do agree that it seems like a good idea though14:15
-openstackstatus- NOTICE: Gerrit is restarting to correct memory/performance issues.14:18
prometheanfirecoolsvap|afk: tonyb I did notice that the email didn't go out14:35
dhellmannodyssey4me , dims : we can't include pip, et al in upper-constraints.txt because pip is what enforces the constraints15:01
odyssey4medhellmann that makes sense, but it does appear that pip can downgrade itself if need be15:04
prometheanfiredhellmann: it's self re-enforcing, but why can't it work?15:05
prometheanfireI'm guessing it has to do with how we use get-pip.py?15:06
openstackgerritValeriy Ponomaryov proposed openstack/requirements: Update constraint for python-manilaclient to new release 1.10.0  https://review.openstack.org/34291915:08
openstackgerritValeriy Ponomaryov proposed openstack/requirements: Bump manilaclient version  https://review.openstack.org/34272715:10
dhellmannodyssey4me , prometheanfire : sometimes downgrading works, sometimes it doesn't. Why do you want to use constraints on those tools?15:32
prometheanfirepersonally I don't think it's needed for pip, but I know setuptools had an issue recently15:33
odyssey4medhellmann to provide the same protection as the rest of upper-constraints - a known, good, working version at that point in time15:33
odyssey4medhellmann specifically for openstack-ansible, it provides complete build repeatability - at the SHA we're fixed on, the build will always use the same version of everything installed... forever15:34
odyssey4meit wasn't that long ago that pip 8.0 was released, and all hell broke loose15:35
odyssey4medifferent wheel versions result in different package name schemes15:35
odyssey4meand setuptools isn't always perfect either15:35
odyssey4meso for us, when we tag, we want that tag to always use the same version of the things it was tested with15:36
dhellmannI'm not 100% clear of the details of why those packages are unconstrained, but IIRC it was a combination of lacking a reliable way to do it and a desire to be testing with newish tools. Maybe because we can't assume developers are installing constrained versions on their systems?15:36
odyssey4meback then there wasn't the u-c system we have today, where we update the u-c regularly after testing the newer versions15:37
odyssey4meto be clear, it's not crucial to us - we just implement the pins in a different way to achieve the same goal... but I thought it worth discussing for the benefit of a broader group15:38
openstackgerritRicardo Carrillo Cruz proposed openstack/requirements: update constraint for oslo.context to new release 2.6.0  https://review.openstack.org/34154315:40
prometheanfireodyssey4me: the main issue we'd have is with pip I think15:45
prometheanfireodyssey4me: given our use of get-pip.py infra side15:45
prometheanfirebut for setuptools and wheel it should be doable I think15:46
dhellmannif we can make it work, it's worth looking into. I'd like to understand why we didn't include them in the constraints system when we implemented that, though, before we change that decision and end up with an unintended consequence15:47
dhellmannwe might need to get lifeless and ttx to explain that, since I don't think I was involved15:47
dhellmannfungi might remember15:48
odyssey4meprometheanfire using get-pip.py you can tell it which version to install15:49
odyssey4meprometheanfire see the usage here: https://github.com/pypa/get-pip15:50
*** coolsvap|afk has quit IRC15:50
*** coolsvap|afk has joined #openstack-requirements15:51
odyssey4meto enforce the right versions, we set the version of pip, setuptools and wheel when installing pip using get-pip15:51
*** coolsvap|afk is now known as coolsvap15:51
odyssey4mehttps://github.com/openstack/openstack-ansible-pip_install/blob/master/tasks/install_online.yml#L4515:51
coolsvapprometheanfire, yes the email did not go out15:52
prometheanfiredhellmann: fair enough, this is something odyssey4me is bringing up in the next meeting15:52
prometheanfireodyssey4me: true, I don't think we use that yet15:52
coolsvapprometheanfire, i updated the bot review to exclude the oslo.context till jamie works on it15:59
coolsvapand we can check that later16:00
coolsvapi brought up the issue of mistral-extras in infra16:00
coolsvapso that project-config is not updated before requirements/projects.txt is updated16:00
prometheanfireah, cool16:05
odyssey4mecoolsvap yeah, currently there's a job to validate that anything put into requirements/project.txt has a check-requirements job16:29
odyssey4mewhat needs to be added is a check that anything that has the check-requirements job removed has already been removed from requirements/project.txt16:30
odyssey4methat's the missing link16:30
odyssey4meI'd be happy to try and figure out where to put that, but I won't get to it within the next week or two I don't think.16:31
coolsvapodyssey4me, yes i am looking to tackle that, if not iwill let you know16:54
rcarrillocruzhey folks19:14
rcarrillocruzcan any core +A https://review.openstack.org/#/c/341543/ ?19:14
patchbotrcarrillocruz: patch 341543 - requirements - update constraint for oslo.context to new release ...19:14
rcarrillocruzi rebased it19:14
rcarrillocruzi'm getting 500 nova errors due to current oslo.context version package19:14
rcarrillocruzdims, prometheanfire ^19:18
prometheanfirercarrillocruz: other projects are breaking with 2.6.0 iirc, which is why it's being held back atm19:19
rcarrillocruzoh?19:19
rcarrillocruz:/19:19
prometheanfireya...19:19
prometheanfirehttps://bugs.launchpad.net/neutron/+bug/160208119:20
openstackLaunchpad bug 1602081 in OpenStack Compute (nova) "Use oslo.context's policy dict" [Undecided,In progress] - Assigned to Jamie Lennox (jamielennox)19:20
rcarrillocruzi'm getting this fine exception on nova with 2.5.0 :/19:20
rcarrillocruzhttp://paste.openstack.org/show/533092/19:20
rcarrillocruzsigh19:20
dimsrcarrillocruz : is there evidence of the nova 500 problem in the CI?19:21
prometheanfirecommenting on the 1543 review with it would be helpful if so19:22
rcarrillocruzdims: dunno, have asked since yerd19:23
rcarrillocruzyesterday and except coolsvap seeing similar issues this morning nothing19:23
rcarrillocruzbut i've seen this similar issue with other packages, it just i got past them cos the packages i had issues with got versions bump on requirements19:24
dimsrcarrillocruz : let me share what we do.. for example when the releases happened yesterday, the bot proposed an update (https://review.openstack.org/#/c/341323/) then we have a script that updates a bunch of reviews against individual projects to see if the bot proposed update breaks something (https://review.openstack.org/#/q/status:open+branch:master+topic:dims/test/constraints). Those are the reviews we go look for19:35
dims problems.19:35
patchbotdims: patch 341323 - requirements - Updated from generate-constraints (MERGED)19:35
dimsrcarrillocruz : looks like coolsvap had to touch up that review19:35
rcarrillocruzyeah, i was looking into it this morning, he touched as i was getting oslo-utils issues on 3.1519:37
rcarrillocruzbut anyway19:37
rcarrillocruzbumping19:37
rcarrillocruzis masking the issue19:37
rcarrillocruzwe must know why the current versions are broken per the test failures19:37
rcarrillocruzi'm checking current oslo-context on a venv to see19:37
dimsrcarrillocruz : looks like coolsvap did not trigger all the reviews after he touched up the bot proposed review, so i am doing that now19:39
dimsrcarrillocruz : you should see all the review refreshed in https://review.openstack.org/#/q/status:open+branch:master+topic:dims/test/constraints19:40
dimslet's watch that and see if we made a mistake merging something this morning19:40
rcarrillocruzsweet, thx!19:40
*** MarleenLazard63 has joined #openstack-requirements20:59
*** MarleenLazard63 has quit IRC21:17
*** MarleenLazard63 has joined #openstack-requirements21:52
*** MarleenLazard63 has quit IRC23:06

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