Friday, 2017-04-07

jeblair* (not a recommended production configuration) ;)00:00
jlklol yeah00:00
jlkoh I'm getting alarm clock on feature/zuulv3  Interesting. I wasn't before00:11
*** jamielennox is now known as jamielennox|away04:18
tobiashjeblair: thanks for approving the semaphore patch :)05:36
tobiashjeblair: what should be the process for the v2 version of that patch?05:37
tobiashjeblair: shall I abandon this now or leave it open for others until the release of v3 and abandon this then?05:37
tobiashSpamapS: I've left a comment on https://review.openstack.org/#/c/450704/06:45
tobiashSpamapS: I still think it's cleaner to use unicode but I'm ok with abandoning the patch if wanted06:45
*** bhavik1 has joined #zuul09:09
*** yolanda has quit IRC09:19
*** yolanda has joined #zuul09:19
*** bhavik1 has quit IRC09:29
*** openstackgerrit has quit IRC11:18
*** hashar has joined #zuul11:35
*** tobiash has quit IRC13:12
*** openstackgerrit has joined #zuul13:15
openstackgerritMerged openstack-infra/nodepool feature/zuulv3: Show message if node hold not found  https://review.openstack.org/45397113:15
eggshello/14:15
jlkSo I let a bisect run last night, 916acb0a64c3afdde1a098cf0232b829ec68376b was the last hash that I could run tests locally.14:27
jlk91132fbe9155b4482e267b9d3ba703ea62c6eeba is where things started to fail.14:27
mordredjlk: if you do a git revert of 14ab6ca01a8827918cb50dcb90a40c293786ea01 (the commit that commit merged) - does the tree work for you again?14:30
jeblairjlk: since that's just enabling a single test, the cause may be testtools reshuffling test order in a way which caused more contention.14:31
mordredyah- that's why I'm kind of curious if a revert on top of things fixes things again14:31
mordredbecause wow that commit certainly doesn't seem be the sort of thing that would do anything substantial like break everything14:32
jeblairmordred: i was thinking -- there's one other aspect of the config/project repo difference that is sort of hidden by changing the names to 'trusted/untrusted projects' -- config repos are allowed to configure more things (like pipelines), and are branchless (we only read from the master branch).14:37
jeblairmaybe that's two things.  :)14:38
*** hashar has quit IRC14:40
mordredjeblair: hrm. I agree with you- both that it hides things, and that it hides two things14:45
Shrewsjeblair: i think the first thing is sort of inherent in the "trusted" thing. the branch thing is not obvious though14:46
jeblairShrews: yeah, the branch thing is more subtle14:46
Shrewsit's actually a bit counterintuitive that trusted projects are constrained to master, but untrusted aren't14:49
Shrews(from a non-zuul-expert POV)14:49
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (1/2)  https://review.openstack.org/45336214:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Replace config/project repos with trusted/untrusted projects  https://review.openstack.org/45334714:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add hostname to TriggerEvent  https://review.openstack.org/45234814:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (2/2)  https://review.openstack.org/45382114:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fully qualify project configuration names  https://review.openstack.org/45197014:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add source to project and remove unused tenant attrs  https://review.openstack.org/45196914:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Pass source to project instantiations  https://review.openstack.org/45159614:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Add a project index to Tenant  https://review.openstack.org/45159714:51
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove unused Tenant.getRepo method  https://review.openstack.org/45192914:52
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Use new tenant project index for config references  https://review.openstack.org/45192814:52
mordredjeblair: maybe we should go back to config repos and project repos and just rename the opentsack-infra/project-config repo so that we personally don't go crazy :)14:52
jeblairShrews: yeah, i think fundamentally 'trusted project' says "this is a project of higher status" when it's the other way around -- it's a project that principally serves zuul.14:53
jeblairmordred: yeah, maybe... though i do still want to remove the word 'repo' from the tenant config file...14:54
jeblairconfig-project / untrusted-project?  config-project / project?14:55
Shrewszuul-project / project ?14:56
Shrewsblue-pill / red-pill ?  :)14:57
jeblairfred / ginger ?14:57
mordredjeblair: naming sucks14:58
jeblairya14:58
jlkjeblair: mordred: yeah sorry I had to step away for some domestic duties. I plan to try a variety of things with the tree today to figure out what's going on with tests.15:27
jlkthis could be a false report from bisect, so more investigation is needed.15:29
pabelangerShrews: so, found an issue with nodepool-launcher, if we remove a provider from configuration, with images still uploaded to cloud, we have no way to remove them from zookeeper15:32
pabelangerShrews: you can see this on nodepool.o.o today, with the tripleo-test-cloud-rh2 provider15:32
Shrewspabelanger: out to lunch, but pretty sure jeblair put code in to handle that15:33
pabelangerk15:33
Shrewsiirc. Could be misremembering15:34
ShrewsSomething something obsoleteProvider something15:35
jeblairpabelanger: https://docs.openstack.org/infra/nodepool/operation.html#removing-a-provider15:35
jeblairthere's the wind-down procedure for a provider15:35
pabelangerhttps://review.openstack.org/#/c/451115/1/nodepool/nodepool.yaml15:37
pabelangermax-servers was 015:37
pabelangerthat likely explains it15:37
pabelangerokay, I'll clean this up15:37
jeblairpabelanger: max servers 0 should be fine too as long as all the images are removed.15:38
pabelangerjeblair: images: [] in provider section enough for that?15:38
jeblairpabelanger: yep.15:38
pabelangerk15:39
jeblairpabelanger: i think you can even omit the key entirely15:39
jeblairmordred, Shrews: i'm leaning toward config-project / untrusted-project.15:40
mordredjeblair: thesaurus.com lists "thing" as a synonym for project ... so we could do config-thing and untrusted-thing15:42
jeblair(i feel like 'project' needs a modifier for each one)15:42
jeblairbwahaha15:42
mordredjeblair: also, in the bwahaha section, "baby" shows up as an informal synonym - I think "config-baby" vs "untrusted-thing" would be great15:43
mordredor maybe just "baby" and "thing"15:43
jlkresource, archive, codex, .... suppository (as opposed to repository)15:43
jeblairmordred: is thesaurus.com just a random word generator?15:44
mordredyah15:44
mordred""" project c.1400, "a plan, draft, scheme," from L. projectum "something thrown forth," """ - in case anyone was curious15:45
jlkI have no joke, I just like saying "projectum"15:45
*** tobiash has joined #zuul15:45
jeblairi think that fairly well describes what we're trying to accomplish here.  :)15:48
openstackgerritPaul Belanger proposed openstack-infra/nodepool master: Remove ubuntu-precise from dsvm-nodepool jobs  https://review.openstack.org/45479416:36
jlkmaybe I just need to reboot the VM between each test run :/16:36
*** tobiash has quit IRC17:14
*** tobiash has joined #zuul17:15
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (1/2)  https://review.openstack.org/45336217:16
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Replace config/project repos with trusted/untrusted projects  https://review.openstack.org/45334717:16
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (2/2)  https://review.openstack.org/45382117:16
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fully qualify project configuration names  https://review.openstack.org/45197017:16
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Extend test timeout to 120s  https://review.openstack.org/45480617:16
jeblairjlk: i'm bumping the test timeout in my stack ^.  i'd like to pare it back later, but at the moment, the tests are doing a lot of extra work which will take some effort to clean up.17:18
jeblairjlk: that may help17:19
jlkI was using a rather long timeout. I think there's just something about repeated runs in the same environment that are making things fail. I rebooted and a commit that had previously failed started working.17:20
jeblairjlk: hrm.  you might also try removing the .testrepository directory between runs.  that should cause testr to avoid "optimizing" the ordering of the tests.17:22
jlkoh good call.17:22
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fix dynamic reconfiguration  https://review.openstack.org/45439517:37
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: WIP test lookups  https://review.openstack.org/45439617:37
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Set jobdir to 0755 before we delete it  https://review.openstack.org/45481917:38
pabelangerjeblair: clarkb: ^ os.walk change17:44
clarkbwas just looking at that, I think this is simpler than the error handler method17:46
clarkbwondering if we shouldn't try to unlink directly rather than shutil.rmtree17:47
clarkbbut that also seems like less simple17:48
jeblairi think os.walk is going to be top-down?  presumably rmtree is bottom-up?  so this is probably the most reliable thing?17:49
pabelangerthink so17:50
clarkboh good point17:50
jeblair(ie, if we unlink on the way down, we may still encounter errors.  so we need to chmod all the way down before we can start unlinking on the way up)17:50
mordredjeblair: I think you can recurse with os.walk and then do the rms on the way back up the stack?17:50
clarkbyou can make os.walk do it the other way but ya17:50
mordredjeblair: you said words better than I did17:50
clarkbI left a comment and looks like pep8 is unhappy17:50
jeblairoh, yeah, we run pep8 under py3 now so that needs to be 0o755 now17:51
clarkbaha17:52
pabelangergreat17:52
pabelangerlet me fix17:52
openstackgerritPaul Belanger proposed openstack-infra/zuul master: Set jobdir to 0755 before we delete it  https://review.openstack.org/45481917:53
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (1/2)  https://review.openstack.org/45336217:54
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Replace config/project repos with trusted/untrusted projects  https://review.openstack.org/45334717:54
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (2/2)  https://review.openstack.org/45382117:54
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Extend test timeout to 120s  https://review.openstack.org/45480617:54
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Fully qualify project configuration names  https://review.openstack.org/45197017:54
pabelangertmpreaper, that was the app I was thinking of17:55
pabelangerI'll see about adding puppet-tmpreaper to zl.o.o servers17:55
jeblairhandy but we can't rely on it.  an executor can fill up / very quickly.  :)17:55
pabelangertrue17:56
openstackgerritCullen Taylor proposed openstack-infra/zuul feature/zuulv3: [WIP] Integration: Get static nodes from nodepool  https://review.openstack.org/45482617:56
mordred13870918:01
jeblairthat's a very old change number.  yes that's what that is.18:03
openstackgerritMerged openstack-infra/zuul master: Set jobdir to 0755 before we delete it  https://review.openstack.org/45481918:04
*** rcarrill1 has joined #zuul18:05
pabelangerAlso, when was the last time we restart v25 launchers for zuul?18:05
pabelangerpretty nice, not having to do that weekly :)18:05
*** rcarrillocruz has quit IRC18:06
SpamapSjlk: if removing .testrepository works, then you can likely find the misbehaving test(s) with analyze-isolation18:52
jlkit doesn't work in isolation.  A full reboot seems to have some help?18:53
SpamapSanalyze-isolation tries to find tests that interact with the others18:53
SpamapSbut a full reboot suggests .testrepository isn't the problem really.. maybe it's the zookeeepr18:54
jlkSlowly climbing up the commit tree. I tried skipping  afew and hit a failure. I'm kind of doing my own manual bisect.18:59
clarkbalso if tests don't work when isolated then likely not an inter test interaction19:00
pabelangerhttps://review.openstack.org/#/c/454794/ removes ubuntu-precise from our dsvm job, since it is EOL19:02
SpamapSthe tests DO work when isolated19:07
SpamapSonly running the full suite produces the weird timeouts19:07
clarkbah19:07
SpamapSwhich suggests there's an ordering issue19:07
clarkbjlk said they don't work in isolation above19:07
SpamapSwhich is exactly what testr can fix19:07
SpamapSclarkb: "it" being the full suite19:07
SpamapSI took it as anyway.19:07
SpamapSDunno, but I'm having similar issues to jlk19:08
SpamapSto the point where I don't even bother trying to run it locally anymore19:08
jlkI'd go that route, but my change is failing upstream and I would like to figure out why :/19:10
clarkbjust thinking off the top of my head the .testrepository and zk server aren't reused in the gate19:10
clarkbthe .testrepository not being used means the test ordered in the gate is naive, but will be "smart" locally if you have at least one test run recorded19:11
SpamapSjlk: oh you're geting a timeout fail in the gate too? but a different one?19:15
SpamapSthat I missed19:15
openstackgerritMerged openstack-infra/nodepool master: Remove ubuntu-precise from dsvm-nodepool jobs  https://review.openstack.org/45479419:19
*** openstackgerrit has quit IRC19:19
jlkSpamapS: I'm not sure what's happening in the check queue, it's 80~ megs of logs :)  I'll wget it at some point.19:22
clarkbapparently we need a mysql now?19:25
* clarkb will get one19:25
clarkbbut first lunch19:25
mordredclarkb: ya - for tests of the mysql reporter19:26
jeblairmordred, pabelanger: i'm trying to put things in order before i leave next week --20:06
jeblairi'm not going to finish https://review.openstack.org/454396 today, so perhaps you can continue working on it next week.  i've established a pattern there, so it should be fairly easy to go through the rest of the lookups20:07
jeblairin fact, you could just land that patch and then do followups20:07
jeblairit's parent is already ready to land.20:07
jeblairpabelanger: i think we're okay to re-start zuulv3-dev now, and proceed with more jobs when you're ready20:08
pabelangergreat. Yes, I'll help work on the lookup tests for sure20:09
jeblairpabelanger: feel free to just take over that change if you want.  you can add new tests directly to it, or drop the WIP, land it, and do followups.20:10
pabelangerk20:10
clarkbjlk: is test_playbook one that fails for you when run in the full suite?20:10
jeblairclarkb, fungi, pabelanger, SpamapS: it looks like the zuulv3 executor security spec is ready, so i've added it to next week's infra meeting agenda for approval even though SpamapS won't be there.  i suspect it's been gone over enough to do this async, but of course, if there are objections in the meeting, the chair can just postpone it until next week (that's why we put these on the meeting agenda after all).20:13
pabelangerjeblair: ack20:22
*** rcarrill1 is now known as rcarrillocruz20:23
clarkbits on my list of changes to review20:26
clarkbalong with the translation site spec ...20:26
*** rcarrillocruz has quit IRC20:31
*** rcarrillocruz has joined #zuul20:32
fungiwfm20:34
fungii still intend to go through it this weekend as well20:34
*** openstackgerrit has joined #zuul20:37
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (1/2)  https://review.openstack.org/45336220:37
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Replace config/project repos with config/untrusted projects  https://review.openstack.org/45334720:37
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: Remove source from pipelines (2/2)  https://review.openstack.org/45382120:37
jeblairmordred, Shrews: ^ that's now 'config-projects' and 'untrusted-projects'.20:37
jlkclarkb: that's one I see often, yes.21:07
jlkOooh, I think I have a repeatable failure.22:01
jlk87834afb2a8b70113a91ebe094031d725e2385d9 seems to consistently fail.22:01
jlkbefore it passes.22:01
jlk( 1ba9651166e7d8b6d720a97ae22b0abb08ede594 )22:01
clarkbjlk: SpamapS going off of spamaps idea I seem to only have the sql tests (because no mysql currently) fail if I delete my zk datadir before running tests22:13
clarkbso I'm guessing that something is polluting the zk db22:13
clarkbit also looks like I leaked a nodepool test chroot22:17
clarkb(not sure if related at all yet)22:17
clarkboh that was concurrency=1 too22:19
clarkbso now sorting out if concurrency=1 is sufficient22:29
jlkI'm reverting the commit that seems to break me to see if things start working.22:29
clarkbjlk: it looks like doing tox -epy27 -- --concurrency=1 is sufficient to make things reliable22:45
clarkbjlk: so looking like intertest conflict22:45
clarkb(also we reliably leak our last used zk chroot. So I'm gonna poke at that)22:45
clarkbdoesn't look like every test leaks so nwo to find which one(s) do22:52
jlkHey look at that.23:20
jlkI reverted ae04e4ce8fca33872f3677838d6a813d2c378e79 and things keep working.23:20
jlkfd0354a094116fab6496e025f7a23f888322058c is the last commit before my revert.23:21
jesusaurjlk: womp womp :(23:27
jesusauris it consistent which tests break?23:27
jlkjesusaur: heh, yeah, sorry about that....23:27
jlkit's test_playbook for me23:27
clarkbjesusaur: it seems like its intertest conflict because --concurrecny=1 works23:28
clarkbmaybe git repo state is being shared somehwere it shouldn't in the test suite?23:28
jesusaurpossibly23:29
jesusaurseveral of the test_v3.py tests were giving me trouble23:29
jesusaurI think test_dynamic_config is the one that tripped me up the most, then it would pass when re-running tox with --failing23:30
clarkbseparately I think I have a couple improvements to the kazoo fixture to make debugging things easier (and might have foudn the reason we leak sometimes)23:30
clarkbjust waiting for tests to finish so I can push things23:30
mordredclarkb: woot23:33
clarkbnope that didn't fix the leak but I know which test does it now23:43
clarkbheh and it doesn't leak when run on its own23:45
clarkbso confused23:45
clarkbthis is interesting. Subunit file says the leaked test failed, but stdout from testr doesn't say it failed. Though the sql tests did fail23:49

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