Wednesday, 2013-12-11

anteayafungi: in that patch does project come in as /neutron or does it come in as /openstack/neutron?00:00
anteayathe path needs the second option00:00
anteayaI can't see in the code which one gets passed in00:01
fungianteaya: you could look at a bug updated by gerrit00:01
fungii'll find a good example00:01
StevenKhttps://bugs.launchpad.net/bugs/125729500:01
uvirtbotLaunchpad bug 1257295 in python-novaclient "openstack is full of misspelled words" [Low,In progress]00:01
fungithe man of the hour00:01
StevenKhttps://bugs.launchpad.net/nova/+bug/1257295/comments/7 in fact00:01
*** jcooley_ has quit IRC00:02
fungianteaya: so there you can see that the first %s gets orgname/reponame and the second %s gets the commit sha00:02
*** jcooley_ has joined #openstack-infra00:02
fungianteaya: so you can try replacing the bits of the format string which i replaced and see if that gets you a usable page00:02
fungi(something i would have tested myself if i weren't so slack)00:03
pleia2github.org uses the same path ie openstack/neutron so it's an easy one to eyeball00:03
fungiyup00:03
*** yamahata_ has quit IRC00:04
fungii *did* at least pull up a sample cgit commit page for sanity00:04
*** fbo is now known as fbo_away00:04
anteayaStevenK: thank you00:04
openstackgerritA change was merged to openstack-infra/zuul: Pin Sphinx to <1.2  https://review.openstack.org/6117200:05
anteayafungi: yes I can see the value for the first and second %s in the original, and they make sense now for the change00:05
fungianteaya: good review!00:05
anteayathanks00:05
* anteaya shakes off the dust00:05
anteayapleia2: yes, that is true00:06
*** jcooley_ has quit IRC00:07
anteayatrying to find a rhythm again00:07
anteayaStevenK: coming in to review 61290?00:10
*** jcooley_ has joined #openstack-infra00:13
*** jcooley_ has quit IRC00:13
*** jcooley_ has joined #openstack-infra00:13
StevenKanteaya: Have just done so00:16
*** jcooley_ has quit IRC00:18
anteaya:D00:18
openstackgerritDavanum Srinivas (dims) proposed a change to openstack-infra/elastic-recheck: Fix the legend in the e-r page  https://review.openstack.org/6129500:18
*** jergerber has quit IRC00:18
*** Bada has quit IRC00:19
openstackgerritA change was merged to openstack-infra/config: Install libtidy on slaves  https://review.openstack.org/6087200:21
*** herndon has quit IRC00:21
*** pmathews has quit IRC00:25
*** jhesketh_ has joined #openstack-infra00:29
*** salv-orlando has joined #openstack-infra00:30
*** ^d is now known as ^demon|away00:31
*** jhesketh_ is now known as jhesketh00:33
*** jhesketh_ has joined #openstack-infra00:33
openstackgerritClark Boylan proposed a change to openstack-infra/elastic-recheck: Cap Sphinx at <1.2 to avoid distutils problems.  https://review.openstack.org/6129700:34
*** sarob has joined #openstack-infra00:34
openstackgerritClark Boylan proposed a change to openstack-infra/elastic-recheck: Document adding bug signatures to e-r.  https://review.openstack.org/6129800:34
clarkbthat will close another one of our bugs \o/00:35
sdagueclarkb: is e-r publishing public docs yet?00:35
fungilgtm00:36
clarkbsdague: unsure00:36
sdagueman, this fact that gerrit only returns 500 results at a time is annoying00:36
clarkbsdague: doesn't look like it, it is just a couple jobs in the zuul layout file to make it happen00:36
sdagueclarkb: any chance that you could propose that?00:36
clarkbsure00:36
sdaguehey, while there are knowledgable folks around. Anyone know the magic invocation to use upstream nova client to spin up rax nodes?00:37
openstackgerritA change was merged to openstack-infra/elastic-recheck: Cap Sphinx at <1.2 to avoid distutils problems.  https://review.openstack.org/6129700:37
fungisdague: stop using the rax-specific auth and use an account password00:38
fungisdague: example at https://git.openstack.org/cgit/openstack-infra/devstack-gate/tree/README.rst#n10000:38
clarkbdid we stop publishing zuul docs?00:39
sdaguefungi: so I tried that, and it didn't work00:39
sdagueI can try it again00:39
clarkboh nevermind it is a special job00:39
fungisdague: OS_USERNAME,OS_PASSWORD,OS_TENANT_NAME,OS_AUTH_URL,OS_REGION_NAME are all i use with latest released novaclient from pypi00:39
fungisdague: and remove any vars specific to rax special auth methods00:40
sdaguehmm... let me test again00:40
fungisince those now require pulling their novaclient plugin off github00:40
anteayasdague: any objections to me submitting an e-r patch clean up the empty spaces?00:41
openstackgerritClark Boylan proposed a change to openstack-infra/config: Publish elastic-recheck documentation.  https://review.openstack.org/6130000:41
clarkbsdague: ^00:41
sdagueanteaya: which empty spaces?00:41
anteayabeen looking for https://git.openstack.org/cgit/openstack-infra/elastic-recheck/tree/queries for a while00:41
anteaya1252514, 1251920, 1251784, 1251512 ...00:42
anteayathe bugs with no matches00:42
*** datsun180b has quit IRC00:44
*** cyeoh_ has joined #openstack-infra00:46
*** cyeoh_ is now known as cyeoh00:46
*** dims has joined #openstack-infra00:46
*** salv-orlando has quit IRC00:46
anteayaor is there something obvious which I am failing to understand?00:46
sdaguefungi: ok, maybe I mis understand what OS_TENANT_NAME should be00:48
*** sarob has quit IRC00:48
*** sarob has joined #openstack-infra00:49
fungisdague: for our rackspace accounts, it's an integer00:49
fungiseemingly unique, so probably tenant id number00:49
*** ^demon|away has quit IRC00:50
fungii can poke around the webui to see what it matches00:50
sdagueok, that was the magic bit of info I needed00:51
sdagueit's your account #00:51
fungisdague: yup, if you log into https://mycloud.rackspace.com/ it's next to your account name in the top-right corner00:51
fungifor our hpcloud accounts it's a project name, so i'm guessing it's just a provider-specific id field each cloud implements to tie into whatever their other systems want as a unique key00:52
anteayaclarkb: one suggestion on 6129800:53
*** sarob has quit IRC00:53
*** yamahata_ has joined #openstack-infra00:55
clarkbanteaya: responded00:55
openstackgerritSean Dague proposed a change to openstack-infra/devstack-gate: update documentation with specific of rax setup  https://review.openstack.org/6130100:55
*** yamahata_ has quit IRC00:55
sdagueanteaya: oh, so there are patches in flight for dropping those bugs right now00:56
*** yamahata_ has joined #openstack-infra00:56
sdaguefungi: ok, so above is a doc patch to help the next poor slob that doesn't understand this the way I failed to understand it00:56
fungisdague: thanks!00:57
anteayasdague: ah perhaps I can review them /me looks at elastic-recheck patches00:58
*** jhesketh_ has quit IRC00:58
fungisdague: i run those steps soooo often that i now have a set of scripts... one which allows me to select provider/region/account/flavor/image/servername, a second which spins up the vm and applies all the puppetry, and a third which uploads a tempest job shell stub and patch and runs with those against the project/branch i specify00:59
fungii probably did 50 by-hand tempest runs against various patches over the course of last weekend01:00
anteayaclarkb: back at 'cha01:00
sdaguefungi: you got those scripts somewhere?01:00
fungisdague: i can upload the secnod and thord (and some sub-scripts they call), though the first script is basically credentials01:01
sdaguefungi: also, you know what the performance flavors are called01:01
sdaguefungi: right :)01:01
fungisdague: nova flavor-list?01:01
anteayaclarkb: here is my use case: https://wiki.openstack.org/wiki/Network/Meetings#Bugs01:01
sdagueah, right01:01
anteayaI'm going through all the gate blocking bugs for neutron and since I am doing such a great job, now the critical neutron bugs too01:02
fungisdague: i can slap those into a git repo and cram them up to github or something, but not right this moment. i think ttx may also have some similar since he runs a lot of them for the same reasons i do01:02
clarkbanteaya: I guess I am not seeing how they are different other than the mechanical steps. I will change step 3 to suggest pasting the logstash url instead of just the query01:02
anteayahaving a link to logstash in each bug report just helps me sort out which bugs are currently an issue and which aren't01:02
sdaguefungi: yeh, seems like that would be a handy set of things to share.01:02
sdaguepossibly even as a subdir of d-g01:02
devanandaclarkb: hi! have a minute or two for a chat about ironic testing?01:03
anteayaclarkb: this bug report has both the fingerprint and the url: https://bugs.launchpad.net/neutron/+bug/125144801:03
uvirtbotLaunchpad bug 1251448 in neutron "BadRequest: Multiple possible networks found, use a Network ID to be more specific. " [High,New]01:03
anteayait is just faster when I have to go through about 7 or 8 bug reports, that is all01:03
clarkbdevananda: sure01:03
clarkbanteaya: ya, I will update01:03
anteayaclarkb: and thanks01:03
*** jhesketh_ has joined #openstack-infra01:03
openstackgerritClark Boylan proposed a change to openstack-infra/elastic-recheck: Document adding bug signatures to e-r.  https://review.openstack.org/6129801:04
clarkbanteaya: ^01:04
fungisdague: definitely--i just need to generalize them a little more first, but at the moment i have a bunch of advisories to put together for tomorrow morning01:04
sdagueno worries01:05
sdagueI just feel accomplished to have figured out this part :)01:05
*** mrodden has joined #openstack-infra01:05
devanandaclarkb: remember the conversations we had a while back about testing nova-baremetal inside of devstack-gate01:06
fungisdague: that's how i felt once i got that writeup cut-n-pasteable enough for what i was doing. that's honestly most of the battle with replicating tests01:06
devanandaclarkb: eg, set up a network bridge, create a few VMs, and let baremetal control them01:06
clarkbdevananda: ya01:06
devanandaclarkb: all that got canned when it was apaprent that tripleo couldn't be tested that way because nested VMs are too slow01:06
devanandaclarkb: but that doesn't apply to the testing of ironic01:06
clarkbdevananda: right01:07
devanandaclarkb: we just need to bring up a tiny cirros image01:07
devanandaclarkb: how feasible do you think it would be today to revive that effort?01:07
clarkbdevananda: I think it is very feasible (I thought we were already going down that route)01:07
devanandaclarkb: and get tempest exercising the whole deployment path with ironic in d-g pipeline01:08
devanandaclarkb: well, pleia2 was the last one working on that stuff, and afaik she stopped when it didn't fit tripleo's needs01:08
clarkbdevananda: right I don't think anyone is working on it01:08
*** sandywalsh_ has quit IRC01:09
pleia2there was a recent mailing list thread about it, and I spoke with someone else the other day01:09
devanandasome folks from mirantis are now looking at testing ironic. i'm not sure how easily i can explain this to them.... but it seems better than having them run off and do something else entirely01:09
* pleia2 digs up notes01:09
*** julim has joined #openstack-infra01:09
clarkbdevananda: ++01:09
devanandapleia2: possibly vkozhukalov ? I pulled him in here at one point in relation to some of this01:09
pleia2devananda: I think he's the one I corresponded with over email, someone else in irc01:10
pleia210:31 < pleia2> mestery: vkozhukalov collected links from our current work, I replied here: http://lists.openstack.org/pipermail/openstack-dev/2013-December/021399.html01:10
pleia2ah, it was mestery :)01:10
anteayaclarkb: +1'd and \o/01:10
clarkbthe way I would start is to have a small pretest devstack-gate hook that does the setup for the "baremetal" nodes01:10
clarkbthen tempest will run and have that available to it01:10
fungimestery: is cisco, not mirantis01:11
devanandapleia2: yep! saw that, thanks01:11
pleia2yeah, vkozhukalov is from the mirantis crew01:11
clarkbsince devstack itself doesn't need to know about this right? this is purely contrived test env setup01:11
pleia2so we've got some mirantis folks, and at least one guy from cisco interested01:11
devanandapleia2: i don't see the tripleo-ci stuff as in any way overlapping (or likely even being reusable) for this01:12
devanandabut maybe i'm missing something01:12
anteayamestery mostly needs multi-node testing for neutron stuff, to the best of my knowledge01:12
clarkbI think multinode testin will need to go another route01:12
anteayahe is having a meeting for third party testing on Thursday at 1700utc in -alt, mostly aimed at -neutron plugin testing01:13
devanandaclarkb: well. something needs to switch on the flag(s) in devstack to use ironic, configure it the right way, and enroll the VMs that were pre-prepared01:13
pleia2devananda: yeah, perhaps not01:13
anteayathe multi-node testing will probably come up01:13
clarkbdevananda: that is what devstack-gate does01:13
clarkbdevananda: I guess I am trying to differentiate between make sure baremetal nodes are avaialble and setup a cloud01:13
devanandaclarkb: right. devstack itself does need some changes for testing ironic (some or most of those may already be in place)01:14
devanandaclarkb: and d-g clearly needs most of the work01:14
clarkbya01:14
devanandaclarkb: i think that the existing tempest tests which exercise clouds should be fine.01:14
devanandaAND01:14
devanandathis is all separate from the tempest tests which we've already proposed01:14
devanandathose explicitly perform CRUD operations on ironic's API01:15
devanandawhich won't be tested by devstack in teh above discussion -- they'll be _used_ by d-g in the preparation of the run01:15
clarkbdevananda: so one potential problem there is the existing tempest tests can start a ton of VMs, we will need to make sure the "baremetal" nodes have enough capacity01:15
*** eharney has quit IRC01:15
devanandahum01:15
devanandaclarkb: are they starting "fake" vms?01:15
clarkbno real qemu VMs today01:15
devanandaah, k01:15
devanandain principle, there shouldn't be any more overhead for ironic to manage a bunch of qemu VMs01:16
clarkbdevananda: we just need to size the fake baremetal env appropriately01:16
clarkbthis won't be 2 or 3 nodes, probably more like 10001:16
devanandawell. correction. the nova scheduler may be a bit mroe of a bottleneck -- it'll see each qemu VM as a separate resource01:16
clarkbsdague and mtreinish would have a better handle on tempest resource consumption01:17
devanandacool01:17
*** oubiwan__ has joined #openstack-infra01:17
sdaguedevananda: what image are you going to boot on the fake baremetal?01:17
devanandamy point above is that teh CRUD of ironic resources still needs to be handled separately by tempest01:17
sdaguetoday we do really tiny guests because we boot the cirros image01:17
devanandasince that won't be covered by the traditional tempest-runs-against-a-cloud stuff01:17
sdaguethat's the only place I think we might get in trouble01:18
devanandasdague: cirros is fine for testing whether ironic booted something01:18
sdaguedevananda: that will pxe?01:18
devanandawhy wouldn't it?01:18
devanandait has a kernel & ramdisk01:18
lifelesssdague: cirros is above the PXE layer01:18
sdagueok, fair01:18
lifelesssdague: cirros is the workload, not the VM :)01:18
sdagueright :)01:18
sdagueok, I'm on the same page now01:18
devananda:)01:18
sdagueI guess in your fake baremetal layer, how are you specifying qemu memory?01:19
devanandasdague: ironic is not creating VMs01:19
clarkbdevananda: for the other stuff you would just have tempest tests tagged with ironic or whatever that only run when ironic is available. similar to how we do ?neutron? again sdague knows best01:19
devanandasdague: in this environment, d-g scripts would create all the tiny VMs ahead of time and just enroll them with ironic -- feed the MAC addresses of the NIC of each qemu VM to our API01:20
clarkbsdague: right so something in d-g (I think a hook) would setup a ton of qemu VMs 64MB large each then register them into ironic via devstack or whatever01:20
sdaguedevananda: ok, gotcha01:20
devanandaclarkb: it'd have to be after devstack is started (or at least after the ironic services are up)01:20
clarkbdevananda: yup01:21
*** sandywalsh_ has joined #openstack-infra01:21
sdagueright, so as long as that mem size is tunable sanely in d-g life is probably good01:21
*** dims has quit IRC01:21
devanandabotgh the mem size and # of qemu VMs01:21
clarkbI am thinking devstack needs to know about enrollment beacse you may want to use devstack to do ironic01:21
clarkbbut devstack shouldn't start a ton of small VMs to be baremetal proxies, because that is implementation specific01:21
sdaguenow that's an interesting idea01:21
lifelessclarkb: btw we have that code in tripleo incubator already01:21
lifelessclarkb: we should reuse it01:21
sdaguehonestly, that might be a good devstack patch01:22
clarkblifeless: perfect01:22
lifelesswe might want to rehome it for this01:22
lifelessbut it shouldn't live in devstack01:22
devanandaclarkb: so, maybe have d-g create the VMs and dump their MACs into a csv file01:22
devanandaclarkb: then have devstack suck up that file as part of lib/ironic or such?01:23
sdaguelifeless: so why wouldn't you have this live in devstack?01:23
devanandasdague: because tripleo does the same thing01:23
lifelesssdague: because that would make tripleo-gate depend on devstack01:23
*** sarob has joined #openstack-infra01:23
sdagueif I was a developer, and I wanted to work on ironic, this would be really useful01:23
devanandalifeless: this sounds a lot like what bmposeur initially aimed to do01:23
clarkbdevananda: that is what I am thinking01:23
lifelesssdague: right, so we should make it more accessible yes01:23
lifelesssdague: but the devstack codebase is a thing that takes over your machine, and thats very much not what the tripleo devtest cycle does - we explicitly avoid that01:24
lifelesssdague: because the workaround - running in a VM - is horribly slow for tripleo01:24
*** salv-orlando has joined #openstack-infra01:25
sdaguehmmm... ok, I guess I'll see the patches when they come01:25
lifelesssdague: devstack can reuse things, right? :)01:26
clarkbdevananda: so I think we start with those two bits. Something to spin up a ton of small qemu VMs and devstack learning to enroll them as baremetal nodes01:26
lifelessdevananda: yes, but it overreached and became a reimplementation of virsh01:26
clarkbonce we have that we can add a job that runs tempest against a "baremetal" cloud01:26
devanandalifeless: agreed01:27
clarkbon top of that we add the additional tests01:27
*** talluri has quit IRC01:27
lifelesssdague: devstack combines deployment tooling with developer setup - and thats fine for its mission, the problem is if we want to reuse just the developer setup, it's really hard because its conflated with the deployments tuff01:27
devanandaclarkb: sounds good to me01:27
clarkbbecause the underlying cloud should have all of the dependencies you need to run those tests at that point01:27
lifelesssdague: which is why we have similar but different stuff in the tripleo space :(01:27
*** sarob has quit IRC01:28
*** salv-orlando has quit IRC01:28
lifelessone approach I think might work well would be to suck the tripleo-incubator into devstack for some of these functions [we'd want symettric gating for it for that, of course]01:28
sdaguelifeless: well it would be interesting to understand how that could be sliced better, because having a reimplementation in tripleo space seems suboptimal, even if different on a few things01:28
*** nosnos has joined #openstack-infra01:29
*** salv-orlando has joined #openstack-infra01:29
lifelesssdague: I think you should have a solid play with tripleo, it would help you see where there is overlap-that-should-be-converged and overlap-that-shouldn't-be01:29
sdaguepossibly, but with the stuff on my plate, it will be a while :)01:30
lifelesssdague: sure :)01:30
lifelesssdague: it's just kinda hard to give a useful handwave description01:30
sdagueplus I'm more hardware constrained than previously at the moment. Will fix that, but it means playing with this is somewhat bounded.01:30
devanandaclarkb: I need to step away and start prepping for dinner soon. this has been very helpful; i'm sending a few notes to the ML. thanks!01:31
lifelesssdague: point is, devstack's mission is developer productivity with some deployment capability as option, tripleos is production deployment with developer-productivity as option01:31
clarkbdevananda: np I need to head home in a minute too01:31
clarkbI will try to keep up with the ML thread01:31
lifelessdevananda: what do you want tonnes of VMs to assess?01:32
sdagueok, fair. Seems like we're going to have some duping, but some times that's what it is.01:33
devanandalifeless: i don't. it's apparently a requirement of tempest now01:33
*** yaguang has joined #openstack-infra01:33
devanandalifeless: for the general let-tempest-exercise-openstack tests01:34
lifelessoh, due to the concurrency?01:34
clarkblifeless: concurrency and async cleanup iirc01:34
lifelesskk01:35
lifelessso should be identical to qemu01:35
*** dims has joined #openstack-infra01:36
clarkbnew propose reqs failure :( https://jenkins.openstack.org/job/propose-requirements-updates/40/console01:37
clarkbI can't believe there is a conflict, unless an out of band requirements update went in01:37
jeblairclarkb: 2013-12-11 01:23:35.782 | Rebasing (1/108)01:39
clarkbjeblair: right it did a rebase for some reason, I think possibly out of band requirement01:40
jeblairclarkb: that's kind of a red flag.  is it possible there's some git repo cleanup in the workspace not happening?01:40
*** julim has quit IRC01:40
clarkbjeblair: well it is pulling the existing change from gerrit and basing on that01:40
*** talluri has joined #openstack-infra01:40
clarkbjeblair: I think we may need to pull that change from gerrit for diffing only01:40
clarkbgo back to basing new patchset on $branch then at the end do a git diff HEAD and a git diff $oldpatchset from gerrit. If they both differ then push01:41
clarkbI need to run, but that may fix the probem01:42
jeblairclarkb: i'm not sure it checkout out the havana branch of ceilometer01:43
jeblairwow01:43
jeblairclarkb: i'm not sure it checked out the havana branch of ceilometer01:43
*** michchap_ has quit IRC01:46
*** sarob has joined #openstack-infra01:47
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Fix branch logic in req propose script  https://review.openstack.org/6130401:47
jeblairclarkb: ^01:47
*** michchap has joined #openstack-infra01:47
anteayaclarkb: on 61300 I am just curious about '{name}-docs' I don't see it anywhere else in projects.yaml, why here?01:47
anteayaoh he left01:48
*** reed has quit IRC01:58
*** herndon has joined #openstack-infra02:00
*** rongze has joined #openstack-infra02:01
*** guohliu has joined #openstack-infra02:02
*** AaronGr is now known as AaronGr_Zzz02:03
*** bingbu has joined #openstack-infra02:03
*** jcooley_ has joined #openstack-infra02:04
*** mriedem has joined #openstack-infra02:04
*** mriedem has quit IRC02:05
*** mriedem has joined #openstack-infra02:06
*** xchu has joined #openstack-infra02:10
openstackgerritA change was merged to openstack-infra/elastic-recheck: Ability to Soft Delete Stale Bugs from elastic-recheck  https://review.openstack.org/6114902:10
openstackgerritA change was merged to openstack-infra/elastic-recheck: Fix the legend in the e-r page  https://review.openstack.org/6129502:10
openstackgerritA change was merged to openstack-infra/elastic-recheck: Delete stale bugs from elastic-recheck page  https://review.openstack.org/6118602:14
*** ryanpetrello has quit IRC02:17
*** herndon has quit IRC02:20
*** ryanpetrello has joined #openstack-infra02:28
*** sarob has quit IRC02:29
*** sarob has joined #openstack-infra02:30
*** rongze has quit IRC02:31
openstackgerritSean Dague proposed a change to openstack-infra/elastic-recheck: use grenade gate numbers, not check queue numbers  https://review.openstack.org/6130702:32
*** slong has joined #openstack-infra02:33
*** sarob_ has joined #openstack-infra02:34
*** sarob has quit IRC02:35
*** krotscheck has quit IRC02:37
*** jcooley_ has quit IRC02:43
*** rongze has joined #openstack-infra02:46
sarob_i requested a new stackforge project02:49
sarob_stackforge/milk has no master, i can't push the first patch02:51
*** sarob_ is now known as sarob02:51
sarobErrors running git rebase -i remotes/gerrit/master02:52
sarobfatal: Needed a single revision02:52
sarobinvalid upstream remotes/gerrit/master02:52
*** Ryan_Lane has quit IRC02:52
*** Ryan_Lane has joined #openstack-infra02:53
*** nati_ueno has quit IRC02:54
*** Ryan_Lane has quit IRC02:58
*** marun has joined #openstack-infra03:00
*** sarob has quit IRC03:06
*** sarob has joined #openstack-infra03:06
*** ryanpetrello has quit IRC03:11
*** pcrews has quit IRC03:11
*** sarob has quit IRC03:11
*** ladquin has quit IRC03:14
*** AaronGr_Zzz is now known as AaronGr03:19
*** paul-- has joined #openstack-infra03:21
*** zhiyan has joined #openstack-infra03:22
zaroanteaya: '{name}-docs' expands to 'elastic-recheck-docs' which is found in layout.yaml03:23
*** Ryan_Lane has joined #openstack-infra03:25
* StevenK peers at https://wiki.openstack.org/wiki/Governance/Approved03:28
*** Ryan_Lane has quit IRC03:30
fungiif sarob returns, i've cleared and successfully reimported stackforge/milk, but unfortunately that means our race is probably still lurking (don't have time to go spelunking in logs just at the moment)03:30
clarkbfungi: if you are still on review.o.o check that jeepyb is up to date there03:32
fungigood idea03:32
clarkbI think it has had trouble updating which may explain it (could be the race is just still there and ugh)03:32
fungijeepyb==1caeeae03:34
fungiaccording to pip freeze03:34
clarkbthat is up to date :/03:35
clarkbI am pretty sure the problem is related to creating groups. Anytime a new project creates a new group everything after that fails03:35
clarkbsubsequent runs work03:35
clarkbmaybe the logic in group creation is actualyl the problem? should probably beef up logging and hit review-dev when it is back03:36
*** hcc has joined #openstack-infra03:50
*** gyee has quit IRC03:55
*** SergeyLukjanov has joined #openstack-infra04:17
*** SergeyLukjanov has quit IRC04:21
*** dstanek_afk has joined #openstack-infra04:22
*** ArxCruz has quit IRC04:22
*** ArxCruz has joined #openstack-infra04:24
*** slong_ has joined #openstack-infra04:24
*** slong has quit IRC04:24
*** yamahata_ has quit IRC04:24
*** dstanek has quit IRC04:24
*** plomakin has quit IRC04:24
*** Mithrandir has quit IRC04:24
*** Mithrandir has joined #openstack-infra04:25
*** plomakin has joined #openstack-infra04:25
*** hcc is now known as hdd_04:25
clarkbfungi: I think the problem may be elsewhere looking at the new mange-projects, if project_created: push_to_gerrit() then later if acl_config: process_acls() if has-github: create_github_project()04:27
*** SergeyLukjanov has joined #openstack-infra04:27
*** yamahata_ has joined #openstack-infra04:28
clarkbthe github project was created so those other things must be independently failing now04:28
*** ArxCruz has quit IRC04:29
*** dstanek_afk has quit IRC04:31
*** mriedem has quit IRC04:31
*** ArxCruz has joined #openstack-infra04:32
*** changbl has quit IRC04:33
clarkblooking at the git log for the project it looks like project creation simply failed04:34
*** changbl has joined #openstack-infra04:36
*** dstanek_afk has joined #openstack-infra04:36
fungidid you confirm the github mirror wasn't created on my manual re-run?04:39
clarkbfungi: I checked it about 15 minutes before you reran it04:40
fungiah... okay04:40
clarkbfungi: assuming your statement was near when you reran it04:40
clarkbfungi: I wonder if the clone of the seed repo is failing04:41
fungiyup04:41
*** blamar has quit IRC04:47
*** talluri has quit IRC04:48
*** rongze has quit IRC04:50
*** dstanek_afk is now known as dstanek04:52
*** AaronGr is now known as AaronGr_Zzz04:53
*** oubiwan__ has quit IRC04:56
*** ryanpetrello has joined #openstack-infra04:58
*** talluri has joined #openstack-infra05:04
*** SergeyLukjanov is now known as _SergeyLukjanov05:09
*** _SergeyLukjanov has quit IRC05:10
*** SergeyLukjanov has joined #openstack-infra05:14
SergeyLukjanovfungi, clarkb, hey guys :)05:15
fungiSergeyLukjanov: hey there05:15
SergeyLukjanovthat's funny to have a 12h time difference :)05:16
* fungi should get to sleep soon05:17
*** oubiwan__ has joined #openstack-infra05:17
StevenKSleep is for the week05:17
*** oubiwan__ is now known as oubiwann-lambda05:17
*** boris-42 has joined #openstack-infra05:18
*** rongze has joined #openstack-infra05:20
*** oubiwann-lambda has quit IRC05:23
*** ryanpetrello has quit IRC05:25
*** ryanpetrello_ has joined #openstack-infra05:25
*** nosnos_ has joined #openstack-infra05:31
*** jcooley_ has joined #openstack-infra05:33
*** nosnos has quit IRC05:34
*** rongze has quit IRC05:35
*** nicedice has quit IRC05:36
*** jhesketh has quit IRC05:38
*** xchu has quit IRC05:45
openstackgerritSteve Martinelli proposed a change to openstack/requirements: Add oauthlib library to replace oauth2  https://review.openstack.org/6119805:53
openstackgerritChangBo Guo proposed a change to openstack-dev/pbr: Fix typos in documents  https://review.openstack.org/6111005:53
openstackgerritKhai Do proposed a change to openstack-infra/config: fix installation of nodepool on jenkins-dev  https://review.openstack.org/6132105:54
*** juice has quit IRC05:57
*** devananda has quit IRC05:57
*** davidlenwell_ has joined #openstack-infra05:57
*** devananda has joined #openstack-infra05:57
*** Ghe_HPDiscover has quit IRC05:57
*** vipuls has quit IRC05:58
*** davidlenwell has quit IRC05:58
*** echohead has quit IRC05:58
*** LinuxJedi has quit IRC05:58
*** NobodyCam has quit IRC05:58
*** xchu has joined #openstack-infra05:59
*** echohead has joined #openstack-infra05:59
*** LinuxJedi has joined #openstack-infra06:00
*** rongze has joined #openstack-infra06:03
*** juice has joined #openstack-infra06:03
*** nosnos_ has quit IRC06:04
*** nosnos has joined #openstack-infra06:05
*** xchu has quit IRC06:06
*** vipul has joined #openstack-infra06:07
*** rongze has quit IRC06:07
*** vkozhukalov has quit IRC06:09
*** paul-- has quit IRC06:13
*** paul-- has joined #openstack-infra06:13
*** NobodyCam has joined #openstack-infra06:14
*** rongze has joined #openstack-infra06:15
*** paul-- has quit IRC06:17
*** odyssey4me has joined #openstack-infra06:19
*** hdd_ has quit IRC06:20
*** SergeyLukjanov has quit IRC06:21
*** zhiyan has quit IRC06:22
*** xchu has joined #openstack-infra06:25
*** echohead has quit IRC06:31
*** Ghe_HPDiscover has joined #openstack-infra06:35
*** jcooley_ has quit IRC06:39
*** senk has joined #openstack-infra06:40
*** denis_makogon has joined #openstack-infra06:42
*** thomasbiege has joined #openstack-infra06:45
*** SushilKM has joined #openstack-infra06:46
*** zhiyan has joined #openstack-infra06:51
*** ryanpetrello_ has quit IRC06:52
*** ryanpetrello has joined #openstack-infra06:56
*** dstanek has quit IRC07:02
*** lifeless has quit IRC07:05
*** jhesketh_ has quit IRC07:09
*** jcooley_ has joined #openstack-infra07:09
*** sdake_ has quit IRC07:13
*** jcooley_ has quit IRC07:15
*** guohliu has quit IRC07:18
*** boris-42 has quit IRC07:22
*** guohliu has joined #openstack-infra07:25
*** nati_ueno has joined #openstack-infra07:36
*** thomasbiege has quit IRC07:37
*** yolanda has joined #openstack-infra07:37
*** SergeyLukjanov has joined #openstack-infra07:49
*** sarob has joined #openstack-infra07:51
*** xchu has quit IRC07:52
*** DinaBelova has joined #openstack-infra07:54
*** thomasbiege has joined #openstack-infra07:55
*** Abhishek_ has joined #openstack-infra07:57
*** vkozhukalov has joined #openstack-infra07:57
*** senk1 has joined #openstack-infra07:58
*** senk has quit IRC08:00
*** jcoufal has joined #openstack-infra08:04
*** jcoufal has quit IRC08:04
*** jcooley_ has joined #openstack-infra08:05
*** bingbu has quit IRC08:05
*** jcoufal has joined #openstack-infra08:05
*** xchu has joined #openstack-infra08:05
*** jcooley_ has quit IRC08:09
*** flaper87|afk is now known as flaper8708:13
*** ruhe has joined #openstack-infra08:16
*** fbo_away is now known as fbo08:18
*** ruhe has quit IRC08:21
*** ruhe has joined #openstack-infra08:22
*** bingbu has joined #openstack-infra08:25
*** ruhe has quit IRC08:25
*** guohliu has quit IRC08:35
*** guohliu has joined #openstack-infra08:35
*** nati_ueno has quit IRC08:38
*** yongli is now known as yongli_away08:41
ttxStevenK: about that wiki URL, it's pretty stale08:45
*** yassine has joined #openstack-infra08:46
ttxStevenK: we are phasing it out and using https://github.com/openstack/governance instead08:46
*** rongze has quit IRC08:46
*** rongze has joined #openstack-infra08:47
openstackgerritA change was merged to openstack-dev/hacking: Updated from global requirements  https://review.openstack.org/6128608:52
*** apevec has joined #openstack-infra08:52
*** nprivalova has joined #openstack-infra08:52
apevecfungi, ping - is there ci lp bug# for sphinx issue?08:54
apevechttps://review.openstack.org/61236 was merged but I don't see automatic proposals James mentioned?08:54
SergeyLukjanovapevec, https://review.openstack.org/#/q/owner:jenkins,n,z08:55
openstackgerritChangBo Guo proposed a change to openstack-dev/hacking: Fix typos of comment in module core  https://review.openstack.org/6111108:55
SergeyLukjanov^^ here are the auto proposed requirements updates08:55
SergeyLukjanovand here is the bug for sphinx08:55
SergeyLukjanovhttps://bugs.launchpad.net/openstack-ci/+bug/125951108:55
uvirtbotLaunchpad bug 1259511 in openstack-ci "sphinx docs gating jobs are broken (source_dir must be a directory)" [Critical,Fix released]08:55
apevecSergeyLukjanov, thanks!08:55
*** roeyc has joined #openstack-infra08:56
DinaBelovaSergeyLukjanov, thank you so much08:56
apevecSergeyLukjanov, so that's all for master08:56
apevecwhat about stable/havana08:56
SergeyLukjanovapevec, it'll be fixed after one fix merged08:57
SergeyLukjanovhttps://review.openstack.org/#/c/61304/08:57
openstackgerritChangBo Guo proposed a change to openstack-dev/pbr: Fix typos in documents  https://review.openstack.org/6111008:58
apevec  SergeyLukjanov ah ha! thanks for the pointers08:58
SergeyLukjanovnp08:58
*** jcooley_ has joined #openstack-infra09:00
*** afazekas has joined #openstack-infra09:02
*** jcooley_ has quit IRC09:04
*** senk1 has quit IRC09:05
*** yolanda has quit IRC09:06
*** boris-42 has joined #openstack-infra09:06
*** apevec has quit IRC09:06
*** yolanda has joined #openstack-infra09:07
*** Abhishek_ has quit IRC09:08
*** hashar has joined #openstack-infra09:11
*** jpich has joined #openstack-infra09:14
*** bingbu has quit IRC09:14
mattymoSergeyLukjanov, ping09:16
*** Abhishek_ has joined #openstack-infra09:17
*** locke105 has quit IRC09:17
*** avishayb has joined #openstack-infra09:18
*** hashar has quit IRC09:18
*** hashar has joined #openstack-infra09:22
StevenKttx: And it's only on github because?09:23
*** derekh has joined #openstack-infra09:23
SergeyLukjanovmattymo, pong09:24
ttxStevenK: it's not only on github, just mirrored there09:26
ttxhttp://git.openstack.org/cgit/openstack/governance/09:26
StevenKNot very user-friendly. But okay09:28
ttxStevenK: the goal is to get it publiched somewhere from there09:28
StevenKHowever, the core developer policy is under that wiki hierachy, and it isn't in that git repo09:28
ttxpublished*09:28
ttxStevenK: link?09:29
ttxthere are lots of very old wiki pages that may or may not still be relevant09:29
StevenKttx: https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess09:31
ttxStevenK: so that one predates the notion of PTL09:32
ttxsince then we established that PTLs have ultimate authority on a project matters09:33
ttxso they are free to pick whatever method they like to establish their core team09:33
ttxthat said, most still follow the ideas described in this document09:33
*** guohliu has quit IRC09:33
ttxSo that's superseded by https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee - section on Program Leads09:34
ttxthat page being a copy of http://git.openstack.org/cgit/openstack/governance/tree/reference/charter09:35
ttxGovernance/Approved/CoreDevProcess should no longer be linked from anywhere09:36
StevenKttx: I did a quick google this morning about core developer -- everything you're mentioning doesn't look to be well discoverable09:36
*** nosnos_ has joined #openstack-infra09:36
*** tsufiev has joined #openstack-infra09:37
*** sergmelikyan has joined #openstack-infra09:37
tsufievhi there! do you know about problem with new branch creation in review.openstack.org?09:37
ttxStevenK: https://wiki.openstack.org/ >> Governance >> Technical Committee09:38
SergeyLukjanovtsufiev, which problem?09:38
ttxStevenK: but yeah, Google will find stale pages on the wiki for sure09:38
tsufievwe've just tried to create a new branch for our murano repositories, but could not do that09:38
SergeyLukjanovtsufiev, have you checked ACL?09:38
ttxStevenK: and we should remove all non longer applicable pages, or at least move them to some attic/09:39
sergmelikyanWe created new branches around 2 month ago and all was OK, there was some changes?09:39
tsufievSergeyLukjanov: not yet. Where can it be done?09:39
SergeyLukjanovsergmelikyan, I don't think so09:40
SergeyLukjanovtsufiev, https://review.openstack.org/#/admin/projects/stackforge/murano-repository,access09:40
*** jooools has joined #openstack-infra09:40
*** nosnos has quit IRC09:40
SergeyLukjanovtsufiev, do you have any error message?09:40
ttxStevenK: there were lots of changes in the governance over the last 3 years, and the wiki still contains artifacts from that. If you're interested in history, I wrote up a summary of the evolution: http://fnords.wordpress.com/2013/06/20/history-of-openstack-governance/09:41
sergmelikyanhttp://i41.tinypic.com/sw5nio.jpg09:41
sergmelikyanError message :)09:42
*** denis_makogon has quit IRC09:42
sergmelikyanSimply Application Error: Cannot create refs/heads/release-0.409:42
tsufievSergeyLukjanov: actually, there is no special section for branch creation in Access section09:42
*** lifeless has joined #openstack-infra09:43
tsufievwait a minute... can this change have caused it https://review.openstack.org/gitweb?p=stackforge/murano-repository.git;a=commitdiff;h=c95e646aca6c6f12fcc9eed12c681e0efd219229 ?09:44
sergmelikyanhttps://github.com/openstack-infra/config/commit/9bbd07ee06fe656ad7687dd4bb725a5d6984360009:46
sergmelikyanIssue with ACL :( Thx!09:46
*** johnthetubaguy has joined #openstack-infra09:56
SergeyLukjanovsergmelikyan, np, exactly, you remove the ability to create refs09:57
*** jcoufal has quit IRC09:58
*** shardy_afk is now known as shardy10:01
*** katyafervent has joined #openstack-infra10:03
*** xchu has quit IRC10:04
*** senk has joined #openstack-infra10:05
*** senk has quit IRC10:10
*** heyongli has joined #openstack-infra10:10
*** rossella_s has joined #openstack-infra10:14
*** markmc has joined #openstack-infra10:14
*** bogdando has joined #openstack-infra10:15
*** Bada has joined #openstack-infra10:15
*** apevec has joined #openstack-infra10:17
*** apevec has joined #openstack-infra10:17
*** dizquierdo has joined #openstack-infra10:17
*** DinaBelova has quit IRC10:20
*** nprivalova has quit IRC10:20
*** SergeyLukjanov is now known as _SergeyLukjanov10:23
bogdandohello. What is typical work-flow  for creating WIP branches in gerrit for Openstack projects?10:24
bogdandoshould I send PRs to https://github.com/openstack-infra/config? What exactly should be changed? Any help with docs? Thank you.10:25
*** sarob has quit IRC10:26
sdaguettx: we should build a docs job for the governance repo10:31
sdagueso it publishes out to somewhere on openstack.org in pretty html10:31
ttxsdague: yes, or get them mirrored on the wiki: https://bugs.launchpad.net/openstack-ci/+bug/123305910:31
uvirtbotLaunchpad bug 1233059 in openstack-ci "Set up governance wiki pages as read-only copies of reference repo" [High,Triaged]10:31
ttxif not on wiki, we'll have to set up redirects -- the wiki URLs are cited in governance docs like bylaws.10:32
sdaguettx: honestly, I think the docs jobs are a better bet. Republishing to the wiki seems weird.10:33
lifelesswhy publish somewhere folk can edit and then say they can't edit10:34
ttxsdague: agreed, we just need to preserve links10:35
ttxso replacing charter with link to actual charter10:35
ttxlifeless: fwiw those pages are protected. they are on the wiki because that was the easiest option, not the best.10:36
ttxlifeless: I'm more scared to see the Foundation *bylaws* on the wiki, tbh10:36
*** senk has joined #openstack-infra10:43
*** che-arne has joined #openstack-infra10:43
*** senk has quit IRC10:47
openstackgerritTimur Sufiev proposed a change to openstack-infra/config: Enable new branch creation for murano.  https://review.openstack.org/6136910:47
*** senk has joined #openstack-infra10:48
*** jd__ has quit IRC10:48
*** jd__ has joined #openstack-infra10:48
tsufievmordred, fungi, clarkb: could you please review this change https://review.openstack.org/61369 ?10:50
*** bogdando has quit IRC10:51
*** mgagne has quit IRC10:52
*** Bada has quit IRC10:52
*** nosnos_ has quit IRC10:57
*** ativelkov has joined #openstack-infra10:57
*** nprivalova has joined #openstack-infra10:57
*** nosnos has joined #openstack-infra10:57
*** yaguang has quit IRC10:59
*** yhe_ has joined #openstack-infra11:04
*** zhiyan has quit IRC11:05
*** mgagne has joined #openstack-infra11:06
*** mgagne has quit IRC11:06
*** mgagne has joined #openstack-infra11:06
*** zhiyan has joined #openstack-infra11:06
*** heyongli has quit IRC11:06
*** zhiyan has quit IRC11:08
sdaguehmmm... I'm still getting that sphinx issue from yesterday, even with the pin locally11:08
*** nprivalova has quit IRC11:09
sdagueoh, that's why, sphinx 1.2b3 is out on pypi11:11
sdagueI wonder why that only sometimes was getting pulled11:11
apevecoh no again beta < release issue11:13
openstackgerritSean Dague proposed a change to openstack/requirements: change sphinx requirement to < 1.1.99 because 1.2b3 exists  https://review.openstack.org/6137811:13
sdagueyep11:14
apevecok, so just local builds, gate is not affected11:14
*** sarob has joined #openstack-infra11:16
*** lcestari has joined #openstack-infra11:16
*** Bada has joined #openstack-infra11:17
sdagueapevec: yeh, that's what it seems like11:19
sdaguemaybe we don't mirror betas to the gate?11:19
sdaguewhich would actually be bad11:19
sdaguettx: https://review.openstack.org/#/c/61380/11:20
apevecyeah, interesting to check how is mirroring comparing versions11:20
ttxsdague: nice11:20
sdaguetox -evenv -- python setup.py build_sphinx11:21
sdagueto test it11:21
sdagueand see what the output looks like11:21
*** rongze has quit IRC11:21
*** nati_ueno has joined #openstack-infra11:21
sdagueif we go down that path, I'll provide some patches to get the tree into something which builds nicely for all the docs11:21
*** senk has quit IRC11:21
*** rfolco has joined #openstack-infra11:22
apevecsdague, could you propose 61378 to stable/havana too? <1.2 hasn't been propagated yet to havana, so better we take yours version11:22
sdagueapevec: oh, sure11:22
*** Abhishek_ has quit IRC11:23
*** jcoufal has joined #openstack-infra11:24
*** roeyc has quit IRC11:24
*** talluri has quit IRC11:26
*** talluri has joined #openstack-infra11:27
sdagueapevec: https://review.openstack.org/#/c/61383/11:27
apevecsdague, I'd prefer the same changeid11:29
apeveclike https://review.openstack.org/#/q/I0487b4eca8f2755b882689289e3cdf429729b1fb,n,z11:29
*** talluri has quit IRC11:31
*** yhe_ is now known as heyongli11:33
sdagueapevec: ok11:33
*** bogdando has joined #openstack-infra11:33
*** yamahata_ has quit IRC11:33
tsufievjeblair: could you please review the change https://review.openstack.org/#/c/61369/ ?11:34
sdagueapevec: I wasn't sure how we were doing backports like that, fixed now11:35
sdaguetsufiev: it's at least 5 hrs before jeblair is awake11:35
sdagueand you just pinged about that 40 minutes ago11:36
*** paul-- has joined #openstack-infra11:36
*** paul-- has quit IRC11:37
*** talluri has joined #openstack-infra11:40
*** jcooley_ has joined #openstack-infra11:43
*** rongze has joined #openstack-infra11:44
openstackgerritA change was merged to openstack-infra/release-tools: Initial setup of python project layout  https://review.openstack.org/6084011:46
*** jcooley_ has quit IRC11:47
openstackgerritThierry Carrez proposed a change to openstack-infra/release-tools: Add mpcut.sh for milestone-proposed branch cutting  https://review.openstack.org/6138911:48
*** sarob has quit IRC11:48
*** DinaBelova has joined #openstack-infra11:57
*** hashar has quit IRC12:04
*** nprivalova has joined #openstack-infra12:04
tsufievsdague: I did not actually know what timezone he lives in :(. Just tried my luck.12:07
tsufievsdague: anyway, thank you for the info12:09
*** SergeyLukjanov has joined #openstack-infra12:10
*** [1]avishayb has joined #openstack-infra12:11
*** adalbas has joined #openstack-infra12:12
*** [2]avishayb has joined #openstack-infra12:12
openstackgerritTimur Sufiev proposed a change to openstack-infra/config: Enable new branch creation for murano.  https://review.openstack.org/6136912:13
*** sarob has joined #openstack-infra12:13
*** avishayb has quit IRC12:13
*** [2]avishayb is now known as avishayb12:13
BobBallsdague: do you know if only re-running the failed jobs on recheck/reverify has been considered?12:14
sdagueBobBall: meaning?12:14
*** [1]avishayb has quit IRC12:15
BobBallwell - we've got so many jobs running tempest now (and that number is likely to increase) if we have a reverify issued we currently re-run everything.  So if there was a failure rate of 1 in 5 and we ran 5 jobs every time, you're going to hit it on every recheck on average.12:16
BobBallWe're increasing the number of runs that we do - therefore we're increasing the chance of hitting an issue - even if it's a hypervisor issue12:16
ArxCruzALL: Does anyone saw this error before? http://paste.openstack.org/show/54815/12:16
BobBalljust thinking about reducing the chances that an instability would wedge check/gate jobs :)12:17
BobBallof course, we want to get rid of all instabilities too and it could be argued that making them have less of an impact would work against them getting fixed12:18
*** hashar has joined #openstack-infra12:21
*** nprivalova has quit IRC12:21
*** nprivalova has joined #openstack-infra12:26
openstackgerritSean Dague proposed a change to openstack-infra/devstack-gate: don't have grenade hit the network with apt, as the network breaks  https://review.openstack.org/6139912:26
sdagueBobBall: so the right thing to do there is help get rid of the races :)12:27
openstackgerritSergey Lukjanov proposed a change to openstack-infra/config: Make savanna-ml able to create branches  https://review.openstack.org/6140012:27
sdagueyeh, I think you'll find the qa and infra teams would be opposed to making it easier to ignore the system races.12:27
sdagueArxCruz: that means you have a syntax error in a test somewhere12:29
ArxCruzsdague: I just ran stack.sh in F1912:29
*** Bada has quit IRC12:29
ArxCruzchecking the logs I don't see anything wrong in devstack installation12:30
sdagueArxCruz: that's a syntax error in the tempest tree somewhere12:30
ArxCruzthere's a bunch of warnings like: warning: LocalManifestMaker: standard file '-c' not found12:30
BobBallI understand and agree with that - I'm just concerned that as we grow the chances of hitting gate blocking issues - or even just check blocking issues - could increase out of proportion, which is why I was asking if it had been considered ;)12:31
sdagueBobBall: actually, the intent is make smaller and smaller races blocking on the gate12:31
*** jcoufal has quit IRC12:31
sdagueso they get resolved12:31
sdaguebecause they don't otherwise12:32
BobBallbut it's not just races / bugs in OS that I'm thinking about12:32
BobBallbut anyway12:32
BobBallit's a hypothetical discussion ATM ;)12:33
BobBallI'm thinking that by the end of IceHouse we could easily have hyper-v, XS, KVM and vmware tested in the check jobs - and any bugs in those hypervisors would cause issues for everyone12:34
BobBallnot just in the drivers12:34
sdagueBobBall: they are check jobs though, so they aren't blocking. If it turns out they are racing they can be overridden by the reviewers12:38
sdaguejeblair: for when you get up, after all that ... openstack-ci-bugs is a closed group? :P12:39
*** ativelkov has quit IRC12:41
*** nprivalova has quit IRC12:42
BobBallbtw, sdague, while I've got you here...12:43
*** dkliban has quit IRC12:43
BobBallHow would you / can you trace back from an instance/cinder device to the test that left it hanging around?12:43
openstackgerritSergey Lukjanov proposed a change to openstack-infra/config: Improve storyboard gate jobs  https://review.openstack.org/6111912:43
*** dcramer_ has quit IRC12:43
BobBallI can easily get back to the request sent to cinder + nova but then how do you track it back to the actual test?12:43
sdagueBobBall: I don't think you can get the test, you can get the class if you are running with tenant isolation12:44
*** beagles has quit IRC12:44
sdagueas the classname of the test class is part of the tenant name12:44
BobBallyeah - I've got to that in a number of cases... but I'm still struggling to figure out why/how these aren't being cleaned up sometimes12:45
BobBall:)12:45
*** sarob has quit IRC12:45
sdaguehttp://youtu.be/qrzFuYyr8c4?t=20m46s12:48
sdagueBobBall: so I'd look at the tear down paths for those classes12:48
sdagueto make sure they are actually cleaning up correctly12:48
BobBallthey seem to be from my naieve understanding12:49
BobBallI'll dig more :)12:49
BobBallI was  hoping for some magic way to join the dots12:49
sdagueyeh, honestly, I'm not entirely convinced that cinder always cleans up right12:49
sdaguethe above youtube video is best I've got, that's where I talk about this at summit12:50
BobBallI'm watching ATM12:50
sdagueit's a little unfortunate that the charts are so blown out on that12:51
*** nprivalova has joined #openstack-infra12:51
*** dkliban has joined #openstack-infra12:51
*** senk has joined #openstack-infra12:53
BobBallI wonder if we should have a test that runs explicitely at the end to confirm there are no test tenants/VMs/volumes left lying around12:53
sdagueyeh, we've talked about that. Realistically it would be in the final tearDown on the basic class where we purge the tenant12:54
sdagueneeds someone to actually do it12:54
BobBallassuming that you do purge the tenant... I'm left with many tenants12:54
BobBallmany = a dozen or so, depending on what actually went wrong12:54
sdagueyeh, I expect the tenant purge probably fails when it has resources12:54
BobBallThe strange thing is I'm sure I've seen tenants + volumes left when a test passes12:55
BobBallbut anyway - needs more investigation before I can tie it down12:55
* BobBall loves random failures12:55
sdagueBobBall: yeh, so because deletes are async12:55
*** odyssey4me has quit IRC12:56
*** jcoufal-mob has joined #openstack-infra12:56
sdaguethey all pass with 202 return12:56
BobBallah12:56
sdagueso unless you explicitly wait around and check, they may not actually delete12:56
openstackgerritSean Dague proposed a change to openstack-infra/devstack-gate: don't have grenade hit the network with apt, as the network breaks  https://review.openstack.org/6139912:58
*** thomasbiege has quit IRC12:58
*** eharney has joined #openstack-infra12:58
*** [1]avishayb has joined #openstack-infra12:59
sdaguefungi: so when you get up - https://review.openstack.org/#/c/61399/ probably should fastpath13:00
*** thomasbiege has joined #openstack-infra13:00
*** vkozhukalov has quit IRC13:00
*** [2]avishayb has joined #openstack-infra13:00
*** tma996 has joined #openstack-infra13:01
*** avishayb has quit IRC13:02
*** [2]avishayb is now known as avishayb13:02
*** [1]avishayb has quit IRC13:03
*** nprivalova has quit IRC13:04
* fungi is not really here. stack of advisories going out, but i'll look once those are rolling13:05
*** nprivalova has joined #openstack-infra13:05
*** [1]avishayb has joined #openstack-infra13:06
*** sandywalsh_ has quit IRC13:07
sdaguefungi: so if advisories are going to include trying to land patches, that grenade patch should get looked at13:08
*** jcoufal-mob_ has joined #openstack-infra13:08
* fungi grumbles13:08
sdaguewell that d-g change should get looked at13:08
*** avishayb has quit IRC13:09
*** [1]avishayb is now known as avishayb13:09
sdaguebecause it's bouncing things on rax iad servers atm13:09
fungii take it grenade is wedging the gate?13:09
fungitoo fun13:09
sdaguewell... only partially13:09
fungiwell, rax nodes are check-only, not gate13:09
*** b3nt_pin has joined #openstack-infra13:10
*** sarob has joined #openstack-infra13:10
*** dprince has joined #openstack-infra13:11
*** Bada has joined #openstack-infra13:11
sdagueok, not just rax13:11
sdaguehttp://logs.openstack.org/27/61227/3/gate/gate-grenade-dsvm/3156471/console.html13:11
*** jcoufal-mob has quit IRC13:11
sdaguethat was an hp cloud one13:11
sdaguebasically apt.puppetlabs.com is timing out some times13:12
*** b3nt_pin has quit IRC13:12
*** b3nt_pin has joined #openstack-infra13:12
sdagueand... it turns out that grenade it actually doing an apt-get update under the covers13:12
fungiyeah, i think we already had a bug open with ideas toward a different solution13:13
fungiin particular, remove the puppetlabs apt repo (and any other unnecessary ones) at the end of the image prep in nodepool scripts13:13
sdagueok, any reason to not just revoke the apt-get update like I did it?13:13
fungiwhich would allow us to still hit the vendor mirrors13:14
sdagueright, but the vendor mirrors will be up to date within 24hrs, right?13:14
jog0ohh externeneral dependencies13:14
jog0external*13:14
fungimore or less. it seems like an okay compromise... do we not do apt upgrades in other dsvm jobs?13:14
fungijust grenade?13:15
*** nprivalova has quit IRC13:17
sdaguehmmm... we do it in devstack as well13:17
fungilooks like bug 1253774 was prompted by a grenade job as well13:17
uvirtbotLaunchpad bug 1253774 in openstack-ci "Reduce number of apt sources that must be up for gate to work" [Medium,Confirmed] https://launchpad.net/bugs/125377413:17
fungii want to say bug 1259911 is a duplicate of that one13:18
uvirtbotLaunchpad bug 1259911 in openstack-ci "apt.puppetlabs.com connectivity problem from rax breaks grenade job" [Undecided,In progress] https://launchpad.net/bugs/125991113:18
*** b3nt_pin is now known as beagles13:19
fungii guess i'd want to know, first, whether there are good reasons to be performing an apt-get update/upgrade at all in any of those jobs. i'm okay with considering https://review.openstack.org/61399 as a stop-gap if that's where it's hurting us most at the moment, but i'd rather solve this correctly (whatever correctly means in this case) and consistently once there's time to discuss further13:20
sdaguefungi: so, no, this hits us everywhere - http://logstash.openstack.org/#eyJzZWFyY2giOiJcIkZhaWxlZCB0byBmZXRjaCA8YSBocmVmPSdodHRwOi8vYXB0LnB1cHBldGxhYnMuY29tL2Rpc3RzL3ByZWNpc2UvUmVsZWFzZS5ncGcnPmh0dHA6Ly9hcHQucHVwcGV0bGFicy5jb20vZGlzdHMvcHJlY2lzZS9SZWxlYXNlLmdwZzwvYT5cIiIsImZpZWxkcyI6W10sIm9mZnNldCI6MCwidGltZWZyYW1lIjoiNjA0ODAwIiwiZ3JhcGhtb2RlIjoiY291bnQiLCJ0aW1lIjp7InVzZXJfaW50ZXJ2YWwiOjB9LCJzdGFtcCI6MTM4Njc2Nzk2MTk3OSwibW9kZSI6InRlcm1zIiwiYW513:20
sdaguehbHl6ZV9maWVsZCI6ImJ1aWxkX25hbWUifQ==13:20
*** yaguang has joined #openstack-infra13:20
*** sandywalsh_ has joined #openstack-infra13:20
sdagueso let me make that generically apply13:20
*** Bada has quit IRC13:21
*** prad has joined #openstack-infra13:23
sdaguehmmm... now that I think about it, that fix is probably not the right one. As it could mean an out of data index file for installing from the local mirrors13:25
*** talluri has quit IRC13:25
sdaguefungi: so your idea of removing the extra repos is probably a good one. Where should I do that.13:25
sdagueThis is something we've hit a lot apparently13:26
fungisdague: https://bugs.launchpad.net/openstack-ci/+bug/1253774/comments/113:26
uvirtbotLaunchpad bug 1253774 in openstack-ci "Reduce number of apt sources that must be up for gate to work" [Medium,Confirmed]13:26
fungidetails there13:26
fungishould be as simple as just deleting the additional repo files. any files in /etc/apt/sources.list.d/ are fair game i think...13:27
*** talluri has joined #openstack-infra13:27
fungithough if you look on one of your d-g nodes you spun up yesterday for manual tests, see what is in sources.list and sources.list.d which might not be needed for the tests to run13:28
*** smarcet has joined #openstack-infra13:28
* fungi puts his other hat back on for a couple hours13:29
sdaguehmm... interestingly.... it only seems to trigger the fail on the grenade jobs13:29
sdaguethe error is passed by in the devstack jobs most of the time13:30
*** jcooley_ has joined #openstack-infra13:30
*** dstanek has joined #openstack-infra13:35
*** sarob has quit IRC13:35
*** jcooley_ has quit IRC13:35
*** talluri has quit IRC13:38
sdaguefungi: so - https://review.openstack.org/61418 might actually be a sensible fix as well13:38
*** talluri has joined #openstack-infra13:38
*** jorisroovers has joined #openstack-infra13:39
fungisdague: that seems a little more resilient... if the update fails and you end up with outdated sources which fail to be able to install particular packages, you'll still get failures later but that can be diagnosed sanely i think13:39
sdagueyeh13:40
sdaguethis actually is only a grenade failure... after looking at logstash13:40
sdaguewe set -o errexit on all the upgrade scripts13:40
sdagueand we do this a lot in them13:40
sdagueso it's actually basically ignored effectively in all the devstack jobs13:41
sdaguejust the grenade jobs make it a failure13:41
sdaguealso, I thought we linked reviews to launchpad - https://bugs.launchpad.net/openstack-ci/+bug/1259911 ?13:42
uvirtbotLaunchpad bug 1259911 in openstack-ci "apt.puppetlabs.com connectivity problem from rax breaks grenade job" [Undecided,In progress]13:42
*** talluri has quit IRC13:43
sdagueor is that just launchpad racing and not taking updates13:43
*** paul-- has joined #openstack-infra13:44
sdagueok, if https://review.openstack.org/61418 passes I'll push it through13:45
sdaguefungi: please put your +1 on that if you like it.13:46
fungicould be lp. i can add that to the list of things to look at later13:46
fungiwill do13:46
openstackgerritA change was merged to openstack-dev/hacking: Add a check for file with only comments  https://review.openstack.org/5909013:46
fungii take it that's what devstack already does to get around it elsewhere?13:46
sdaguefungi: I dug in because this actually bounced the requirements updates13:46
sdaguefungi: well, we don't error there13:46
fungigrr13:46
fungiahh, okay13:47
openstackgerritA change was merged to openstack-infra/config: Fix branch logic in req propose script  https://review.openstack.org/6130413:47
sdaguegrenade is way more aggressive on using set -o errexit13:47
sdagueso in devstack... the update returns bad, but we don't check, and don't care13:47
fungiworks for me. in for a penny, in for a pound13:48
sdaguein grenade, errexit means even if we don't check, bash exits13:48
*** dkranz has joined #openstack-infra13:48
fungii'd rather we be consistently broken about it than have inconsistent workarounds. makes it easier if we choose differently later13:48
sdaguewe seem slightly resource starved, the job didn't start yet, waiting on d-g nodes13:50
sdagueoh, just got them13:51
fungimore just busy than starved, looks like13:51
*** bpokorny has joined #openstack-infra13:54
*** thomasbiege1 has joined #openstack-infra13:54
*** thomasbiege2 has joined #openstack-infra13:55
*** thomasbiege2 has quit IRC13:57
*** thomasbiege has quit IRC13:58
*** thomasbiege1 has quit IRC13:58
sdaguewell, now just the waiting14:00
*** dkliban has quit IRC14:01
*** NikitaKonovalov has joined #openstack-infra14:02
sdaguejog0: so yuo back in the states now?14:02
*** mfer has joined #openstack-infra14:04
*** bogdando has left #openstack-infra14:05
*** prad has quit IRC14:06
*** sarob has joined #openstack-infra14:06
*** nosnos has quit IRC14:06
openstackgerritA change was merged to openstack-infra/elastic-recheck: use grenade gate numbers, not check queue numbers  https://review.openstack.org/6130714:08
*** ryanpetrello has quit IRC14:09
*** ryanpetrello has joined #openstack-infra14:09
*** thomasem has joined #openstack-infra14:11
*** prad has joined #openstack-infra14:12
openstackgerritJoe Gordon proposed a change to openstack-infra/elastic-recheck: Add graph for gate hit count  https://review.openstack.org/6142914:13
jog0sdague: nope, in Barcelona but actually able to do work today14:14
*** dkliban has joined #openstack-infra14:14
*** sarob has quit IRC14:14
*** paul-- has quit IRC14:15
*** mriedem has joined #openstack-infra14:16
*** jcoufal has joined #openstack-infra14:17
sdagueman, you're as bad as mordred14:18
*** NikitaKonovalov has quit IRC14:19
openstackgerritSean Dague proposed a change to openstack-infra/elastic-recheck: refactor graphite stanzas for readability  https://review.openstack.org/6143314:20
katyaferventfungi, Hi!14:20
jog0sdague: I am seeing him on 3 continents in less then 10 days14:21
katyaferventWe realized why we can't create a new branch and prepare a fix https://review.openstack.org/#/c/61369/14:21
katyaferventPlease take a look at that. We needed in new branch)14:22
*** michchap has quit IRC14:24
jog0sdague: I was just about to work on http://paste.openstack.org/show/54592/14:24
jog0you want to do that one instead, your js is better then mine14:24
*** jcooley_ has joined #openstack-infra14:25
sdagueI actually wanted to get back to the datamine on gerrit for our categorization rate :)14:25
sdaguewas just doing this while babysitting the grenade patch14:25
jog0sdague: cool14:25
jog0i'll give it a whack then14:25
sdaguejog0: but if you can layer on top of that last change I put out there14:25
sdagueit would be good, as that should clean things up a bunch14:26
sdaguejog0: yuo mind if I just land 6143314:27
*** jgrimm has joined #openstack-infra14:27
*** jergerber has joined #openstack-infra14:27
*** jcoufal-mob_ has quit IRC14:27
*** sarob has joined #openstack-infra14:27
jog0go fir it14:28
*** weshay has joined #openstack-infra14:29
*** jcooley_ has quit IRC14:29
*** eharney has quit IRC14:30
*** sarob has quit IRC14:32
*** zhiyan has joined #openstack-infra14:32
*** nati_ueno has quit IRC14:33
*** [1]avishayb has joined #openstack-infra14:34
*** rnirmal has joined #openstack-infra14:34
*** oubiwan__ has joined #openstack-infra14:36
*** HenryG has quit IRC14:36
*** avishayb has quit IRC14:37
*** [1]avishayb is now known as avishayb14:37
*** mrodden has quit IRC14:39
anteayazaro: ah thank you14:41
*** alcabrera has joined #openstack-infra14:41
*** odyssey4me has joined #openstack-infra14:41
openstackgerritA change was merged to openstack-infra/elastic-recheck: refactor graphite stanzas for readability  https://review.openstack.org/6143314:44
openstackgerritJoe Gordon proposed a change to openstack-infra/elastic-recheck: Add graph for gate hit count  https://review.openstack.org/6142914:44
*** jergerber has quit IRC14:47
*** esker has joined #openstack-infra14:47
*** ativelkov has joined #openstack-infra14:47
*** jergerber has joined #openstack-infra14:48
sdaguefungi: do we have a way to move changes in the queue yet?14:48
fungisdague: nope14:48
*** mattray has joined #openstack-infra14:49
fungiwe have ways to blow away and reload the queue in a chosen order, but it's fairly time-intensive14:49
sdagueyeh, ok14:49
sdaguea lot more is failing in the gate than I expected, slowing that grenade change in getting anywhere14:49
*** jorisroovers has quit IRC14:49
fungitrust me, i feel your pain. much more today than usual14:50
*** SushilKM has quit IRC14:50
sdagueyep.14:50
*** mrodden has joined #openstack-infra14:50
*** yaguang has quit IRC14:51
sdagueI also need to figure out why the web console updates only seem to take some times14:51
fungii think there must be something going on with rackspace's network, because the change i merged to get stable requirements updates working doesn't seem to be making it to the proposal slave. timeouts from puppet agent trying to talk to the master14:52
openstackgerritJoe Gordon proposed a change to openstack-infra/elastic-recheck: Add check pipeline graphs  https://review.openstack.org/6144414:52
fungigonna have to hand-patch it in14:52
fungierr: Could not retrieve catalog from remote server: Connection reset by peer - SSL_connect14:52
*** marun has quit IRC14:53
*** dhellmann has joined #openstack-infra14:53
katyaferventfungi, Thanks a lot!14:54
mattraywhat's the proper way to get a repository removed from GitHub? Specifically https://github.com/openstack/openstack-chef14:54
mattraydprince is on board with this, this repo is out of date and unmaintained, we prefer that people use the StackForge cookbooks14:54
fungimattray: it's a historical artifact. we have an unresolved on-again/off-again discussion about how we should treat projects which we host, which are now defunct14:55
fungithat is one of several14:55
mattrayfungi: so we just update the README with that for now?14:55
fungimattray: i think so. bit shouty warnings all over14:55
fungier, big14:56
mattraydprince: I'll send you a shouty pull request?14:56
dprincemattray: cool14:56
fungimattray: gerrit review14:56
mattrayfungi: is that repo even under gerrit review?14:56
openstackgerritA change was merged to openstack-infra/config: Enable new branch creation for murano.  https://review.openstack.org/6136914:57
fungithat's part of the problem. it's a project in gerrit14:57
*** jcoufal-mob has joined #openstack-infra14:59
sdaguefungi: that apt.puppetlabs.com problem is happing from hp-az3 as well15:03
sdagueso it's probably puppet's fault15:03
mattraydprince: https://review.openstack.org/#/c/6145015:03
mattrayfungi: ^^15:03
dprincemattray: approved15:03
*** alcabrera is now known as alcabrera|afk15:03
*** SergeyLukjanov_ has joined #openstack-infra15:03
mattraythanks!15:03
*** yaguang has joined #openstack-infra15:04
katyaferventfungi, Do we need to restart anything or changes in acl configs applies right away?15:05
fungikatyafervent: they'll probably take about another 10 minutes15:05
sdaguefungi: fwiw, the top of the gate went in 3h 45m ago15:05
*** freyes has joined #openstack-infra15:05
katyaferventfungi, Thanks!15:05
fungisdague: yeah, doesn't bode well for all these dozen patches i have going into various projects15:06
*** SergeyLukjanov has quit IRC15:06
sdagueyeh15:06
sdaguehow much of the gate is yours right now?15:06
*** vkozhukalov has joined #openstack-infra15:08
*** boris-42 has quit IRC15:08
fungihonestly, no idea. they'll begin triclking in as stable branch maintainers and core reviewers reapply their preapproval from the bugs15:08
*** jcoufal has quit IRC15:08
*** eharney has joined #openstack-infra15:09
*** jcoufal-mob has quit IRC15:10
*** SergeyLukjanov has joined #openstack-infra15:10
*** SergeyLukjanov_ has quit IRC15:12
*** HenryG has joined #openstack-infra15:13
jog0http://paste.openstack.org/show/5483415:13
jog0gate failure rate = 57.76%15:13
sdaguejog0: yeh15:13
jog0sdague: pragmatically calculated this time15:14
*** spredzy has joined #openstack-infra15:14
pabelangerGuess you guys are fighting with apt.puppetlabs.com being down?15:15
*** jcoufal has joined #openstack-infra15:15
*** mrmartin has joined #openstack-infra15:16
mrmartinhi15:17
*** jcooley_ has joined #openstack-infra15:18
*** odyssey4me has quit IRC15:19
*** mattray has left #openstack-infra15:21
*** sarob has joined #openstack-infra15:21
*** talluri has joined #openstack-infra15:22
mattymofungi, did you see the issue my colleague Roman Vyalov (rvyalov@mirantis.com) reported?15:22
*** julim has joined #openstack-infra15:23
*** jcooley_ has quit IRC15:23
sdaguepabelanger: well, there is a work around trying to get through the gate15:23
*** NikitaKonovalov has joined #openstack-infra15:24
*** sarob has quit IRC15:26
*** mrmartin has quit IRC15:26
*** sarob has joined #openstack-infra15:27
fungimattymo: i haven't caught up on scrollback, mailing list or non-security bugs yet today. i'll try to have a look in another hour or so15:28
mattymofungi, in gerrit rvyalov@mirantis.com has two entries and neither can be selected as Reviewer15:29
mattymoI imagine somehow he registered twice15:29
fungimattymo: it's not uncommon to find duplicates in there. i can clean it up later today15:29
mattymothat's perfect15:30
mattymothanks15:30
fungigerrit considers e-mail addresses to be unique between accounts, and then has trouble when that assumption is invalid15:30
fungibut there are places where it doesn't prevent address duplication. mainly when it comes in via openid i think15:31
mattymomore like openevil15:31
fungiso having more than one launchpad account or changing/merging lp accounts has a tendency to cause this15:31
*** sarob has quit IRC15:32
*** oubiwan__ is now known as oubiwann-lambda15:35
*** datsun180b has joined #openstack-infra15:35
*** rcleere has joined #openstack-infra15:36
*** leifmadsen has quit IRC15:36
mordredomg backscroll15:40
*** jorisroovers has joined #openstack-infra15:40
*** heyongli has quit IRC15:41
sdaguetl;dr - apt.puppetlabs.com periodic flakiness causing grenade job issues - fix in gate - fix probably 4 - 6 hrs from landing based on current reset rate15:41
*** jorisroovers has quit IRC15:46
*** jroovers has joined #openstack-infra15:46
*** changbl has quit IRC15:46
*** dims has quit IRC15:46
mordredwow15:48
pabelangersdague, Ya, some of my boxes are failing to run puppet, since it is down.15:49
openstackgerritMate Lakat proposed a change to openstack-infra/nodepool: Support install phase with nodepool  https://review.openstack.org/6146315:50
sdaguemordred: also, sphinx req fix was wrong15:50
sdaguebecause 1.2b3 is a pypi version15:50
*** senk has quit IRC15:51
jeblairsdague: what's the puppetlabs fix?15:51
sdaguejeblair: https://review.openstack.org/#/c/61418/15:51
mordredsdague: wait - what?15:52
sdaguebasically grenade runs a lot more under set -o errexit15:52
*** dizquierdo has quit IRC15:52
mordredsdague: what does "is a pypi version" mean15:52
jeblairyou know, if any infra-cores want to review https://review.openstack.org/#/c/60644/ we could push changes to the top of the queue.15:53
mordredjeblair: looking15:53
sdaguemordred: pip install sphinx < 1.2 installs 1.2b315:53
sdagueI have no idea why it doesn't do it in the gate some times15:53
mateljeblair: a patch regading to node install is uploaded: https://review.openstack.org/61463 - could you look at it to see if I'm on the right path or not?15:53
mordredjeblair: gah - I keep opening these to look at them and then keep getting distracteed15:53
mordredsdague: pip version15:53
sdague1.4.115:54
jeblairmatel: yes, but probably not right away15:54
mordredit should ignore that.15:54
sdaguewell it didn't15:54
*** julim has quit IRC15:54
mateljeblair: sure.15:54
*** rcleere has quit IRC15:55
sdagueI couldn't add the docs build to openstack/governance until I pinned at 1.1.9915:55
mordredsdague: and you're sure that docs build was running somewhere sensible? that had pip 1.4?15:56
sdaguemordred: on my laptop15:56
sdagueunder tox15:56
mordredwth. I just reproduced15:57
sdagueor... not laptop. my desktop. but my primary computer for dev :)15:57
sdagueso used to saying laptop15:57
mordredwait. no I didn't15:58
mordredhttp://paste.openstack.org/show/54840/15:58
*** yolanda has quit IRC15:59
pabelangerjeblair, new hotness! Great feature15:59
*** jorisroovers has joined #openstack-infra15:59
*** changbl has joined #openstack-infra15:59
clarkbsdague see my -215:59
sdaguemordred: I don't know, I went around and around on that one16:00
sdaguemordred: sure it acts the right way under tox?16:00
sdagueand pbr16:00
*** mestery has quit IRC16:00
clarkbit doesnt see my -2 :)16:00
sdagueclarkb: which -216:00
clarkbon the requirements change to <1.19916:01
*** rcleere has joined #openstack-infra16:01
sdagueok16:01
*** dims has joined #openstack-infra16:01
clarkbportante and I sorted this for swift yesterday16:01
sdagueok16:02
*** AaronGr_Zzz is now known as AaronGr16:02
sdagueso there are then plenty of trees that need this tox update16:02
*** jroovers has quit IRC16:03
clarkbpossibly16:03
fungiyes. most of them in fact16:03
clarkbmordred can weigh in on that?16:03
fungii did get the requirements proposal re-run with jeblair's latest patch in place, but haven't circled back around to see whether it did the right thing16:04
clarkbmordred usually proposes changes like this across the world. was this just missed?16:04
sdagueso I copied tempest bits to governance, so tempest definitely doesn't have this16:05
*** SergeyLukjanov has quit IRC16:05
*** NikitaKonovalov has quit IRC16:05
sdaguethere were others that were commenting on the patch that they were hitting this issue as well16:05
sdagueas it's also a backport, it means that doing tox patches on havana branches as well16:05
*** afrittoli has quit IRC16:06
*** DinaBelova has quit IRC16:06
*** rcarrillocruz has joined #openstack-infra16:06
sdagueI'm happy if the answer is mordred fixes the tox world :)16:06
*** andreaf has joined #openstack-infra16:06
openstackgerritMate Lakat proposed a change to openstack-infra/nodepool: Support install phase with nodepool  https://review.openstack.org/6146316:07
yaguanghi , for this bug  sphinx docs gating jobs are broken16:07
*** dizquierdo has joined #openstack-infra16:08
yaguangafter fix is merged , but why  stable cinder gating still fails16:08
clarkbmordred: have you left us? curious if that was a nova only workaround for site packages?16:08
yaguangbug is here https://bugs.launchpad.net/openstack-ci/+bug/125951116:09
uvirtbotLaunchpad bug 1259511 in openstack-ci "sphinx docs gating jobs are broken (source_dir must be a directory)" [Critical,Fix released]16:09
*** elasticio has joined #openstack-infra16:09
clarkbyaguang was the fix applied to the stable branch?16:09
*** alcabrera|afk is now known as alcabrera16:11
*** dstanek has quit IRC16:11
apevecyaguang, "Updated from global requirements" aren't merged yet https://review.openstack.org/#/q/owner:jenkins+branch:stable/havana,n,z16:11
apevecfungi, ^^^ btw how come only cinder, ceilo and glance??16:11
apevecshould be all projects, rihgt?16:11
*** jorisroovers has quit IRC16:11
fungiapevec: i've got another patch coming--that fix was insufficient16:11
apevecbad day to go public with cves, heh16:12
fungiapevec: no kidding16:12
yaguangapevec, thanks to point it out, and I think we still need to fix stable/grizzly  right ?16:12
apevecyaguang, yes, grizzly needs iso8601 fix and this sphinx cap in each project16:13
apeveclatter would be manual job, I don't think "updates from global" is working for stable/grizzly16:14
*** dstanek has joined #openstack-infra16:14
fungiapevec: keep in mind that sphinx fixes for grizzly will probably need to be piecemeal. the global requirements implementation for grizzly is a work in progress since we didn't have any enforcement back then16:14
jeblairapevec: it may or may not work; but the change to reqs for sphinx hasn't landed because of the iso8601 issue: https://review.openstack.org/#/c/61237/16:15
apevecfungi, ack16:15
yaguangapevec, iso8601  blocks any nova   backport to stable/grizzly16:15
fungiand thus there is no strong consistency between requirements lists on grizzly branches of projects16:15
apevecright, re. iso8601 I've asked Glance core to chime in https://review.openstack.org/5593916:15
*** jcooley_ has joined #openstack-infra16:15
apevecnow waiting for their PTL to approve16:15
apevecif anyone sees markwash send him to that review :)16:16
jeblairclarkb: what was your question for mordred?  maybe we can figure out the answer.16:16
clarkbjeblair: looking for possible reasons line 9 of nova's tox.ini isn't ubiquitous16:17
jeblairclarkb, mordred, fungi: and if anyone wants to +2 https://review.openstack.org/#/c/60644/ i'll restart zuul and reorder the queue.16:17
clarkbit overrides the tox pip install command disabling prerelease dependencies by default16:18
*** jcooley_ has quit IRC16:20
*** weshay has quit IRC16:22
jeblairclarkb: https://review.openstack.org/#/c/42178/16:22
jeblairclarkb: my recollection of his plan was that that change should go everywhere16:22
jeblairclarkb: i see no evidence he proposed a change like that to any other project though.16:22
jeblairclarkb: oh, here's 1: https://review.openstack.org/#/c/57170/16:23
mordredah. yes. we should put that everywhere16:23
mordredI forgot about that16:24
jeblairmordred: are you in a position to script that now?16:24
mordredjeblair: my internet here is TERRIBLE16:24
jeblairmordred: okay, i will work on spamming all projects with the tox change16:25
*** julim has joined #openstack-infra16:25
clarkbthanks. I am reviewing zuul change now16:25
jeblairdoes the tox change need to include the sphinx <1.2 version pin?16:25
*** reed has joined #openstack-infra16:26
apevecpip -U prevents prereleases?16:27
jeblairapevec: i think the default tox command allows pre-release, and we're omitting something from it.16:28
*** talluri has quit IRC16:28
*** boris-42 has joined #openstack-infra16:28
*** talluri has joined #openstack-infra16:28
*** jcoufal has quit IRC16:28
clarkbjeblair this is only a problem for folks at home so it can be a separate change16:29
jeblairclarkb: ok, thx16:29
clarkbthe mirror protects the gate iirc16:29
clarkbsdague ^ that right?16:29
apevecdefault:16:30
apevecpip install --pre {opts} {packages}16:30
*** prad_ has joined #openstack-infra16:31
sdagueclarkb: it was definitely not being seen in the gate, and I expect that's why16:31
*** prad has quit IRC16:31
*** prad_ is now known as prad16:31
jeblairapevec: i believe '--pre' means 'allow prerelease versions'16:32
apevecyep16:32
*** cody-somerville has joined #openstack-infra16:32
*** cody-somerville has quit IRC16:32
*** cody-somerville has joined #openstack-infra16:32
apevec--pre16:32
apevecInclude pre-release and development versions. By default, pip only finds stable versions.16:32
*** talluri has quit IRC16:33
jeblairclarkb: this lgty? https://review.openstack.org/#/c/61473/16:33
*** jcooley_ has joined #openstack-infra16:33
*** yaguang has quit IRC16:34
jeblairoh, i should probably amend the commit msg to mention the --pre thing16:34
clarkb++16:34
jog0jeblair: can you convert some code into js for me?16:34
*** Ryan_Lane has joined #openstack-infra16:34
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Check that the target branch exists  https://review.openstack.org/6147516:35
fungijeblair: clarkb: ^ latest attempt to fix the reqs proposal for stable branches16:35
jog0jeblair: my javascript is non existent16:35
fungijeblair: clarkb: current state with the patch from last night... https://jenkins.openstack.org/job/propose-requirements-updates/41/console16:35
jog0jeblair: http://paste.openstack.org/show/5484116:36
*** weshay has joined #openstack-infra16:36
mordredapevec: tox decided that backwards compat behavior by default was more important than sanity :)16:36
jog0code to calculate gate failure rate.  sdague ^ same16:36
clarkbjeblair: for the zuul change. if line 556 of the scheduler throws a key error won't that crash the scheduler? A test seems to cover this with less horrible results. I guess the scheduler has a catch all exception handler16:36
apevecmordred, that's... toxic16:36
mordred:)16:36
jog0jeblair sdague:  I got this far and am stuck with js http://paste.openstack.org/show/5484216:37
sdaguejeblair: so I think I can replicate the elastic-recheck page without the pickle or the daemon through gerrit bulk query that could run on cron16:37
jeblairclarkb, mordred: review commit msg: https://review.openstack.org/#/c/61473/16:38
jeblairsdague: ++16:38
mordredjeblair: ++16:38
sdagueI'm writing some classes for looking up things in gerrit that elastic search needs, like which bugs are people rechecking against that aren't on our list16:38
jeblairjog0: sorry, firefighting now; will look later if you're still stuck16:39
*** SushilKM has joined #openstack-infra16:39
clarkbjeblair lgtm16:39
openstackgerritA change was merged to openstack-infra/zuul: Refactor reconfiguration into a management event  https://review.openstack.org/6062316:40
jog0jeblair: no problem thanks.  there is no rush, its more of I don't knwo any javascript and throwing this over the fence.  And its something I think we all want16:40
jog0I will put up a review as as WIP  for it16:40
jeblairclarkb: see line 697 for the exception handler that will catch that case and send the traceback to the client16:41
fungiwow, gerrit's diff algorithm made a serious mess of 61475 in the webui16:41
sdaguejog0: I'm not really quite sure that that is, but WIP with a big explaination of what the intent is16:41
openstackgerritJoe Gordon proposed a change to openstack-infra/elastic-recheck: WIP: Add gate failure rate number to status page  https://review.openstack.org/6148016:43
jog0sdague: ^16:43
zarogood morning16:44
*** rcleere has quit IRC16:45
clarkbjeblair see inline comment16:45
clarkbonce I wrap my head around the inline comment there I think this may be ready to go16:45
clarkbzaro: morning16:46
*** rcleere has joined #openstack-infra16:46
*** afazekas has quit IRC16:46
jeblairclarkb: rplied16:47
*** ^d has joined #openstack-infra16:48
fungii love it when changes merge while i'm reviewing them, and i don't even notice for 10 minutes. reminds me of just how painfully slow my code reading comprehension really is16:50
clarkbjeblair: +216:50
jeblairfungi: or how thorough you are16:50
*** SushilKM has quit IRC16:51
fungiwell, i also don't like to hold up the boat16:51
*** rongze_ has joined #openstack-infra16:51
*** dcramer_ has joined #openstack-infra16:51
jeblairfungi: that doomed ship's gotta sail!16:52
fungiundeed16:52
*** rongze__ has joined #openstack-infra16:52
*** rongze has quit IRC16:52
* fungi hoists the mainsail16:53
*** gothicmindfood has joined #openstack-infra16:54
fungi60644 lgtm16:54
*** SushilKM has joined #openstack-infra16:56
*** mestery has joined #openstack-infra16:56
*** rongze_ has quit IRC16:56
jeblairclarkb: several projects do have the new tox settings (ceilo, keystone) but not all16:56
*** klrmn has joined #openstack-infra16:57
clarkbfungi: for 61475, is it possible the branch won't be in the packed refs? we may want to try a git branch -a instead?16:57
*** SushilKM has quit IRC16:58
*** SushilKM has joined #openstack-infra16:59
fungiclarkb: good question. the ones i tested manually, the only way to confirm the remote branches existed without changing into the directory and using git commands was to grep through the pack. i'll do a new patchset with what i think the git branch -a solution would look like instead17:00
clarkbfungi: loose refs like loose objects are technically possible I think17:00
jeblairwhat is 'distribute=False' in a tox.ini?17:00
fungii thought that told tox not to install distribute (install setuptools instead)17:01
fungisince it needs to make the virtualenv with one or the other17:01
jeblairi've only seen it in oslo.config, not any others17:01
*** herndon has joined #openstack-infra17:02
*** herndon has quit IRC17:04
*** pmathews has joined #openstack-infra17:04
sdaguejog0: I take it you would probably react poorly to me adding 37 MB of gerrit test data to er?17:04
*** acabrera has joined #openstack-infra17:04
*** HenryG has quit IRC17:04
*** dcramer_ has quit IRC17:05
*** HenryG has joined #openstack-infra17:05
zaromordred: questions for you on https://review.openstack.org/#/c/6034817:05
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Check that the target branch exists  https://review.openstack.org/6147517:06
fungiclarkb: ^ git branch -a alternative17:06
*** alcabrera has quit IRC17:07
zaroclarkb: too cold to come in today17:07
clarkbfungi: ty17:08
mordredjeblair: it's not needed anymore. it used to be needed17:08
*** acabrera is now known as alcabrera17:08
clarkbzaro: :( I am headed in shortly17:08
jeblairmordred: ok.  i'll probably just ignore for now; but we could probably do a pass through and remove that.17:09
zaroclarkb: have a nice walk :)17:09
mordredzaro: we do the publisher in the check jobs so that we can install the war produced on review-dev without needing to land the change first17:09
mordredzaro: you'll notice that it publishes to a subdir17:10
*** tma996 has quit IRC17:10
mordredzaro: 'tarballs/ci/test/'17:10
*** rongze__ has quit IRC17:11
*** freyes has quit IRC17:11
zarook. i see the reason.  but don't you want to  install war after gate ?17:11
mordrednope17:11
mordredbecause a lot of times the way we test it for the gate is by instaling the war on review-dev17:12
mordredand that might need a few iterations17:12
zarogotcha.  will add deployment to the check job then.17:12
mordredthanks!17:12
*** nprivalova has joined #openstack-infra17:12
mordredthe other thing I'm meh on - I'm fine with it being there17:13
sdague763 reviews have seen activity in the last 24hrs.... if I make my dataset 4hrs I can cut it down to about 350 reviews ... still kind of impressive17:13
*** bodepd has quit IRC17:13
*** bodepd has joined #openstack-infra17:13
*** resker has joined #openstack-infra17:14
*** weshay has quit IRC17:14
*** hashar has quit IRC17:14
openstackgerritA change was merged to openstack-infra/zuul: Add a promote client command  https://review.openstack.org/6064417:15
*** esker has quit IRC17:15
*** weshay has joined #openstack-infra17:16
sdaguewoot17:16
*** rongze has joined #openstack-infra17:17
sdaguejeblair: 61418,2 is the one we want on top17:17
fungizaro: part of the backstory there is that sometimes the (old) gerrit build process would pack javascript improperly and result in broken warfiles17:18
*** johnthetubaguy has quit IRC17:18
fungiseemingly at random17:18
dkranzmordred: Do you have the gerrit link for the "gate on client library stability" patch?17:19
mordreddkranz: https://review.openstack.org/#/c/41931/17:19
dkranzmordred: Thx17:20
*** thomasem has quit IRC17:20
mordreddkranz: if you fix it, I'll buy you a puppy17:20
jeblairsdague: ack, will start on that in ~10 mins17:20
*** SergeyLukjanov has joined #openstack-infra17:20
jeblairsdague: is there a bug for the apt.puppetlabs issue?17:24
jeblairfungi: ^?17:24
tsufievwhat can still prevent murano from creating new branches? Though https://review.openstack.org/#/c/61369/ is merged, we still don't see 'create' permission in refs/heads/*, nor can actually create a branch17:24
sdaguejeblair: https://bugs.launchpad.net/openstack-ci/+bug/125991117:25
uvirtbotLaunchpad bug 1259911 in openstack-ci "apt.puppetlabs.com connectivity problem from rax breaks grenade job" [Undecided,In progress]17:25
fungijeblair: bug 1253774 and bug 125991117:26
uvirtbotLaunchpad bug 1253774 in openstack-ci "Reduce number of apt sources that must be up for gate to work" [Medium,Confirmed] https://launchpad.net/bugs/125377417:26
uvirtbotLaunchpad bug 1259911 in openstack-ci "apt.puppetlabs.com connectivity problem from rax breaks grenade job" [Undecided,In progress] https://launchpad.net/bugs/125991117:26
fungijust found them in scrollback17:26
fungioh, i guess sdague already did too17:26
jeblairi think 1259911 is the one we want to promote for reverifies17:27
* zaro wonders if it's kosher to share projects via a review?17:27
fungitsufiev: it's possible there's a problem with puppet applying that change on gerrit17:27
jeblairzaro: what do you mean?17:27
ativelkovfungi: is there anything we can do to fix it?17:28
*** SushilKM has quit IRC17:28
fungioh, right, clarkb: jeblair: mordred: also seen this morning but haven't had time to troubleshoot yet. puppet timeouts on ssl interactions with ci-puppetmaster. i worked around it on proposal.slave where i saw it by hand-applying the change i was waiting on17:28
jeblairfungi: we should check ci-puppetmaster load17:28
fungibut there's every chance it's hitting us elsewhere too--i haven't had time to look yet17:28
zarojeblair: i wanted to share my modified jjb project with mgagne .17:28
fungihaving a look now17:29
jeblairzaro: what do you mean by project?17:29
zarojeblair: changes i guess.  changes that i would never want merged.17:29
fungiativelkov: patience. we've got a stack of problems in the infrastructure and gating we're trying to resolve all at once17:29
zarojeblair: so maybe upload then abandone17:29
fungiload average on the puppet master is trivial, but maybe it wasn't earlier. checking graphs17:30
ativelkovfungi: thanks17:30
mgagnezaro: draft :D17:30
*** blamar has joined #openstack-infra17:30
*** gyee has joined #openstack-infra17:30
mordredzaro: yeah - or draft - which you can then explicitly give permission to someone else17:30
zarowhat's the difference?17:30
jeblairmordred: can you look at tox.ini in savanna-dashboard? they have an extra testenv section and i wonder what's going on.17:31
*** ^demon has joined #openstack-infra17:31
*** ^demon has joined #openstack-infra17:31
mordredyup17:32
*** reed has quit IRC17:32
SergeyLukjanovjeblair, mordred, is the tox.ini incorrect in savannas-dashboard?17:32
mordredSergeyLukjanov: it's weird - what do you guys use the tests env for?17:33
*** ^demon has quit IRC17:33
*** dims has quit IRC17:33
SergeyLukjanovmordred, does you mean [testenv:tests]?17:33
mordredSergeyLukjanov: and why do you have sitepackages=true? is that on purpose?17:33
SergeyLukjanovmordred, if yes - it's for selenium tests17:33
mordredSergeyLukjanov: yes17:33
*** ^demon has joined #openstack-infra17:33
mordredSergeyLukjanov: how do you call it?17:33
mordredoh. duh. brain dead17:34
SergeyLukjanovmordred, tox -e tests, but we're executing it in savanna-ci17:34
SergeyLukjanovmordred, checking file history to understand why sitepackages=true was used17:34
*** ^d has quit IRC17:35
jeblairwe run selenium for django17:35
jeblairgah17:35
jeblairwe run selenium for horizon17:35
openstackgerritJames E. Blair proposed a change to openstack-dev/hacking: Add -U to pip install command in tox.ini  https://review.openstack.org/6151717:36
*** nprivalova has quit IRC17:36
*** ^demon has quit IRC17:36
jeblairokay, i've done all the openstack projects in projects.txt17:36
*** ^d has joined #openstack-infra17:36
jog0sdague: haha yes17:37
SergeyLukjanovmordred, I'll remove sitepackages=true asap17:38
mordredSergeyLukjanov: cool17:38
mordredSergeyLukjanov: you can probably just remove all traces of it17:39
*** dims has joined #openstack-infra17:39
jeblairSergeyLukjanov: can you look at what we do for horizon and see if you can run the selenium tests in the openstack gate?17:39
SergeyLukjanovjeblair, I do17:39
SergeyLukjanovjeblair, we have someone assigned to it and verdict was that - nope, we can't17:39
*** oubiwann-lambda has quit IRC17:40
SergeyLukjanovjeblair, oh, I remember, this tests are not functional, but integration - we're creating hadoop clusters and run jobs on them17:40
*** chandankumar has quit IRC17:41
jeblairfungi: i logged into zuul; puppet has not updated the git repo since last night17:42
jeblairfungi: continual ssl errors17:43
*** thomasem has joined #openstack-infra17:43
*** thomasem has quit IRC17:44
*** thomasem has joined #openstack-infra17:44
fungijeblair: yes, it looks like the puppet master process was restarted this morning at 05:37 (haven't narrowed down the cause yet, assuming cron job, maybe log rotation, no mention of it in the dpkg log), and after that the graphs for the master flatlined17:44
fungitrying to restart it but i think i may have the wrong initscript for the master process though... i guess it's not puppetqd?17:45
SergeyLukjanovjeblair, thanks for the tox.ini update17:45
SergeyLukjanovmordred, done, will be merged soom17:46
SergeyLukjanovsoon*17:46
jeblairfungi: apt.puppetlabs being down plus this is a strange coincidenc.17:46
fungijeblair: i feel the same17:46
SergeyLukjanovis there still problems with propose-requirements-updates on non-master branch?17:47
*** dstanek has quit IRC17:47
jeblairrestarting zuul17:47
mordredfungi: puppetmaster is run through apache17:47
mordredit's a passeger thing17:47
fungiSergeyLukjanov: yes, https://review.openstack.org/6147517:47
mordredfungi: restarting apache is what you want17:47
*** dstanek has joined #openstack-infra17:47
fungimordred: aha! thanks muchj17:48
sdaguegrrr.... gerritlib is driving me nuts if I search with multiple queries it's only returning data for the first one17:48
*** jooools has quit IRC17:48
SergeyLukjanovfungi, oh17:48
fungimordred: looks like you already did. thanks again17:48
mordredfungi: I did not17:49
mordredfungi: I did not touch anything - I just logged in to look at the load17:49
*** senk has joined #openstack-infra17:49
fungier17:49
fungiperhaps apache started new master threads on its own17:49
fungis/threads/processes/17:49
fungirestarting now in that case17:50
*** rcarrillocruz1 has joined #openstack-infra17:50
fungiin case it's an apache issue17:50
pabelangerI've had a heck of a time with puppetmaster-passenger recently, so much so, I actually when back to just using the native puppetmaster17:50
*** rcarrillocruz has quit IRC17:50
jeblairzuul restarted and queue reloaded17:52
fungijeblair: clarkb: mordred: after a good clean restart of apache on ci-puppetmaster, i can pull puppet configs from it successfully again17:52
mordredfungi: that's SPECTACULAR17:52
*** acabrera has joined #openstack-infra17:52
funginot so much spectacular as really annoying17:53
fungithe other spectacular17:53
sdaguejeblair: neat17:53
sdaguewith any luck we'll start landing things quickly17:53
*** senk has quit IRC17:53
*** alcabrera has quit IRC17:55
*** SushilKM has joined #openstack-infra17:56
*** acabrera is now known as alcabrera17:56
*** derekh has quit IRC17:57
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Remove 'reverify no bug'  https://review.openstack.org/6152217:59
mordredjeblair: can I +A that? or should I just +2?18:01
jeblairmordred: +A at will18:02
*** sdake_ has joined #openstack-infra18:02
mgagnemordred: ironically, gate will fail and reverify no bug will be used.18:02
fungithe -dev ml got a couple days notice18:02
jeblair#status alert Grenade gate infra issues: use "reverify bug 1259911"18:03
openstackstatusNOTICE: Grenade gate infra issues: use "reverify bug 1259911"18:03
uvirtbotLaunchpad bug 1259911 in openstack-ci "apt.puppetlabs.com connectivity problem from rax breaks grenade job" [Undecided,In progress] https://launchpad.net/bugs/125991118:03
*** ChanServ changes topic to "Grenade gate infra issues: use "reverify bug 1259911""18:03
sdaguejog0: how about 4M of json? that's about as small as I can get and still have it be a real slice with enough variants18:03
pmathewsmordred: Can I get you to review this: https://review.openstack.org/#/c/59875/318:04
jog0sdague: I can live with that as long as its not 4k files or something18:04
sdagueit's one file18:05
jog0cool, and I assume you will document how it was created so when the schema we use gets out of date and we need a new file18:05
sdagueyep,18:05
*** che-arne has quit IRC18:06
*** reed has joined #openstack-infra18:06
sdagueI mostly want to have this in the tree so I can write the rest of the things that go against this all with a fake backend, so I'm not constantly waiting 60 seconds to get the result set back over the network18:06
*** cody-somerville has quit IRC18:08
jeblairsdague: 60 seconds?  please consider gerrit server load.  :)18:08
sdaguejeblair: well, that's why I'm trying to get a local dump :)18:09
jeblairsdague: that's great; i'm just worried about running it production too if there are queries that take 60 seconds to return18:10
jeblairsdague: not saying don't do it -- just asking you to keep it in mind, and we can evaluate or tune later as needed of course18:10
sdaguesure18:10
sdaguelet me get real timings, it might just feel like 60s18:11
sdagueit looks like gerrit is saying these are 8, 4, and 1 s queries (need all three) for last 4hrs of active patches18:12
jog0I wonder what the load on gerrit is18:13
sdaguethe 2w query is probably going to agregate to 60s, as gerrit comes back with only 500 rows at a time, and you need to go across cursors to them18:13
sdagueyeh, it's a good question. fwiw I've been doing this all morning, a lot18:13
sdaguefinally got far enough that a cache is going to work18:14
jog0what are you querying gerrit for anyway?18:14
sdagueall open, merged, or abandoned patches that have since activity in the last "foo" time period (2w in the real world, but 4h in this smaller set)18:15
sdagueto gather up all the recheck comments in the time period that er runs18:15
sdagueto cross reference them, and see that 50 bugs that people rechecked against that we don't have fingerprints for18:15
sdagueit will be cron runnable low frequency18:16
fungii'm willing to bet at least half of those are people still incorrectly rechecking against the bug their patch fixes18:16
sdaguefungi: probably18:16
sdagueI could check :)18:17
*** Protux has quit IRC18:17
fungithat would be a funny e-r "hey numbskull" check18:17
*** ^d has quit IRC18:18
jog0sdague: why not look at status.openstack.org/rechecks ?18:18
*** ^d has joined #openstack-infra18:18
openstackgerritKhai Do proposed a change to openstack-infra/config: Setup tooling and jobs for openstack Gerrit ver 2.8 and beyond  https://review.openstack.org/6034818:19
sdaguejog0: because that's extra fragile code that keeps a local pickle database, and reads the gerrit stream18:19
sdagueand if it hangs it just looses events until someone notices18:19
sdaguewhich it does, plenty18:19
sdaguethe point was to get rid of that code base18:19
clarkbright we are trying to move more towards e-r instead18:19
*** Protux has joined #openstack-infra18:20
jeblairif it's low frequency, users won't notice new bugs until the next run18:20
jog0sdague: heh it is really fragile, while your at it want to track the recheck no bugs as well?18:20
jeblairsdague: a local cache would be a great way to avoid running the 2w query often.18:20
sdaguejeblair: so the reality is18:21
sdaguethe 2w query is only 3x - 4x the 4hr query18:21
sdaguewhich is sort of due to the longevity of a patch18:22
*** senk has joined #openstack-infra18:22
sdagueso the small queries may not really help on load, but we can figure that all out later18:22
fungiso, the grenade change merged. and i see lots near completion in teh gate with successful grenade jobs18:24
clarkbwoot18:25
jeblairsdague: gerrit currently handles about one query per second; moreover, for some reason the people who write these bots start a new ssh connection for each query.  there is a sizable load from unoptimized query bots.  i'd like it if we, who actually know how this works, could do a little better.  :)18:25
sdaguejeblair: sure18:25
sdaguelet me get the functionality fleshed out first, then we can figure out the right optimization18:26
jeblairsdague: ++18:26
sdaguejeblair: also, is gerritlib correctly reusing the ssh connection?18:26
jeblairsdague: i'm attempting to help by brainstorming ideas, not prematurely reviewing.  :)18:26
*** senk has quit IRC18:26
sdaguemy intent was to punt to that as assuming it does the right thing18:27
jeblairsdague: it does not.  gerritlib needs updates from zuul.lib.gerrit to do that.18:28
jeblairsdague: (and then zuul should depend on gerritlib)18:28
sdagueok, that would be cool to do18:29
jeblairthere's some low hanging python-hacking fruit ^18:29
clarkbit does for event watching but nothing else18:29
fungiand would have a pretty sizable impact, both for random people interating with us via their own bots/automation and also reducing load on our gerrit18:29
fungier, integrating18:30
fungiwe'd trade ssh auth and setup/teardown overhead for more perpetually-open connections, but i suspect that'll still be a net win18:31
*** ^demon has joined #openstack-infra18:31
*** ^d has quit IRC18:32
*** ^demon is now known as ^d_18:32
*** ^d_ is now known as ^d18:32
jeblairfungi: yeah, most of these are effectively perpetually open anyway.18:33
dimshuh! bug 1259907 marked as incomplete18:33
uvirtbotLaunchpad bug 1259907 in openstack-ci "check-grenade-dsvm marked as FAILED - n-api/g-api Logs have errors" [Undecided,New] https://launchpad.net/bugs/125990718:33
fungidims: i hit it just a few minutes ago on a keystone patch18:34
*** praneshp has joined #openstack-infra18:35
sdaguefungi: which job?18:35
fungiah! dolphm suggests it's actually bug 126001518:35
uvirtbotLaunchpad bug 1260015 in openstack-ci "PKI token contains the string "ERROR"" [Undecided,New] https://launchpad.net/bugs/126001518:35
fungithat's so craaaaaazy18:35
*** ^d has quit IRC18:35
fungidkranz: you'll like that one18:36
*** markmc has quit IRC18:36
*** krotscheck has joined #openstack-infra18:36
praneshpCan someone please review https://review.openstack.org/#/c/60132/ ? It was approved, then automatic merge failed, and I merged changes. Now waiting for review and approval again.18:36
openstackgerritA change was merged to openstack-infra/config: Check that the target branch exists  https://review.openstack.org/6147518:36
fungisdague: on check-tempest-dsvm-full18:36
morganfainbergLOL seriously, 'ERROR' in the token's string18:37
sdaguefungi: yeh, I never saw it fail those other jobs18:37
morganfainbergthats a new one.18:37
openstackgerritA change was merged to openstack-infra/config: Remove 'reverify no bug'  https://review.openstack.org/6152218:37
jeblairsdague: doesn't e-r use stream-events already?18:38
*** simonmcc has quit IRC18:38
*** dizquierdo has quit IRC18:38
jeblair(for the real-time identification, not graphs, obviously)18:39
sdaguejeblair: yes18:39
sdaguebut it keeps no state18:39
*** nati_ueno has joined #openstack-infra18:40
jeblairsdague: how about combining some ideas here, have that do real time updates, but also have it run queries at startup to make sure you don't miss data18:40
sdagueif we want to put a database in front of gerrit, we can do that. But it's a different thing.18:40
jeblairsdague: a cache.18:40
sdagueso I think basically we just need to decide are the er tools stateless, because they can discover everything from gerrit / er / lp18:41
jeblairsdague: maybe a mem.  cache.18:41
*** blamar has quit IRC18:41
jeblaird.18:41
sdagueyeh, let's not build a caching architecture until we actually get the set of things it's doing done :)18:41
*** blamar has joined #openstack-infra18:41
sdagueespecially not if it's 0.1% of the gerrit load with all those other bots out there18:42
zarofungi: could you tell me what do i need to change to add my key for review-dev?18:42
dkranzfungi: Heh. That is obviously a bug I should fix.18:42
*** SushilKM has quit IRC18:42
jeblairsdague: we're already at caching scale.  we're already caching.  you're about to drop that and lose functionality in the process.  i fell like we've already done the 'sketch out what this would look like quickly' bit, we're at 'do it right'.18:43
*** simonmcc has joined #openstack-infra18:43
jeblairso again, i'm trying to brainstorm ideas so that we don't have to keep rewriting this.18:43
fungizaro: yeah, there's a couple files you need to change18:43
*** AaronGr is now known as AaronGr_afk18:43
openstackgerritClark Boylan proposed a change to openstack-infra/elastic-recheck: Document adding bug signatures to e-r.  https://review.openstack.org/6129818:43
fungizaro: http://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/manifests/users.pp18:44
fungizaro: put a user entry for yourself there with your ssh public key18:44
dimspki token ERROR - LOL18:44
fungizaro: http://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/manifests/review_dev.pp18:45
*** rossella_s has quit IRC18:45
sdaguejeblair: so I actually think the set of data queries we're going to want isn't yet well defined, so I'd rather actually work out that code first, then figure out the right performance afterwards.18:45
*** dcramer_ has joined #openstack-infra18:45
fungizaro: add a relize for your user in that file similar to the one in http://git.openstack.org/cgit/openstack-infra/config/tree/modules/openstack_project/manifests/groups_dev.pp#n2418:46
fungizaro: also add a review comment once you submit it, stating that you've read and agree to follow http://ci.openstack.org/sysadmin.html#ssh-access18:46
*** ^d has joined #openstack-infra18:47
*** jpich has quit IRC18:47
*** pcrews has joined #openstack-infra18:47
sdagueanyway, I'm way past lunch here, so I got to go do that. biab18:47
jeblairsdague: i think the queries are orthogonal to the architecture.  please consider designing it to at least handle the scale the current tools do.  that's all i'm asking.18:48
openstackgerritClark Boylan proposed a change to openstack-infra/config: Add packstack to gerritbot  https://review.openstack.org/6024018:48
jeblairsdague: it doesn't have to be fragile.  zuul and gerritbot, for instance, are extremely reliable.18:48
clarkbI am just goint to approve 60240, trying to flush the list of changes that have previously been determined to be mergeable. but it will conflict with entropy >_> so I will wait a minute I guess18:50
praneshpjeblair, clarkb: can you approve https://review.openstack.org/#/c/60132/18:52
praneshpthat's the change to entropy, and it was already approved once, just a merge issue18:52
clarkbpraneshp: it has been approved18:52
praneshpthat way your new approval of 60240 will be fine I think18:52
clarkbpraneshp: no I need to rebase again18:53
praneshpoh thanks clarkb18:53
fungistable branch proposals seem to be working better now... https://jenkins.openstack.org/job/propose-requirements-updates/42/console18:53
clarkbfungi: woot18:53
fungiprojects with no stable/havana are being skipped properly, and projects with are getting checked out and processed18:54
fungisuccess!18:54
*** thomasem has quit IRC18:54
fungiapevec: see if your havana requirements update changes look any better now18:54
apevecmuch better https://review.openstack.org/#/q/status:open+branch:stable/havana+topic:openstack/requirements,n,z18:55
openstackgerritKhai Do proposed a change to openstack-infra/config: give zaro access to review-dev server  https://review.openstack.org/6154218:55
fungii think no fewer than four contributors touched and iteratively fixed bugs in that proposal script over the past 24 hours18:55
zarofungi^18:55
zarothanks18:55
clarkbfungi: now we need to do the same with manage-projects18:56
fungiclarkb: and run-mirror18:56
clarkbI am not sure how popular this opinion may be, but I am half tempted to revert all of the changes that have been made to it to go back to the stateless version of the script18:56
clarkbthen we can add the statefulness back in18:56
fungii'm on the fence there. i think there are also improvements interspersed (additional debug logging for example)18:57
clarkbright, but we didn't need that additional logging until after we added all of the features >_>18:58
fungiheh18:58
jeblairclarkb: lost me -- what does the propose script have to do with manage-projects?18:58
clarkbjeblair: nothing directly, just that manage-projects is still apparently broken18:58
clarkbI was suggesting we throw bodies at the problem until it goes away18:58
jeblairclarkb: ah.  okay.  should we stop approving new projects?18:59
*** prad has quit IRC18:59
fungias we discovered last night after sarob popped in to point out that stackforge/milk was uncloneable18:59
clarkbjeblair: no, I think the failure mode is much cleaner right now18:59
jeblairclarkb: uncloneable does not sound clean.18:59
clarkbjeblair: well it means we don't need to fix zuul by hand18:59
jeblairclarkb: how does it get fixed?19:00
*** AaronGr_afk is now known as AaronGr19:00
clarkbmanage-projects? we need to sort out why gerrit project creation is failing these projects19:00
fungii've gotten a bit faster about being able to clear and reimport repositories for gerrit and check for broken mirrors on review, zuul and the git server farm19:00
openstackgerritA change was merged to openstack-infra/config: Added new project, entropy  https://review.openstack.org/6013219:00
jeblairclarkb: no, how doe 'uncloneable' get fixed?19:00
clarkbjeblair: rerun manage-projects is what fungi did19:01
fungiwell, delete several repository copies on gerrit and then rerun manage-projects19:01
fungihave to delete the gerrit, jeepyb and apache copies there19:01
jeblairkeeping in mind that stackforge projects are not our priority, i don't think we should create new ones as long as the new project automation is not working.19:01
clarkbjeblair: wfm19:02
fungican't argue with that logic19:02
clarkbfungi: there was a gerrit copy?19:02
fungiclarkb: there was, it was just empty19:02
clarkbfungi: project creation seemed to have completely failed, but it may have appeared that way to me because you removed the repo19:02
fungiclarkb: i think it got git-init'd and then nothing pushed into it19:02
clarkbfungi: no refs/meta/config?19:02
clarkbthe first commit in refs/meta/config should always happen automagically by gerrit19:03
fungiit did have refs/meta/config but no heads19:03
clarkbgotcha, so project creation did work to that extent19:03
clarkbfungi: did the local jeepyb cache repo have any content in it?19:04
*** mrodden has quit IRC19:04
fungiclarkb: honestly i didn't look. i will copy off all three of the repos on gerrit next time i witness it19:04
jeblairreopened bug 124256919:05
uvirtbotLaunchpad bug 1242569 in openstack-ci "manage-projects error on new project creation" [Critical,Triaged] https://launchpad.net/bugs/124256919:05
*** nati_uen_ has joined #openstack-infra19:05
jeblairmordred: ^ you may be interested in this; manage-projects is still broken19:05
*** klrmn has left #openstack-infra19:05
*** prad has joined #openstack-infra19:06
jeblairAaronGr: if you're looking for a project, that's a good one ^.  just getting things set up to be able to test that will get you familiar with a lot of stuff.19:06
clarkb++19:07
fungii'll see if entropy encounters any issues, since it should be getting imported right about now19:07
jeblairAaronGr: (you would need to set up a gerrit)19:07
clarkbfungi: if it does, can you move the various repos aside so that we can refer back to them while debugging?19:07
fungioh, nevermind. entropy doesn't have an upstream, so it probably won't break19:07
clarkbfungi: will be interesting to see if ACLs apply though19:08
*** nati_ueno has quit IRC19:08
clarkbfungi: if they do I think we can rule out problems iwth group management19:08
fungiwe *can* test with 61250 (openstack-infra/openstackid), but i want to rebase it not on top of the project.yaml realphabetize change (and abandon that one until we have a test for it)19:09
fungii'll do that now19:09
*** rcleere_ has joined #openstack-infra19:09
*** rcleere has quit IRC19:10
*** rcleere_ is now known as rcleere19:10
zarogerrit user summit: https://sites.google.com/site/gerritsummit201419:12
*** rongze has quit IRC19:13
*** danger_fo_away is now known as dangers19:13
*** mrodden has joined #openstack-infra19:13
*** reed has quit IRC19:14
openstackgerritClark Boylan proposed a change to openstack-infra/config: Add packstack to gerritbot  https://review.openstack.org/6024019:15
clarkbbefore any more conflicts happen I am approving that :)19:15
fungiwfm19:15
openstackgerritJeremy Stanley proposed a change to openstack-infra/config: Import the openstackid authentication project  https://review.openstack.org/6125019:15
*** rongze has joined #openstack-infra19:15
clarkbI think that covers things that hit merge conflicts, back to normal review19:16
*** jorisroovers has joined #openstack-infra19:17
*** zhiyan has left #openstack-infra19:18
clarkbjeblair: fungi: out of curiousity are requirements and hacking in your gerrit project watch list? I am debating removing them from my watchlist19:19
*** zhiyan has joined #openstack-infra19:19
openstackgerritA change was merged to openstack-infra/config: Add packstack to gerritbot  https://review.openstack.org/6024019:20
fungiclarkb: i don't think either requirements or hacking are in my watch list since there seemed to already be plenty of people reviewing them19:20
*** crank_ has joined #openstack-infra19:20
*** dcramer_ has quit IRC19:21
clarkbfungi: they also have a lot of noise >_>19:21
fungiyes. noise i do not need19:21
*** crank_ has quit IRC19:21
*** rongze has quit IRC19:22
*** resker has quit IRC19:23
*** esker has joined #openstack-infra19:23
openstackgerritFelipe Reyes proposed a change to openstack-infra/jenkins-job-builder: Adds Mercurial SCM support  https://review.openstack.org/6154719:28
*** CaptTofu has quit IRC19:29
*** CaptTofu has joined #openstack-infra19:30
*** nati_uen_ has quit IRC19:30
*** rcarrillocruz has joined #openstack-infra19:31
openstackgerritFelipe Reyes proposed a change to openstack-infra/jenkins-job-builder: Fix format in installation.rst  https://review.openstack.org/6154819:31
clarkbI went ahead and removed them from my watchlist, we'll see if this helps19:31
*** yolanda has joined #openstack-infra19:31
*** rcarrillocruz1 has quit IRC19:32
*** dcramer_ has joined #openstack-infra19:32
*** openstackgerrit has quit IRC19:34
*** CaptTofu has quit IRC19:34
*** openstackgerrit has joined #openstack-infra19:34
*** rnirmal has quit IRC19:36
*** nati_ueno has joined #openstack-infra19:40
*** prad has quit IRC19:40
*** herndon has joined #openstack-infra19:41
openstackgerritJames E. Blair proposed a change to openstack-infra/devstack-gate: Don't fix disks before rexecing  https://review.openstack.org/6096119:41
*** prad has joined #openstack-infra19:43
*** reed has joined #openstack-infra19:46
*** pblaho has joined #openstack-infra19:47
*** pblaho has quit IRC19:48
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Serve the statusbot alert file from eavesdrop  https://review.openstack.org/6058219:50
jeblairfungi, clarkb: i'm starting to think we should make status.o.o its own host so it can run all those things we want to run (irc bots, cron jobs, etc) without having to worry about artifact hosting.19:51
clarkbjeblair: ++19:51
openstackgerritA change was merged to openstack-infra/statusbot: Add an alert file publisher  https://review.openstack.org/6056819:52
fungijeblair: that makes sense19:53
*** _david_ has joined #openstack-infra19:53
*** thomasem has joined #openstack-infra19:58
*** AaronGr is now known as AaronGr_afk19:58
*** sdake_ has quit IRC19:58
*** sdake_ has joined #openstack-infra19:59
*** dcramer__ has joined #openstack-infra19:59
apevecfungi, ttx - here's draft relnotes for 2013.2.1 https://wiki.openstack.org/wiki/ReleaseNotes/2013.2.1 - please check I didn't miss any CVEs20:02
*** SergeyLukjanov has quit IRC20:02
*** openstackstatus has quit IRC20:02
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Add status.openstack.org vm  https://review.openstack.org/6155220:02
*** openstackstatus_ has joined #openstack-infra20:02
*** openstackstatus_ is now known as openstackstatus20:02
apevecwe should probably have script generate it :)20:02
apevecfungi, do you keep CVE metadata in some machine readable format?20:02
*** openstackstatus has quit IRC20:03
*** openstackstatus_ has joined #openstack-infra20:03
*** openstackstatus_ is now known as openstackstatus20:03
*** dcramer_ has quit IRC20:03
*** openstackstatus has quit IRC20:04
*** openstackstatus_ has joined #openstack-infra20:04
*** openstackstatus_ is now known as openstackstatus20:04
*** rcarrillocruz has quit IRC20:05
*** balar has quit IRC20:05
*** openstackstatus has quit IRC20:05
*** openstackstatus_ has joined #openstack-infra20:05
*** openstackstatus_ is now known as openstackstatus20:05
*** openstackstatus has quit IRC20:06
*** openstackstatus_ has joined #openstack-infra20:06
*** openstackstatus_ is now known as openstackstatus20:06
*** herndon has quit IRC20:07
*** openstackstatus_ has joined #openstack-infra20:07
openstackgerritJames E. Blair proposed a change to openstack-infra/devstack-gate: Don't fix disks before rexecing  https://review.openstack.org/6096120:08
*** openstackstatus has quit IRC20:08
*** openstackstatus_ is now known as openstackstatus20:08
*** openstackstatus has quit IRC20:08
*** apevec has quit IRC20:08
*** openstackstatus has joined #openstack-infra20:08
sdaguefungi: finally found proof that the grenade change helped - http://logs.openstack.org/65/46065/24/gate/gate-grenade-dsvm/a1b5b14/console.html#_2013-12-11_16_52_05_19820:09
sdaguethat would have failed previously20:09
sdaguepuppet's network also got better about the same time we merged that, so I wanted to find an instance of that working20:09
*** dcramer___ has joined #openstack-infra20:09
mtreinishjeblair: were we hitting an issue which prompted?: https://review.openstack.org/#/c/61513/20:10
jeblairmtreinish: sphinx pre-release versions broke local use of tox (not a gate issue)20:11
*** nicedice has joined #openstack-infra20:11
jeblairmtreinish: that change, however, should have been propogated months ago, but was dropped.  about 1/3 of the projects already had it.20:11
*** jroovers has joined #openstack-infra20:12
*** jorisroovers has quit IRC20:12
mtreinishjeblair: yeah, I think I forgot to add it when I updated the tox.ini min-version20:12
*** _david_ has quit IRC20:12
*** thedodd has joined #openstack-infra20:13
*** freyes has joined #openstack-infra20:13
*** dcramer__ has quit IRC20:13
*** jooools has joined #openstack-infra20:15
jeblair#status ok20:16
*** ChanServ changes topic to "Discussion of OpenStack Project Infrastructure | Docs http://ci.openstack.org/ | Bugs https://launchpad.net/openstack-ci | Code https://git.openstack.org/cgit/openstack-infra/"20:18
*** dcramer__ has joined #openstack-infra20:20
*** vipul is now known as vipul-away20:21
*** vipul-away is now known as vipul20:21
*** dcramer___ has quit IRC20:23
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Switch devstack checkout to use git.o.o  https://review.openstack.org/6155620:28
*** vkozhukalov has quit IRC20:29
*** dcramer___ has joined #openstack-infra20:29
*** mrodden has quit IRC20:30
*** gothicmindfood has quit IRC20:31
*** mrodden has joined #openstack-infra20:32
*** dcramer__ has quit IRC20:33
*** dcramer__ has joined #openstack-infra20:33
dhellmannfungi: I'm still having some trouble with that stevedore repo you fixed a day or two ago, do you have a sec to help?20:35
pleia2following up on a couple bug day things, do we want to give shrini the green light to set up an sss demo, or..? https://bugs.launchpad.net/openstack-ci/+bug/120313720:35
uvirtbotLaunchpad bug 1203137 in openstack-ci "Run log analyzer for all IRC logs" [Low,Triaged]20:35
fungidhellmann: sure--what's the symptom?20:35
dhellmannfungi: clone a fresh repo, create a branch, create a commit, git review, merge failure reported by jenkins: https://review.openstack.org/#/c/61559/20:36
dhellmannfungi: the review contains a brand new file (.gitreview)20:36
*** vipul is now known as vipul-away20:37
pleia2jeblair: any thoughts on this one? https://bugs.launchpad.net/openstack-ci/+bug/1221842 argument was made that "mailman isn't secure anyway" but is adding an ssl cert for it really more much trouble/expense than it's worth?20:37
*** dcramer___ has quit IRC20:37
uvirtbotLaunchpad bug 1221842 in openstack-ci "Add ssl cert to lists.openstack.org" [Medium,Triaged]20:37
fungidhellmann: i'll check zuul's clone... probably something's wrong with it from when we were working through fixing these before20:37
dhellmannfungi: that's what I figured, too20:37
fungidhellmann: in good news, more recent project additions haven't been hitting that specific problem20:38
fungiso probably just pending cleanup i missed there20:38
*** zhiyan has quit IRC20:38
*** dprince has quit IRC20:38
dhellmannfungi: good, I have several more to submit once I have a new stevedore release done :-)20:38
openstackgerritPaul Belanger proposed a change to openstack-infra/jeepyb: Add new hook flags for gerrit 2.5  https://review.openstack.org/6156020:38
*** dcramer__ has quit IRC20:39
*** _david_ has joined #openstack-infra20:39
pabelangerSo, taking suggestions how to address the new flags for gerrit 2.5 hooks20:39
jeblairpleia2: i will reply to 120313720:40
pleia2jeblair: thank you20:40
*** sandywalsh_ has quit IRC20:42
jeblairpleia2: as long as we realize that mailman sends out passwords in plain text.  :)  i'm okay adding it though.20:43
jeblairpleia2: assigned to me20:43
*** oubiwan__ has joined #openstack-infra20:43
*** yolanda has quit IRC20:44
reedfungi, re: https://review.openstack.org/#/c/61250/ is the code going to stay on github or can we move it to our git repo?20:45
fungireed: in this case, "upstream" really means "import-from"20:45
reedfungi, so once that erb is executed we will have it on git.openstack.org?20:45
*** lcestari has quit IRC20:46
fungireed: so approving that change is going to effectively move the repository to start being hosted from gerrit as the source of truth, and it will be mirrored to the openstack-infra orgs on git.o.o and github, yes20:46
reedsweet20:46
pleia2jeblair: thanks, I know it's terribly insecure in general20:46
reedfungi, will we need to write jenkins jobs? in other words, now there are not gate checks, right?20:46
*** krotscheck has quit IRC20:47
fungireed: right now there are no jenkins jobs for it (excepting a no-op which just basically returns true on any change). we can add as many as we want though20:47
reedsweet20:47
*** krotscheck has joined #openstack-infra20:49
fungipleia2: yes, even though https prevents someone from sniffing your list password when you log in to moderate posts or update your settings, it in no way helps the attacker who is trying to sniff your traffic from also clicking the "send my password" button and then snagging it out of the ensuing e-mail message20:49
*** AaronGr_afk is now known as AaronGr20:49
fungier, in no way helps thwart20:49
pleia2fungi: right, but I'd argue that the passive sniffing over login is a much more common attack vector, with entry-level tools you can use on windows in starbucks20:50
pleia2other vectors take a targeted attack20:50
fungithough i suppose opportunistic smtp-over-ssl/tls does raise the bar for some message, requiring the attacker to actually mitm the connection (still not too hard since smtps almost never performs cert validation)20:51
*** praneshp has quit IRC20:51
pleia2yeah20:51
fungialso, how did you know i sniff passwords at starbucks? coffee-scented passwords smell great20:52
pleia2everybody's doing it ;)20:52
fungidhellmann: okay, looks like it's fixed now. i got a test to run to completion for it (the change should report here soon-ish once there are available slaves to run the remaining jobs)20:54
*** sandywalsh_ has joined #openstack-infra20:54
dhellmannfungi: thanks!20:54
*** hashar has joined #openstack-infra20:57
*** paul-- has joined #openstack-infra20:59
*** ^demon has joined #openstack-infra21:01
*** ^demon has joined #openstack-infra21:01
*** denis_makogon_ has joined #openstack-infra21:02
*** ^demon has quit IRC21:02
*** hashar has quit IRC21:03
*** ^demon has joined #openstack-infra21:04
*** ^d has quit IRC21:05
*** yassine has quit IRC21:08
SpamapShm.. given http://paste.ubuntu.com/6558026/ and http://paste.ubuntu.com/6558028/ ... why is my pypi-mirror job downloading and installing httpretty over and over?21:09
SpamapSoh n/m21:10
SpamapSUsing download cache from /var/cache/pypi-mirror/pypi/download/pip/openstack/https%3A%2F%2Fpypi.python.org%2Fpackages%2Fsource%2Fh%2Fhttpretty%2Fhttpretty-0.7.0.tar.gz21:10
*** denis_makogon_ is now known as denis_makogon21:11
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Don't re-exec in check-dg-tempest-dsvm-full  https://review.openstack.org/6156921:15
openstackgerritJames E. Blair proposed a change to openstack-infra/devstack-gate: Don't fix disks before rexecing  https://review.openstack.org/6096121:15
jeblairthat change is now ready for review ^21:15
clarkbjeblair: https://review.openstack.org/#/c/55829/9 can you expand on what you mean by your last comment? or possible review the latest patchset and indicate if it looks good21:17
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Add status.openstack.org vm  https://review.openstack.org/6155221:17
*** dstanek has quit IRC21:17
jeblairclarkb: yes; if you read my ealier comments you'll see what i was on about (i just explained more in irc); i'll review now though.21:18
*** dstanek has joined #openstack-infra21:18
jeblairlgtm21:19
jeblair#alert test21:20
jeblair#status alert test21:20
openstackstatusNOTICE: test21:20
*** ChanServ changes topic to "test"21:20
fungi...if this had been an actual emergency...21:20
*** rfolco has quit IRC21:21
jeblair#status ok21:21
*** ChanServ changes topic to "Discussion of OpenStack Project Infrastructure | Docs http://ci.openstack.org/ | Bugs https://launchpad.net/openstack-ci | Code https://git.openstack.org/cgit/openstack-infra/"21:21
openstackgerritSean Dague proposed a change to openstack-infra/elastic-recheck: wip: work in progress on bulk gerrit query  https://review.openstack.org/6157321:24
clarkbjeblair: line 548 https://review.openstack.org/#/c/60961/8/devstack-vm-gate-wrap.sh could that be run out of the workspace instead?21:25
*** vipul-away is now known as vipul21:25
*** thomasem has quit IRC21:25
openstackgerritA change was merged to openstack-infra/config: Serve the statusbot alert file from eavesdrop  https://review.openstack.org/6058221:27
*** dkliban has quit IRC21:27
*** alcabrera has quit IRC21:28
jeblairclarkb: possibly, but i find it's easier to reason about just treating it the same as the rest of the repos at that point in the script.21:29
*** hashar has joined #openstack-infra21:29
clarkbjeblair: ok21:29
*** paul-- has quit IRC21:29
jeblairclarkb: (it should be the same because it should update the workspace copy iff this or a change ahead changes it, and otherwise, tip-of-master should be fine) <-- but that's the sort of thing you don't have to think too much about if we don't do that.  :)21:30
*** thomasem has joined #openstack-infra21:30
jeblairclarkb: oh, also, i think that makes it easier to use in full-on manual dev mode.21:31
*** thomasem has quit IRC21:31
clarkbjeblair: should be the same meaning run out of workspace or run out of /opt?21:32
*** dstanek has quit IRC21:32
mgagnezaro: in its current state (git tag based versionning), how are maven project versions generated when a snapshot is built? (if any) What's the format used?21:32
jeblairclarkb: yes21:32
*** openstackstatus has quit IRC21:32
clarkbheh21:33
*** openstackstatus has joined #openstack-infra21:33
jeblair#status alert test21:34
openstackstatusNOTICE: test21:34
*** ChanServ changes topic to "test"21:34
*** jcooley_ has quit IRC21:34
clarkbmgagne: PROJECT_VER="$SCM_TAG.$COMMITS_SINCE_TAG.$SCM_SHA"; it doesn't do snapshots, it does actual increasing version numbers21:34
jeblair#status ok21:34
*** ChanServ changes topic to "Discussion of OpenStack Project Infrastructure | Docs http://ci.openstack.org/ | Bugs https://launchpad.net/openstack-ci | Code https://git.openstack.org/cgit/openstack-infra/"21:34
mgagneclarkb: "snapshots" are therefore considered sub-releases of a major/minor release previously done.21:35
jeblair#status alert test21:35
openstackstatusNOTICE: test21:35
*** ChanServ changes topic to "test"21:35
clarkbmgagne: right, it does what our python clients do for example21:35
jeblair#status ok21:35
*** ChanServ changes topic to "Discussion of OpenStack Project Infrastructure | Docs http://ci.openstack.org/ | Bugs https://launchpad.net/openstack-ci | Code https://git.openstack.org/cgit/openstack-infra/"21:35
*** ^demon has quit IRC21:35
*** smarcet has quit IRC21:36
hddso this change was approved, but failed at the gate: https://review.openstack.org/#/c/60980/21:36
mgagneclarkb: I had an idea to address the concern someone (I forgot the name) raised yesterday and I want to fully grasp the current concept first.21:36
clarkbmgagne: it was sharwell21:36
mgagneclarkb: thanks21:36
hddand changes for python-glanceclient are all failing to verify because of it21:36
hddfungi, clarkb: any ideas?21:37
openstackgerritJames E. Blair proposed a change to openstack-infra/statusbot: Add missing import directives  https://review.openstack.org/6157521:37
jeblairclarkb, fungi: ^ i'm going to self-approve that; it's, ah, tested in production.21:38
clarkbhdd: looks like review.openstack.org fell over then those tests tried to clone from it21:38
clarkbjeblair: :) go for it21:38
fungilgtm21:38
openstackgerritA change was merged to openstack-infra/statusbot: Add missing import directives  https://review.openstack.org/6157521:38
mgagneclarkb: how are those "snapshots" used? Anything having dependencies against it? Are they published to any Maven repo?21:38
clarkbmgagne: nothing should have dependencies on it and they shouldn't be published to Maven repos (at least we don't do that for other projects that use the process today)21:39
*** jcooley_ has joined #openstack-infra21:39
mgagneclarkb: what's the point of building snapshots if nothing uses it? Are they simply published to a scp site and manually consumed by anyone wishing to test it?21:40
clarkbmgagne: yup21:41
clarkbhdd: 0609 was 15 and a half hours ago? I wonder fi there was a network burp21:41
mgagneclarkb: and I guess they are published to a repo only when built by pre-release/release pipelines.21:41
clarkbmgagne: right21:41
mgagneclarkb: alright. thanks!21:41
openstackgerritSteve Baker proposed a change to openstack-infra/devstack-gate: Register Fedora 20 for DEVSTACK_GATE_TEMPEST_HEAT_SLOW  https://review.openstack.org/6157621:41
*** fbo is now known as fbo_away21:43
sharwellmgagne: snapshots are used in 2 situations: 1) snapshots can be built on a local development machine and then referenced by another project to test the behavior of the dependent project with the new build, and 2) a snapshot can be deployed to a special sonatype repository to allow early testing of a build by other individuals (similar to #1, but publicly accessible)21:43
clarkbjeblair: so I understand. You are saying running it out of $BASE makes sense so that we don't have to worry about complicated d-g updates? imo doing it out of $WORKSPACE avoids that problem because we know $WORKSPACE is up to date21:43
hddclarkb, how can I get that change reverified? No more "reverify no bug" (-:21:43
mgagnesharwell: yes, I correctly guessed how they were used by your team. We have the same (or very similar) workflow. thanks.21:44
clarkbhdd: submit a bug against openstack-ci about tests failing to fetch/clone git stuff due to possible network problems21:44
mgagnesharwell: I want to understand how each team uses the artifact/versioning to I can adjust my proposition/idea to fit the needs of both.21:44
mgagnesO*21:44
clarkbhdd: reverify against that. This is a bug, it just happens to probably be one very trick to correct21:44
hddgot it; thanks21:45
*** ArxCruz has quit IRC21:46
*** jhesketh has joined #openstack-infra21:46
*** jooools has quit IRC21:46
jeblairclarkb: if you want to do that then i think we should remove d-g from PROJECTS and move the re-exec setup_project call out one level.  then i'd feel better about knowing it's always updated.21:48
jeblairclarkb: ugh21:48
jeblairclarkb: more later...21:48
clarkbI don't feel super strongly about it, just pointing out how I think the pieces fit together in my head21:49
fungiso... does anyone remember if we reverted anything https://review.openstack.org/56660 depends on?21:50
clarkbI believe the setup_projects call that happens before we call into $BASE will update the project in $BASE for us, but that happens as secondary step21:50
clarkbfungi: pretty sure we did21:50
clarkbfungi: we reverted the change that told select-mirror where to find wheels21:51
devanandaclarkb: you guys manage global-requirements, ya?21:51
clarkbbecause wheels were not acting case insensitive.21:51
clarkbdevananda: no the requirements core group manages them21:51
devanandaah21:51
devanandaclarkb: i see. ci team is included, thus my presumption21:52
mgagneclarkb: if pbr handles the versioning using git tags, how is there a version in setup.cfg? What's the purpose? https://github.com/openstack/nova/blob/master/setup.cfg#L3 Is it the next major/minor version the project is working/looking toward to release?21:53
clarkbmgagne: ya, pbr supports two different types of versioning. Pre versioning where you are working up to a version and post versioning where you are tacking on point releases to an old version. If you specify the version in setup.cfg that tells pbr that you are using pre versioning and are working up to that version21:54
mgagneclarkb: Maven (project.version in pom.xml) is post-versioning right?21:55
clarkbmgagne: yes21:55
mgagnejust checking21:55
clarkbnp21:55
*** freyes has quit IRC21:57
mgagneclarkb: ... unless -SNAPSHOT is used21:57
*** ^d has joined #openstack-infra21:57
clarkb?21:57
clarkbor would that be the distinction on pre vs post for maven?21:58
mgagneclarkb: if 1.0-SNAPSHOT is used (instead of 1.0) in project.version, this would mean the project is working toward a release of 1.021:58
*** dstanek has joined #openstack-infra21:58
mgagneclarkb: and I guess, even with git tag based releases, pbr has the same "limitation": Someone has to manually bump that version to indicate a new major version is about to be released someday.21:59
clarkbmgagne: right (careful pretty quick here I will be complaining about the date based versioning :) )22:00
fungipreversioning also has a fairly major logistical drawback. you may decide at the last minute that the version number you thoughth you wanted isn't the one you actually wanted, so those pre-versions become sort of a lie22:00
mgagnefungi: true22:01
lifelesss/sort of//22:01
clarkbpreversioning is something ttx and I disagree on for many reasons aiui22:01
fungisnapshot of "the version which never was"22:01
*** praneshp has joined #openstack-infra22:01
lifelessthe problem is that version numbers as most folk know them don't have the concept of 'intended version'22:02
fungiwell, i actually think our use of date-based versioning and preversioning for time-based releases isn't entirely outlandish. if your release model is openbsd-style "we release what's ready on time no matter what" then it seems acceptable22:02
lifelessmore sophisticated grammars do, but they aren't widely adopted and people don't recognise them given an arbitrary string.22:02
openstackgerritRussell Bryant proposed a change to openstack-infra/config: Run solum functional tests  https://review.openstack.org/6158222:02
*** ^d has quit IRC22:02
clarkbfungi: it is outlandish because it doesn't provide me with any non redudnant info22:03
mgagneif you ever backtrack on your intented version, any published artifacts will forever be more recent than any new builds of the new intended version as it will always be lower than the old one.22:03
*** dstanek has quit IRC22:03
clarkbthe version control system knows when a version was cut, it shouldn't be part of the version22:03
clarkbinstead versions should carry semantic info that conveys to users useful data22:04
*** dkliban has joined #openstack-infra22:04
mgagneclarkb: my intention wasn't to open a pandora'S box but I fear I did.22:04
fungiwell, yes, in our case the date-based version numbers are non-semantic and arbitrary, and just happen to include a year for the major part22:05
clarkbmgagne: sorry, I get where you were taking this, I just can't help but bring this up when people want to do the other thing :)22:05
mgagneclarkb: np =)22:05
fungiclarkb: so... digging in the d-g git log, i don't think we reverted the select-mirror patch there after all? wasn't that the one which got proposed but check jobs showed it didn't help?22:06
*** ^d has joined #openstack-infra22:06
mgagneclarkb: I hope you guessed where I'm going with my questions22:06
*** jroovers has quit IRC22:06
clarkbmgagne: yes, I think you are going to suggest we support both pre and post versioning schemes based on a stated version somewhere and the contents of the git repo. I think we can do that, but for reasons above think we shouldn't22:07
clarkbbut I may lose that argument for the same reason I lose when talking nova versioining :)22:07
clarkbfungi: we reverted a change to select-mirror itself22:07
fungiohhhhh22:07
fungii'll find it22:07
clarkbfungi: 343cff816b9ffd6d25d76481ba2a6a0eb7495352 in config22:08
fungiwant to get these reproposed if needed and back on track. we didn't leave enough breadcrumbs in the outstanding commits22:08
*** esker has quit IRC22:08
fungiright, we killed Add support for per-distro wheel mirrors22:09
clarkbfungi: careful about straight up reproposing that change, I think $distro wasn't set in one place it was used and the sed on $distro is wrong compared to what we have in the mirror22:09
clarkb++ to reproposing but for that particular one I think we need to fix a couple things22:09
fungioh, i completely expect anything which needs reproposing to probably also need fixing.22:09
pmathewsjeblair: ping?22:09
fungijust trying to make sure things like 56660 don't get approved and then somehow break everything22:10
anteayaclarkb: a patch hit two different bugs, can I use `recheck bug 1258848 and bug 1257641` ?22:10
uvirtbotLaunchpad bug 1258848 in nova "vif doesn't exist Error message in tempest runs" [Critical,Triaged] https://launchpad.net/bugs/125884822:10
uvirtbotLaunchpad bug 1257641 in nova "Quota exceeded for instances: Requested 1, but already used 10 of 10 instances" [Undecided,Confirmed] https://launchpad.net/bugs/125764122:10
clarkbanteaya: no, just pick one22:10
anteayaokay thanks22:10
*** dkranz has quit IRC22:11
mgagneclarkb: unless I misunderstand something, the version in setup.cfg is the equivalent of having 2014.1-SNAPSHOT in pom.xml22:11
jeblairpmathews: pong22:11
jeblairanteaya: sometimes i leave both in two comments22:11
jeblairanteaya: that way recheckwatch seets both.  but recheckwatch may not live much longer so it probably doesn't matter.22:11
clarkbmgagne: almost, instead you remove -SNAPSHOT and the machinery sorts out what the actual version is22:12
pmathewsjeblair: Can I get you to take a look at https://review.openstack.org/#/c/59875/322:12
jeblairpmathews: not my area, sorry.22:12
anteayajeblair: okay, I just made a note of the other bug in a follow-up comment, not sure if it is the correct syntax for recheckwatch, I doubt it: https://review.openstack.org/#/c/61234/22:13
fungipmathews: you probably will fare better looking for devstack developers on #openstack-qa22:13
*** elasticio has quit IRC22:15
*** oubiwa___ has joined #openstack-infra22:17
*** oubiwa___ is now known as oubiwann-lambda22:18
*** esker has joined #openstack-infra22:18
*** esker has quit IRC22:19
*** oubiwan__ has quit IRC22:20
openstackgerritA change was merged to openstack-infra/config: Switch some infra jobs to use bare precise nodes  https://review.openstack.org/6034422:21
jeblairooh22:21
clarkbdun dun dun22:21
mgagneclarkb: alright. time based release makes this process easier I guess... not so much for libraries which can be released or bump the minor/major version at any time :-/22:21
mgagneclarkb: my plan is falling apart :O22:22
clarkb:(22:22
*** resker has joined #openstack-infra22:22
mgagneclarkb: I could still propose it and see if someone can come up with a solution22:23
fungiokay, i'm going to disappear to grab some dinner, then back for more fun22:24
*** oubiwann-lambda has quit IRC22:24
clarkbmgagne: I am leaning towards just forgoeing automagic releases if the old version scheming is hat important22:25
*** dims has quit IRC22:26
clarkbdo releases by hand since the rest of it needs hand holding22:26
*** hashar has left #openstack-infra22:26
jeblairreleases by hand is not okay.22:26
jeblairi don't care about versioning, but publishing a release artifact has to be automatic.  it can't depend on someone uploading something somewhere manually.22:26
mgagnejeblair, clarkb: the idea was to implement the same magic of pbr in Maven22:27
clarkbfungi: oh crud, I just approved a projects.yaml change. Should I wait on that to do your alphebetizing?22:27
openstackgerritA change was merged to openstack-infra/config: Set launchpad project mapping for all -api repos  https://review.openstack.org/6059722:27
clarkbfungi: I think I will forge ahead and get those through then rebase your change if necessary22:28
*** resker has quit IRC22:28
*** herndon has joined #openstack-infra22:28
*** dstanek has joined #openstack-infra22:30
openstackgerritA change was merged to openstack-infra/config: Set launchpad mappings for rest openstack/* repos  https://review.openstack.org/6059822:30
openstackgerritA change was merged to openstack-infra/config: Set launchpad mappings for all cookbook-* repos  https://review.openstack.org/6059922:30
mgagneclarkb: BUT hey, they would have bumped that version manually anyway.22:30
mgagneclarkb: my plan still stand22:31
*** michchap has joined #openstack-infra22:31
clarkbmgagne: right I think we could have something that emulated pre and post versioning for maven projects22:31
clarkbthat might be one way of tackling the problem if we are very attached to pre versioning22:31
mgagneclarkb: I'm writing a FAQ or some kind of user stories if you want that explains how this system would work.22:32
openstackgerritA change was merged to openstack-infra/config: Set launchpad mappings for the rest projects  https://review.openstack.org/6060022:32
jeblair0o644 is the new right way to do octal in python, right?22:33
mgagneclarkb: I however don't know anything about the inner working of Maven. I know Maven has plugin but don't know the extend of the possibilities and informations they can intercept/modify.22:33
clarkbjeblair: yes22:34
openstackgerritJames E. Blair proposed a change to openstack-infra/statusbot: Set world-readable permissions on alert file  https://review.openstack.org/6158822:34
clarkbmgagne: ya I am pretty light on maven internal knowledge as well. zaro seems to grok good portions of it22:34
mgagneclarkb: zaro is aware of the idea but he looks busy/away atm =)22:35
*** mriedem has quit IRC22:37
*** ryanpetrello has quit IRC22:39
*** dims has joined #openstack-infra22:39
mgagneclarkb: what happens if after a release has been tagged, someone forgets to bump the version? Which version is generated? Is it still against the same version or is the last digit increased?22:40
zaroclarkb: mgagne , so been away for lunch.  need to catch up on scrollback22:40
zaromgagne: version is auto bumped22:40
mgagnezaro: idea is pbr in maven. asking questions about pbr and current maven/pbr versioning system in openstack.22:41
anteayaI'm obviously doing something wrong, I did recheck bug <bug number> on https://review.openstack.org/#/c/61234/ and I don't see it in the check queue and zuul had 0 events22:41
zaromgagne: ohh wait tag is manually set by person making tag.22:41
mgagnezaro: yes22:42
anteaya10 events now, but it did have 0 when I last looked for 61234 in the queue22:42
*** dangers is now known as danger_fo_away22:42
mgagnezaro: you create that tag. A release is done. version in setup.cfg is not bumped. Someone merge a change. Which version is it?22:42
zaromgagne: takling about this? https://github.com/ktoso/maven-git-commit-id-plugin22:42
mgagnezaro: no, pbr22:43
clarkbmgagne: still the old version22:43
clarkbmgagne: it would look like the next snapshot against the previous version22:43
mgagneclarkb: so you could still build snapshots of an already released version.22:43
clarkbI think22:43
mgagneclarkb: alright22:43
anteayamy bad, I just found it22:47
anteayad'oh22:47
*** adrian_otto has joined #openstack-infra22:48
*** mfer has quit IRC22:48
mgagnezaro, clarkb: therefore, the only thing that needs to be fixed is: find a way to override $project.version with tag when releasing and generating a proper snapshot version based on commit since last tag. Nothing else needs to be done to address the workflow of the dev which remains unchanged.22:52
mgagnezaro, clarkb: this can already be done with mvn versions:set22:53
*** CaptTofu has joined #openstack-infra22:53
openstackgerritJames E. Blair proposed a change to openstack-infra/config: Fix serving alert json file on eavesdrop  https://review.openstack.org/6159322:53
zaromgagne: i'm wondering if it can always be set to -SNAPSHOT?22:54
mgagnezaro: it should always be set to -SNAPSHOT22:54
mgagnezaro: X.Y.Z-SNAPSHOT where X.Y.Z is the next intended version.22:54
*** paul-- has joined #openstack-infra22:55
*** dizquierdo has joined #openstack-infra22:56
zaromgagne: yeah, i would agree.22:56
zaromgagne: it's set by default right?  so just mvn package22:57
zaromgagne: so are we back to maven plugin idea?22:58
*** krotscheck has quit IRC22:58
mgagnezaro: no plugin, just mvn versions:set22:58
zaromgagne: is that a phase?23:00
mgagnezaro: it's a target23:00
mgagnezaro: afaik23:00
mgagnezaro: http://mojo.codehaus.org/versions-maven-plugin/set-mojo.html23:00
*** paul-- has quit IRC23:01
clarkbjeblair: zuul status page idea, when a job completes if you hover over the SUCCESS or FAILURE result work have it display the total time it took for the job to run23:04
jeblairclarkb: ++23:04
*** paul-- has joined #openstack-infra23:04
clarkbbtw I have approved a few simple changes with only one +2 (doc updates and gerritbot project watches)23:06
zaromgagne: ahh, i see. maven set is doing the exact same thing as we do now.  except we don't need to have a variable for the project version.  NICE!23:06
mgagnezaro: yep23:06
zaroclarkb: jeblair .  i think mgagne is on to something23:07
openstackgerritA change was merged to openstack-infra/nodepool: Fix README file  https://review.openstack.org/6057923:07
mgagnezaro: updated: https://etherpad.openstack.org/p/java-release-process23:07
openstackgerritA change was merged to openstack-infra/nodepool: Improve README.rst formatting  https://review.openstack.org/6095523:07
zaroclarkb: jeblair, mgagne : that's a simple fix that may make everyone happyy.23:07
clarkbcool23:08
clarkbtrying to flush the queue of as many simple things as possible23:08
zaromgagne: does that fix it for you and your peeps?23:08
mgagnezaro: ironically, we already have this system here, except the version isn't coming from a git tag but a script incrementing the last digit found in $project.version. That version is then bumped by this same script and committed in the repo so the release manager doesn't have to do it. This process is trigged by someone launching a jenkins job.23:10
zarosharwell: your thoughts on mgagne proposal?23:11
mgagnezaro: well, it's a jenkins job (which can be parameterized), no a git tag. that's the point.23:11
zaromgagne: i assume you still deploy with release plugin?23:13
mgagnezaro: I think so. I usually stay away from this system as they are used by projects I do not manage.23:13
mgagnezaro: the missing puzzle piece in the previous system was Versions Maven Plugin.23:14
clarkbjeblair: fungi: curious about what you think of https://review.openstack.org/#/c/61204/23:16
sharwellmgagne: (sorry i'm a little behind, reading your messages now) if you remove -SNAPSHOT for the release commit, and then forget to make a new commit bumping the version and proceed with other work, you will have more than one commit in source control which produces what looks like a final release output. the commit immediately after removing -SNAPSHOT should be a new commit which bumps up the version number and adds -SNAPSHOT23:16
mgagnesharwell: please read the proposition, you never ever have a version without -SNAPSHOT23:16
*** flaper87 is now known as flaper87|afk23:17
openstackgerritA change was merged to openstack-infra/jenkins-job-builder: Fix GitHub pull request builder plugin support  https://review.openstack.org/6067323:17
fungiclarkb: catching up now, but i abandoned the alphabetizing change. there's really no sane way to keep that in shape unless we have a check for it23:17
clarkbfungi: ok23:17
*** bpokorny has quit IRC23:19
zaromgagne: i assume that's a bump version and commit back to git?23:19
jeblairmgagne: does your proposal support not having version info in the source code at all (in a post-versioning system)?23:20
mgagnezaro: it's like pbr. you git tag, release is made by jenkins. you commit the next intended version with -SNAPSHOT. rinse and repeat.23:20
jeblairmgagne: maybe you just set $project.version to something and never touch it?23:20
sharwellmgagne: in your proposal, what in the content of the <version> element in pom.xml for a *tagged* commit23:20
sharwellthe way I read it, it would contain x.y.z-SNAPSHOT23:21
mgagnejeblair: I believe the sharwell's team have other projects depending on this artifact. They are using local maven repository to allow other project to download and build against this snapshot version. Without $project.version, they won't have any version to depend on.23:21
sharwellwhich would not be correct. if a user checks out a tagged commit and builds, it should produce x.y.z, not x.y.z-SNAPSHOT23:21
*** herndon has quit IRC23:21
zarosharwell: it's whatever we want it to be.  the ci system just passes it thru.23:21
zarosharwell: i believe the version plugin gives us the power.23:22
mgagnesharwell: a tagged commit would still have X.Y.Z-SNAPSHOT. (unfortunately)23:22
sharwellmgagne: zaro: I have to run for now,. I'll review again this evening and can continue discussing then or tommorrow23:22
*** ryanpetrello has joined #openstack-infra23:22
mgagnesharwell: as Jenkins won't commit the change it made with mvn versions:set.23:22
jeblairmgagne: i'm not sure that's the case, but that doesn't concern me at the moment; i just want to know if a post-versioned project can operate purely on tags, never updating a commit.23:23
*** paul-- has quit IRC23:23
zaromgagne: actually i was thinking it would be X.Y.Z-$git_sha23:23
mgagnejeblair: yes it can23:23
mgagnejeblair: with mvn versions:set, you set anything you want.23:23
praneshpcan someone help me get +2  review powers on https://review.openstack.org/#/admin/projects/stackforge/entropy,access23:24
mgagnejeblair: and commit (by Jenkins) is not required.23:24
*** thedodd has quit IRC23:24
zaromgagne: hmm, that doesn't seem right.23:24
zaromgagne: doesn't jenkins need to commit to bump the version?23:24
*** thedodd has joined #openstack-infra23:24
*** sergmelikyan has quit IRC23:24
mgagnezaro: snapshots made by Jenkins can have the format you want. it can be the one already used ("$SCM_TAG.$COMMITS_SINCE_TAG.$SCM_SHA")23:25
zaromgagne: maybe not jenkins but the version plugin?23:25
mgagnezaro: jenkins doesn't need to commit anything to be able to build an artifact23:25
zaromgagne: how does the version get bumped if not thru a commit?23:25
openstackgerritA change was merged to openstack-infra/jenkins-job-builder: Description Setter Plugin support added  https://review.openstack.org/6067423:26
zaromgagne: when dev clones they are expecting the bumped version right?23:26
openstackgerritA change was merged to openstack-infra/config: Add launchpad entries for openstack-manuals  https://review.openstack.org/6094323:26
mgagnezaro: version isn't "bumped" per se, it is a passthrough. you git tag, you take that version, you run mvn versions:set to set the value, you build the thing and you are done.23:26
mgagnezaro: the proposed system has the same limitations as pbr. someone needs to bump the version AFTER a release.23:27
*** dstanek has quit IRC23:27
zaromgagne: ohhh. i see.  /me not real familiar with pbr.23:27
openstackgerritA change was merged to openstack-infra/config: Add puppet_openstack_builder to gerritbot config  https://review.openstack.org/6101023:28
jeblairmgagne: are you talking about pre- or post versions?23:28
mgagnezaro: clarkb explained that the version stays the same in setup.cfg until someone bumps it.23:28
jeblairi really think it's important to specify.23:28
jeblairmgagne: that's true for pre-versioned projects.  not post-versioned.23:28
openstackgerritA change was merged to openstack-infra/config: Improve storyboard gate jobs  https://review.openstack.org/6111923:28
jeblairmgagne: all of our java projects will be post-versioned.  are yours pre-versioned?23:29
mgagnejeblair: pom.xml is pre-versioning IF $project.version is set to X.Y.X-SNAPSHOT. If it's X.Y.Z, it's post-versioning.23:29
openstackgerritJoshua Harlow proposed a change to openstack-infra/config: Re-enable patchset-created  https://review.openstack.org/6160523:29
jeblairmgagne: pbr does not require a version in setup.cfg at all for post versioning.23:29
fungipraneshp: i've added you as the initial member of the entropy-core group. you can add/remove other members at https://review.openstack.org/#/admin/groups/252,members23:30
*** thedodd has quit IRC23:30
mgagnejeblair: true, it is however present in all openstack projects I checked23:30
openstackgerritA change was merged to openstack-infra/config: Gerritbot: watch master on python-climateclient  https://review.openstack.org/6122023:31
jeblairmgagne: did you check the client projects?  they are all post-versioned.  the servers are all pre-versioned.23:31
praneshpthanks fungi23:31
mgagnejeblair: didn't check client projects23:31
jeblairmgagne: anyway -- bear with me here for a minute.  do you need pre-versioning?23:31
*** rcleere has quit IRC23:32
mgagnejeblair: I don't need anything, I'm helping people finding a way to answer their needs =)23:32
fungimgagne: compare http://git.openstack.org/cgit/openstack/nova/tree/setup.cfg to http://git.openstack.org/cgit/openstack/python-novaclient/tree/setup.cfg23:32
jeblairmgagne: can you tell me why we're talking about pre-versioning at all here then?23:32
jeblairi'm trying to make this conversation simpler.  :)23:33
mgagnejeblair: ok, to clarify, 2014.1 is pre-versioning right?23:33
*** ^demon has joined #openstack-infra23:33
jeblairmgagne: yes23:33
*** ^demon has quit IRC23:33
*** ^demon has joined #openstack-infra23:33
mgagnejeblair: this is what I'm proposing for java projects.23:33
jeblairmgagne: for yours or ours?23:33
openstackgerritDavid Ostrovsky proposed a change to openstack-infra/config: Gerrit-2.8: Add migration path document  https://review.openstack.org/6160623:33
*** jgrimm has quit IRC23:33
fungii'm not sure why this is suggested for java projects, unless simply because "java people expect preversioning schemes"23:33
mgagnejeblair: forget my projects. I'm referring to java projects managed by openstack23:34
jeblairmgagne: all of our projects will be post-versioned.23:34
mgagnejeblair: what fungi said.23:34
clarkbfungi: want to address https://review.openstack.org/#/c/61290/ really quickly and I will approve that change?23:34
fungiclarkb: sure23:34
mgagnejeblair: ok, I didn't know about the desire to move to "post-versioning"23:34
*** dims has quit IRC23:34
*** Adri2000 has quit IRC23:35
mgagnejeblair: I assumed what was in master of server-side projects (nova, cinder, etc.) was the way to go (pre-versioning)23:35
jeblairmgagne: those are pre-versioned because they are part of a time-based release process23:35
*** openstackgerrit has quit IRC23:35
*** ^d has quit IRC23:36
*** openstackgerrit has joined #openstack-infra23:36
jeblairmgagne: but we have no java projects that do time-based releases, so they should all be post-versioned23:36
mgagnejeblair: ok, I better understand now. then we have a clash.23:36
jeblairmgagne: (openstack client libraries are not part of the time-based release, so they are post-versioned)23:36
openstackgerritJeremy Stanley proposed a change to openstack-infra/jeepyb: Link git.o.o in bug updates  https://review.openstack.org/6129023:36
fungiclarkb: ^ thanks!23:36
*** Adri2000 has joined #openstack-infra23:36
*** Adri2000 has quit IRC23:36
*** Adri2000 has joined #openstack-infra23:36
mgagnejeblair: java projects are pre-versioned.23:36
lifelessI'm sorry, I can't help but read that as perversioned23:36
jeblairmgagne: not in zaro's system23:36
mgagnejeblair: zaro's system is none of them. there is no version at all.23:37
fungilifeless: i'm RIGHT there with you23:37
clarkbfungi: ty23:37
*** _david_ has quit IRC23:38
jeblairmgagne: so i'm interested in hearing more about host post-versioning works in your system with mvn versions plugin23:38
fungimgagne: well, there is a version in the release artifacts, but not in the files which are tracked by revision control23:38
jeblairmgagne: because it sounds like your idea is similar to zaros but would put a nicer version field in a locally built copy23:39
mgagnejeblair: I'll have to dig more on that one. One thing is sure, jenkins HAS to commit something on behalf of the release manager. (to bump version)23:39
*** blamar has quit IRC23:39
jeblairmgagne: that's something we definitely don't want to do.  this system should never have a commit to change a version number.23:39
mgagnejeblair: we would be back to my first iteration of the idea. A new Maven plugin doing what pbr does.23:39
fungihaving files under revision control track the state of the same revision control system gets into gödelian incompleteness territory23:40
mgagnejeblair: so devs can build SNAPSHOT with version based on git tags found in the repository23:40
openstackgerritA change was merged to openstack-infra/jeepyb: Link git.o.o in bug updates  https://review.openstack.org/6129023:40
*** ryanpetrello has quit IRC23:41
jeblairmgagne: i'm not sure why the version used for something locally built by a developer matters.  i think it would be nice if it showed a fully-correct version like pbr, but if it is something like "DEV" that doesn't bother me too much, especially if there's a script someone can run to build a copy with the correct git tag based version number.23:41
fungi("those who do not learn from mathematics are doomed to iterate infinitely")23:42
mgagnejeblair: that "script" should be a first class citizen in maven otherwise devs will have to change their workflow.23:42
zarojeblair: i think it's because it gets integrated with maven's dependency management system.23:42
zarojeblair: SNAPSHOT is very special.23:43
mgagnezaro, jeblair: yes. you have to fully grasp their workflow and how they use those snapshots, dependencies to understand the motivation being it.23:43
jeblairzaro: okay, so DEV-SNAPSHOT.  or 0.0.0-SNAPSHOT.23:43
*** ryanpetrello has joined #openstack-infra23:44
jeblairnothing should be depending on an unreleased locally-built version.23:44
mgagnejeblair: that's how maven works.23:44
*** dstanek has joined #openstack-infra23:44
fungifrom outside, it seems very much like someone codified cargo-cult behavior into a standardized workflow for these details to matter so much23:44
zarojeblair: actually the developer is dependent on it.23:44
zarojeblair: because anything built locally gets place into local maven repo and that gets reused by downstream projects.23:45
jeblairzaro: what downstream projects?23:45
zarojeblair: any other project that has a dependency on foo-x.y-SNAPSHOT23:45
fungi"downstream" sounds like it's javaspeak for "reverse dependency"23:45
fungiahh, good guess ;)23:46
*** paul-- has joined #openstack-infra23:47
jeblairmgagne, zaro: a maven plugin that behaves like pbr might be a good idea, but given that zaro's system achieves the goals we set out some time ago, and already works with some projects we have; i'd like to finish moving clouddocs-maven-plugin to it, and then possibly iterating from there23:48
mgagnezaro: not sure if it's a good comparison, but I think SNAPSHOT and local maven repo could be compared to python setup.py develop23:48
zaro++23:48
fungifor development to depend so heavily on locally-rebuilt dependencies smacks of a compile-everything-and-embed-rather-than-decouple development mentality23:49
fungiseems dangerous, but maybe that's normal in javaland23:50
clarkbjeblair: not to change the subject but https://review.openstack.org/#/c/61463/ feels a lot like working around the lack of public glance which I thought we were against doing23:50
clarkbjeblair: which is why dib hasn't become a thing for us23:50
mgagnefungi: sorry, that's how it works with maven23:50
*** masayukig has joined #openstack-infra23:51
jeblairclarkb: i don't think that's the case.  the devstack-gate setup scripts have always been about creating our own images.  also, mordred had a change to move nodepool to dib but he abandoned it.23:52
*** vipul is now known as vipul-away23:52
jeblairmgagne: so how about setting the version to 0.0.0-SNAPSHOT, and then having the downstream projects depend on that?23:53
*** bodepd has left #openstack-infra23:54
clarkbjeblair: right, but they aren't doing the takeover node thing and completely rewriting the underlying disk23:54
clarkbcaching small changes to existing known working images seems a lot less fragile than dd'ing over a image writing arbitrary bits to it and snapshotting that. However, this is the only practical way of moving forward so maybe I just deal with that23:55
*** adrian_otto has quit IRC23:55
*** jhesketh__ has joined #openstack-infra23:55
jeblairclarkb: wait, i'm confused.23:55
zaromgagne: it can be anything really, but i believe they just release a ver 12.1 or something like that.  so it would be 12.1.0-SNAPSHOT23:55
jeblairclarkb: the change you pointed me at doesn't do anything with dd.23:55
clarkbjeblair: it allows for dd23:56
*** openstackgerrit has quit IRC23:56
zarojeblair: oops, what i said to mgagne23:56
*** blamar has joined #openstack-infra23:56
jeblairclarkb: it allows you to upgrade a kernel...23:56
*** openstackgerrit has joined #openstack-infra23:56
*** datsun180b has quit IRC23:56
jeblairclarkb: it allows for a lot of things.  why are we talking about dd?23:56
mgagnejeblair: this would require changes in pom.xml of the other projects. Those projects have range of supported versions in pom.xml (it's like requirements.txt) With maven, you can create profile (in your home directory) which can be used to allow download of SNAPSHOT instead of release. This allows a dev to test their projects against bleeding edge versions of a dependency they just locally built 15 minutes ago without having to release them and23:56
clarkbjeblair: I believe the intention is feed nodepool an install script, nodepool runs install script, that script dd's over image with Xen bits, node reboots does more stuff to configure Xen bits, snapshot23:56
clarkbjeblair: we can already update the kernel without that feature23:57
jeblairmgagne: you got cut off at "having to release them and"23:57
clarkbthe existing nodepool scriptage does that for us23:57
mgagneand publish them to a public maven repo.23:57
jeblairmgagne: right, so once you have a downstream saying "i want to use something-SNAPSHOT", it doesn't really matter what the 'something' is, does it?23:57
mgagnejeblair: public maven repo being the equivalent of pypi in python23:57
mgagnejeblair: it does23:58
jeblairmgagne: why?  the thing you are indicating is "i want to run the most recent locally built version"23:58
mgagnejeblair: Do you have versions in requirements.txt? It's the same with Maven. You just can't tell the dev to sed everything to 0.0.0.23:58
zarojeblair: it depends on the version #23:58
jeblairmgagne: what would those different numbers be?  how can you have more than one most recent locally built version?23:59
jeblair00:01 < mgagne> jeblair: Do you have versions in requirements.txt? It's the same with Maven. You just can't tell the dev to sed everything to 0.0.0.23:59
jeblair00:01 < zaro> jeblair: it depends on the version #23:59
jeblair00:02 < jeblair> mgagne: what would those different numbers be?  how can you have more than one most recent locally built version?23:59

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