Friday, 2016-12-09

*** jamielennox|away is now known as jamielennox00:08
SpamapSjeblair: http://paste.openstack.org/show/591877/ <-- does this look valid to you? I'm not sure I truly understand how auth: is supposed to be used. :-P00:16
SpamapSjeblair: when we get into the launcher, the auth sections are not attached to the jobs that run.00:16
SpamapSergo, no swift params are sent00:16
*** harlowja_ has quit IRC00:32
SpamapSjeblair: more for the plot.. if I add 'inherit: true' to the _project_ job definitions, it works. (Which seems backwards to me)00:36
* SpamapS runs into "oh and we have to configure the connection" and EOD's00:40
*** harlowja has joined #zuul00:51
*** jamielennox is now known as jamielennox|away01:04
openstackgerritdongwenjuan proposed openstack-infra/nodepool: add log input para to ssh_connect  https://review.openstack.org/40887301:11
*** jamielennox|away is now known as jamielennox01:20
*** saneax is now known as saneax-_-|AFK01:30
*** harlowja has quit IRC02:55
ianwjeblair greghaynes pabelanger: got in contact with fedora-infra at #fedora-admin and they fixed up an issue with the mirrors and stale data.  so think this one was out of our hands03:28
greghaynesianw: ah, thanks03:29
openstackgerritJoshua Hesketh proposed openstack-infra/zuul: Add note about redundant file  https://review.openstack.org/40894904:42
openstackgerritJoshua Hesketh proposed openstack-infra/zuul: Don't try to execute _stop commands  https://review.openstack.org/40895004:42
openstackgerritJoshua Hesketh proposed openstack-infra/zuul: Add command list into server.py  https://review.openstack.org/40895104:42
openstackgerritJoshua Hesketh proposed openstack-infra/zuul: Add zmq back into launcher server  https://review.openstack.org/40895204:42
*** saneax-_-|AFK is now known as saneax05:46
*** hashar has joined #zuul08:21
*** yolanda has quit IRC09:22
*** Cibo_ has quit IRC10:44
*** Cibo_ has joined #zuul10:46
*** bhavik1 has joined #zuul11:31
*** hashar is now known as hasharLunch12:18
*** jamielennox is now known as jamielennox|away12:33
*** hasharLunch is now known as hashar13:07
*** abregman has joined #zuul13:17
*** abregman has quit IRC13:17
*** patrickeast has quit IRC14:38
*** patrickeast has joined #zuul14:38
*** saneax is now known as saneax-_-|AFK14:52
*** zaro has quit IRC15:02
*** zaro has joined #zuul15:03
*** docaedo has left #zuul15:22
jeblairSpamapS: http://paste.openstack.org/show/591877/ looks right enough.  there isn't much auth-related code in v3 yet, so yeah, there will be configuration parsing/model stuff to write (including the inherit thing) as well as hooking that into ansible variables in the launcher.  you may want to check in with rcarrillocruz who is working on the 'secrets' system which is also part of auth, though i don't think he has touched that part of it yet (is ...16:56
jeblair... mostly working on encryption keys, etc).16:56
SpamapSjeblair: I assume the secrets part will also include something to setup swift connections.17:03
jeblairSpamapS: no, that's separate -- 'secrets' here referring just to user supplied key/value secrets.17:08
*** hashar has quit IRC17:31
*** bhavik1 has quit IRC17:32
SpamapSjeblair: Ah, k. Swift is more-specialer then :-18:00
SpamapS:-P18:00
jeblairSpamapS: yeah, we probably want to build a formal plugin interface for auth plugins, but we don't have one yet.  maybe we can do that for 3.0; or maybe for 3.1.  :)18:01
SpamapSYeah I think when the third one shows up is the time to design that interface. :)18:06
SpamapSI'm not going to be around consistently today.. taking care of a sick baby (who is about to wake up from morning nap)_18:07
Shrewsjeblair: 408808 actually has a redundant check that i just noticed. it's safe, though18:17
jeblairShrews: oh yeah... we should actually probably read the object again inside the lock18:17
Shrewsjeblair: well, the idea was to avoid unnecessary zk ops, so that would add an extra op.18:18
Shrewsi think it's better to just remove it18:18
openstackgerritMerged openstack-infra/nodepool: Add __repr__ to ConfigValue objects  https://review.openstack.org/40877618:19
Shrewsonly on rare occasions would it set it to DELETING unnecessarily18:19
openstackgerritMerged openstack-infra/nodepool: Check for in progress build/upload in CLI  https://review.openstack.org/40879418:19
jeblairShrews: yeah, i think removing the check is fine.18:20
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Re-use build data when we set for DELETING  https://review.openstack.org/40880818:21
Shrewsjeblair: there ya go18:21
Shrewsmordred: could you poke 408808 once more?18:24
mordredShrews: done18:26
*** harlowja has joined #zuul18:32
*** harlowja_ has joined #zuul18:34
*** harlowja has quit IRC18:35
openstackgerritMerged openstack-infra/nodepool: Re-use build data when we set for DELETING  https://review.openstack.org/40880819:28
*** openstack has joined #zuul19:47
pabelangerboth builders have been restarted19:52
pabelangerhad to do the touch fedora-24-0000000005.raw trick again to remove pending deleting diskimages19:52
pabelangergoing to write up a test for that now19:52
pabelangermake sure it works properly19:53
clarkbpabelanger: need to erap the deletes in if os.path.exists ?19:55
pabelangerclarkb: not sure, but this happens when we stop nodepool-builder while a diskimage build is in progress.  Should be easy to reproduce and see why it happens19:56
openstackgerritPaul Belanger proposed openstack-infra/nodepool: Make diskimage-builder command configurable for testing  https://review.openstack.org/40497620:43
openstackgerritPaul Belanger proposed openstack-infra/nodepool: Properly cleanup failed diskimage builds  https://review.openstack.org/40932720:43
pabelangerclarkb: Shrews: ^ reproduced our issue, test included20:43
mordredpabelanger: woot!20:44
Shrewspabelanger: that won't work20:46
Shrewspabelanger: we don't want to delete the zk node unless the local file is deleted first20:46
Shrewspabelanger: otherwise, a builder that doesn't own the build could delete the zk node, and the owner would never know to delete the local files20:47
clarkbmaybe we need to store the builder id in with the build data, and if self == builder_id and file not on disk then remove?20:50
clarkbthat still leaves you open to the issue where a builder goes away completely but that will be less common20:50
Shrewsi'm not sure that i'm clear on the issue... we stop the builder, and the build is recored as FAILED, right?20:51
Shrewsoh, now i remember. it gets to the DELETING state and never goes away20:52
Shrewsclarkb: we used to do that check, but jeblair suggested we remove that for some reason i do not recall now20:53
clarkbShrews: correct its set to delete but it can't delete because there is no file on disk20:54
clarkbanother way to address it would be to touch empty files at the start of every build and let dib overwrite them20:54
clarkbbut that way you have the markers on disk for when a failure happens20:54
clarkbthats a fairly simple fix if we want to make it "symmetric"20:55
jeblairclarkb, Shrews: i think the builder name check is what we'll have to do (i think we discussed this already?)20:56
*** jamielennox|away is now known as jamielennox20:58
pabelangerShrews: yes, DELETING state, doesn't go away until we touch a fake file20:58
pabelangerclarkb: not sure I'm a fan of the touch file and have dib overwrite21:02
jeblaircan someone go ahead and implement the builder name check?21:05
jeblairhere's where we talked about this yesterday: http://eavesdrop.openstack.org/irclogs/%23zuul/%23zuul.2016-12-08.log.html#t2016-12-08T20:10:3021:05
Shrewspabelanger: in deleteLocalBuild, if the "if not files" is true, compare hostnames there. you may need to pass in the builder in21:07
Shrewsjust return True if the names match21:08
Shrewss/pass in the builder in/pass in the builder name/21:08
Shrewsor the build object21:08
pabelangersure, let me poke at it21:09
Shrewspabelanger: self._hostname should already be set for you21:11
openstackgerritPaul Belanger proposed openstack-infra/nodepool: Properly cleanup failed diskimage builds  https://review.openstack.org/40932721:25
pabelangerShrews: jeblair: If I understand the request correctly^21:26
jeblairpabelanger: can you avoid moving the log message?  it's going to false fire on non-responsible builders21:29
Shrewspabelanger: +1, but good point jeblair just made21:29
pabelangeryes, let me move back21:30
openstackgerritPaul Belanger proposed openstack-infra/nodepool: Properly cleanup failed diskimage builds  https://review.openstack.org/40932721:32
pabelangerjeblair: when you have time too: 404976 moves fake-image-create out of builder.py too21:52
*** jamielennox is now known as jamielennox|away22:04
*** jamielennox|away is now known as jamielennox22:11
*** jesusaur has quit IRC22:15
adam_gtest suite question: a FakeChange that has its data['status'] = 'MERGED' should be merged into the corresponding repo in /tmp/$tmpdir/zuul-test/upstream/ ?22:42
adam_gor do they not actually hit the merger?22:43
adam_g(v3, btw)22:43
*** cinerama has quit IRC22:47
*** cinerama has joined #zuul22:47
jeblairadam_g: i *think* so, but that's a relatively recent change23:31
adam_gjeblair: i guess what i should be asking is whether post-gate merging expected to be functional at all ATM?23:36
adam_give found what i think is a bug in the launcher merging23:36
adam_gand was trying to trace a change end-to-end, and diff'ing behavior against a v2.5 env23:37
jeblairadam_g: yeah, FakeChange.setMerged() updates the upstream git repo, and it's called by FakeGerritConnection.review() (which is the thing that zuul does to tell gerrit to merge something)23:38
jeblairadam_g: so it *should* dtrt to the upstream repo.23:39
jeblairadam_g: oh but wait, you said 'launcher merging'23:39
jeblairadam_g: which makes me think you're actually looking at a different subsystem23:39
adam_gjeblair: well, the launcher merging thing was something else i was looking at23:40
jeblairadam_g: the merging that happens in the launcher is the speculative merging -- it should only modify the local repo in the JobDir that's created for each job23:40
adam_gbut got me trying to setup a basic end-to-end test, trying to assert things get merged upstream in the correct order23:40
adam_gjeblair: right23:40
jeblairadam_g: ok cool.  btw, there are some tests in test_scheduler that are similar to what you describe, they may be helpful23:41
adam_glet me push what ive got, cause ive got another question while i have you23:41
jeblairadam_g: test_parallel_changes is a basic A,B,C test -- though it only checks the change metadata, it doesn't actually inspect the repo (but there should be others that do)23:42
openstackgerritAdam Gandelman proposed openstack-infra/zuul: Re-enable test_build_configuration_conflict  https://review.openstack.org/40937623:48
adam_gjeblair: so looking through self.history (on the test in ^), i see the correct number of jobs being run, but not with the expected dependent changes included23:50
adam_ghttp://paste.openstack.org/show/591994/23:51
adam_gi'd expect one of those merge tests to include 3,1 + 1,223:52
adam_ghmm, ill look closer at test_parallel_changes, that appears to be producing the result i'd expect23:54
jeblairadam_g: i think there's going to be a v2->v3 difference here because of the merge conflict23:56
adam_gohh23:56

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