Friday, 2019-06-07

*** panda has quit IRC00:01
*** mattw4 has quit IRC00:03
*** panda has joined #zuul00:04
*** rlandy|ruck is now known as rlandy|ruck|bbl00:08
tristanCShrews: is there a bug report somewhere with the k8s issue details?00:35
tristanCShrews: authentication issues may relate to how the zuul executor prepare the kube config, perhaps some provider requires extra settings?00:36
corvustristanC: i think SpamapS that was encountering that and may have more info00:37
corvuss/that//00:37
ShrewstristanC: you'll have to ask SpamapS00:39
tristanCSpamapS: indeed we do test and use the openshift provider successfully00:45
tristanCpabelanger: there is a pagination widget that may works for the builds page using the skip/limit parameters: https://www.patternfly.org/pattern-library/navigation/pagination/00:49
*** michael-beaver has quit IRC01:09
tristanCShrews: SpamapS: or maybe the k8s service account created by nodepool is not working: https://opendev.org/zuul/nodepool/src/branch/master/nodepool/driver/kubernetes/provider.py#L17901:12
*** jamesmcarthur has joined #zuul01:14
*** jamesmcarthur has quit IRC01:18
tristanCso, according to k8s docs, services account may not work depending on the cluster configuration, see the note at the top of: https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/01:20
tristanCit's unclear what type of behavior are required, but it seems like we should requires https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#serviceaccount01:21
tristanCand some rbac according to: https://kubernetes.io/docs/reference/access-authn-authz/rbac/#upgrading-from-1-501:23
tristanCfor example, gke doesn't seems to authorize service account to be used from the outside of the cluster01:27
*** sanjayu_ has quit IRC01:31
pabelangerShrews: thanks for thre review, didn't see it before01:32
pabelangertristanC: okay, thanks. I'll try web 2.0 skills :)01:33
openstackgerritTristan Cacqueray proposed zuul/zuul master: model: add annotateLogger procedure  https://review.opendev.org/66381902:07
*** rlandy|ruck|bbl is now known as rlandy|ruck02:12
*** rlandy|ruck has quit IRC02:15
*** sean-k-mooney has quit IRC02:28
*** jamesmcarthur has joined #zuul02:29
*** threestrands has joined #zuul02:54
*** jamesmcarthur has quit IRC02:58
*** sean-k-mooney has joined #zuul03:00
*** sean-k-mooney has quit IRC03:14
*** sean-k-mooney has joined #zuul03:16
*** threestrands has quit IRC04:12
*** sean-k-mooney has quit IRC04:19
*** sean-k-mooney has joined #zuul04:21
*** swest has joined #zuul04:43
*** raukadah is now known as chandankumar04:55
*** flepied has joined #zuul05:45
*** gtema_ has joined #zuul06:05
*** evgenyl has quit IRC06:20
*** evgenyl has joined #zuul06:24
*** sanjayu_ has joined #zuul06:27
*** sanjayu_ has quit IRC06:32
*** pcaruana has joined #zuul06:35
*** yolanda__ is now known as yolanda06:56
openstackgerritJean-Philippe Evrard proposed zuul/zuul-jobs master: Revert "Explicitly store date facts for promote"  https://review.opendev.org/66384806:56
openstackgerritTristan Cacqueray proposed zuul/zuul master: model: add annotateLogger procedure  https://review.opendev.org/66381906:58
openstackgerritJean-Philippe Evrard proposed zuul/zuul-jobs master: Revert "Explicitly store date facts for promote"  https://review.opendev.org/66384806:58
*** hashar has joined #zuul07:14
openstackgerritJean-Philippe Evrard proposed zuul/zuul-jobs master: Revert "Explicitly store date facts for promote"  https://review.opendev.org/66384807:21
*** jpena|off is now known as jpena07:53
openstackgerritMerged zuul/zuul-jobs master: Revert "Explicitly store date facts for promote"  https://review.opendev.org/66384807:58
*** sanjayu_ has joined #zuul08:00
*** sanjayu_ has quit IRC08:09
*** saneax has joined #zuul08:10
openstackgerritMatthieu Huin proposed zuul/zuul-jobs master: install-nodejs: add support for RPM-based OSes  https://review.opendev.org/63104908:49
ofososIs there anything I need for the test to run despite a zookeeper daemon? I think my tests fail while waiting for a node to run jobs on.... :(08:51
ofosos(Want to run locally)08:53
openstackgerritMark Meyer proposed zuul/zuul master: Add Bitbucket Server source functionality  https://review.opendev.org/65783708:54
openstackgerritMark Meyer proposed zuul/zuul master: Create a basic Bitbucket build status reporter  https://review.opendev.org/65833508:54
openstackgerritMark Meyer proposed zuul/zuul master: Create a basic Bitbucket event source  https://review.opendev.org/65883508:54
openstackgerritMark Meyer proposed zuul/zuul master: Upgrade formatting of the patch series.  https://review.opendev.org/66068308:54
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213408:54
*** zbr has joined #zuul09:29
*** sanjayu_ has joined #zuul09:34
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213409:35
*** saneax has quit IRC09:36
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213409:51
*** flepied has quit IRC10:00
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213410:13
*** gtema has joined #zuul10:34
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213410:35
*** gtema_ has quit IRC10:35
*** zbr is now known as zbr|rover10:44
*** flepied has joined #zuul10:50
openstackgerritAurelio Jargas proposed zuul/zuul master: Break long repo names to make them fit  https://review.opendev.org/66389911:12
*** sanjayu_ has quit IRC11:19
*** saneax has joined #zuul11:20
*** saneax has quit IRC11:24
*** saneax has joined #zuul11:25
*** hashar has quit IRC11:31
*** hashar has joined #zuul11:31
tobiashofosos: you mean the tox tests?11:31
tobiashofosos: in that case you could just run the tools/test-setup-docker.sh script that starts all test requirements in containers11:32
*** jpena is now known as jpena|lunch11:38
ofosostobiash: thanks, that sounds good :)11:38
ofososDoes the `tenant_config_script' get executed just once during startup?11:41
*** EmilienM is now known as EvilienM11:45
*** [GNU] has joined #zuul12:03
[GNU]hey all, is anyone aware of a job that is waiting for a pod to be terminated successful, so that I can peek at the playbook and learn from it!? :)12:04
*** sanjayu_ has joined #zuul12:05
[GNU]kubernetes pod ... btw :)12:07
*** saneax has quit IRC12:08
*** sanjayu__ has joined #zuul12:08
*** sanjayu_ has quit IRC12:11
*** sanjayu_ has joined #zuul12:19
*** sanjayu__ has quit IRC12:22
*** ianychoi_ has joined #zuul12:23
*** ianychoi has quit IRC12:27
*** paladox has quit IRC12:27
*** flaper87 has quit IRC12:27
*** flaper87 has joined #zuul12:29
*** rlandy has joined #zuul12:32
*** rlandy is now known as rlandy|ruck12:33
*** jpena|lunch is now known as jpena12:47
*** sanjayu_ has quit IRC13:07
*** saneax has joined #zuul13:12
*** felixgcb has joined #zuul13:20
*** jamesmcarthur has joined #zuul13:32
*** chandankumar is now known as raukadah14:06
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213414:29
felixgcbHey :) is somebody already using zuul's nodepool ontop of kubernetes (or aws eks)? I wonder if there is some config repo / blog post I could check out...14:35
clarkbfelixgcb: I think tristanC is using it with openshift. I don't know if they have written any blog posts about it14:40
clarkbthat is the software factory zuul install14:40
tobiashofosos: it gets executed during startup and full reconfigurations14:42
[GNU]felixgcb, on OpenShift?! :) yes14:42
[GNU]tristanC, has help a lot with that and has some good blogs on it14:43
*** paladox_ has joined #zuul14:51
*** paladox_ is now known as paladox14:53
*** paladox is now known as paladox__14:53
*** paladox__ is now known as paladox14:53
felixgcb[GNU]: nah on AWS EKS, but I heard the openshift driver can also be used for that. Do you have the links for those blogposts by any chance?14:56
felixgcbI think the kubernetes driver would be more fitting, but it says in the docs that it needs cluster admin permissions. That's a little much :D14:58
[GNU]felixgcb, ja, the openshift driver is basically just using kubectl (iirc), pls have a look around https://www.softwarefactory-project.io/category/blog.html14:58
[GNU]hmm, I'm not a cluster admin with the openshift driver14:59
felixgcbYes the openshift driver needs much less permissions14:59
felixgcbOk I'll have a look :)14:59
clarkbI think with k8s you probably don't want to share that cluster with zuul and other things? especially if testing untrusted code15:00
clarkbopenshift has a lot more isolation built in that makes that safer aiui15:00
Shrewsfelixgcb: easystack uses k8s, but they don't seem to participate in this channel, sadly. their last talk is here: https://www.youtube.com/watch?v=3AHRFORLLFE15:00
[GNU]clarkb, +1 +115:00
clarkbso giving out cluster admin to zuul isn't a huge deal as it should be a dedicated cluster anyway15:00
ofosostobiash, cool15:01
felixgcbclarkb: Hm I see that zuul calls these projects "untrusted projects", but in our case this will be company-internal projects written by our devs, not some codesnippets from the www15:02
felixgcbShrews: Ah cool, I'll check out their talk :) thanks!15:02
clarkbfelixgcb: I would advocate that you not treat unreviewed code much differently regardless of it coming from the internet or intenally. We all make mistakes and this gives you a nice layer of safety15:03
felixgcbclarkb: Hm that's an interesting take on unreviewed code...15:04
*** gtema has quit IRC15:15
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213415:16
*** hashar has quit IRC15:17
clarkbfelixgcb: part of the job of the machines is to help ensure these changes are safe. We lack that information while running the checks15:19
*** saneax has quit IRC15:20
openstackgerritMark Meyer proposed zuul/zuul master: Extend event reporting  https://review.opendev.org/66213415:49
fungifelixgcb: also, using "this will be company-internal projects written by our devs" as a reason to treat all repos as trusted implies you're okay with random internal devs compromising and/or bypassing the ci system at any time15:56
fungiit would be like saying you don't want to put passwords on your office network equipment because only employees connect through it15:56
*** michael-beaver has joined #zuul15:57
*** mattw4 has joined #zuul16:07
*** panda is now known as panda|off16:13
corvusfbo: i think the pagure driver is ready to merge after you fix up https://review.opendev.org/661316 and rebase, yeah?16:19
openstackgerritJames E. Blair proposed zuul/zuul master: WIP add repl  https://review.opendev.org/57996216:24
*** flepied has quit IRC16:25
openstackgerritJeremy Stanley proposed zuul/zuul-jobs master: [DNM] Test unittests and multinode with base-test  https://review.opendev.org/66399516:39
openstackgerritJames E. Blair proposed zuul/zuul master: Proposed spec: tenant-scoped admin web API  https://review.opendev.org/56232116:56
*** jpena is now known as jpena|off16:56
openstackgerritJames E. Blair proposed zuul/zuul master: Add opendev tarball jobs  https://review.opendev.org/66400617:12
*** felixgcb has quit IRC17:24
mattw4Hi Zuul team: can anyone tell me if I can tell Zuul to gather "full" ansible_facts from the test node, rather than the minimum? I'm missing ansible_interfaces, required by devstack setup in the minimum ansible_facts.17:53
mattw4i.e. gathering the minimum facts with ansible "ansible all -m setup -a 'gather_subset=!all'" produces output similar to that gathered by Zuul executor17:54
clarkbmattw4: the playbook can have a setup task to get them all iirc17:54
*** jamesmcarthur has quit IRC17:54
clarkbI want to say that is how it works for the opendev install. We do a smaller amount for most jobs to speed things up then jobs that need more opt into more17:55
mattw4clarkb: I can just instruct the playbook to run the 'full' ansible_facts setup?  I will see if I can figure that out.17:55
clarkbyes you should be able to17:56
clarkbwith a setup task17:56
pabelangerYup, that is correct17:59
mattw4thanks clarkb & pabelanger, testing now...18:06
*** gtema has joined #zuul18:11
mattw4clarkb, pabelanger: thanks again.  Added a "setup" role to the base pre.yaml and that provided the full set of ansible_facts!18:24
gtemaclarkb: I think we need to drop image checksum validation in the nodepool image upload, since after I really repaired it I again got confirmation it is not reliable18:25
gtematests in SDK are failing now and you can really see from the nodepool logs that the checksum returned is not the one we expect18:26
clarkbgtema: is the issue that glance doesn't calculate the sha as it goes? so there is a lag in reporting the checksum?18:26
gtemasee logs under http://logs.openstack.org/38/662738/1/check/nodepool-functional-py35-src/f236fc9/controller/logs/screen-nodepool-builder.txt.gz18:26
clarkbgtema: but also if the checksums are different doesn't that mean our images are different?18:26
clarkband maybe that should be a failure if glance can't write the same image down?18:27
gtemaI have no clue how it get's generated, but it is not the one of the image we upload18:27
clarkbgtema: maybe we can add a step to the job that goes and checks the checksum of the file on disk18:27
clarkbthat should aid in debugging18:27
gtemathis means we need download image18:27
clarkbany file should work I think18:28
gtemaand basically in the glance there is some method (I'm not the developer of it, but I know it exists), which does image transformation during upload18:28
gtemameaning checksum should not be really trusted18:28
clarkbwe just want to verify the same bits end up on both sides to verify that isn't failing (and that would put the bug in glance's checksum reporting)18:28
clarkbso while such a feature is good for easiers for simplicitly it should also be possible to verify an image as well18:29
clarkbI think we can have both things, but maybe that requires work in glance first18:29
gtemaagree18:29
gtemaso for the moment I will do only put a fat warning in the log, bug SDK should not fail unless we fix glance18:30
fungirosmaita or others in #openstack-glance may have suggestions18:30
corvusclarkb, fungi: can you +3 https://review.opendev.org/664006 ?  i did a thing there which i think should make that self-testing, even for the promote jobs.  that will let us see if all the tarballs.opendev.org stuff is working.18:50
clarkbI can look18:50
clarkbalso I should prep for zuul scheduler restart after lunch. Process for that is pull your repl change into local clone, pip3 install that, then restart?18:51
corvusclarkb: t18:51
fungithe nodepool functional failures are expected/known?18:52
corvusclarkb: i think pabelanger would like us to do a full system restart too, to get 2.8 on the executors18:52
corvusfbo: yes18:52
corvusfungi: ^18:52
fungiare these related to what gtema brought up?18:52
fungi(the image checksum mismatches)18:52
corvusoh, maybe they are not known to me18:52
gtemaI do not think. The patch is not yet merged, which enforces checksum verification18:53
clarkbya it was added wtih a flag you ahve to toggle18:53
clarkbso shouldn't affect nodepool18:53
*** armstrongs has joined #zuul18:53
corvusi think that job just needs to be rewritten18:54
fungithe build-javascript-content job seems to link its results to npm/html which dne18:54
corvusfungi: yep!  i didn't write that.18:55
fungiheh18:55
fungiyeah, seems to result in archiving an empty npm directory18:55
corvushrm, there should be a tarball somewhere18:58
corvusoh, ugh.18:59
corvusthat's the wrong job18:59
corvus(which is great, because it means that job does literally nothing)18:59
fungithe build-python-release job does seem to produce artifacts19:00
openstackgerritJames E. Blair proposed zuul/zuul master: Add opendev tarball jobs  https://review.opendev.org/66400619:02
corvusfungi, clarkb: okay, that's updated with a dependency ^19:02
*** armstrongs has quit IRC19:02
*** gtema has quit IRC19:08
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Store autohold requests in zookeeper  https://review.opendev.org/66111419:15
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Add autohold-info CLI command  https://review.opendev.org/66248719:15
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Record held node IDs with autohold request  https://review.opendev.org/66249819:15
openstackgerritDavid Shrewsbury proposed zuul/zuul master: WIP: Auto-delete expired autohold requests  https://review.opendev.org/66376219:15
openstackgerritMerged zuul/zuul master: Break long repo names to make them fit  https://review.opendev.org/66389919:16
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Add caching of autohold requests  https://review.opendev.org/66341219:18
Shrewssorry for the spam19:19
pabelangercorvus: clarkb: yah, it would be neat if we could do executors too19:22
pabelanger2.8.1 was released yesterday too19:22
*** bhavikdbavishi has joined #zuul19:33
Shrewscorvus: what are the incantations i need in a unit test in test_scheduler in order to trigger the code in _doBuildCompletedEvent(), assuming I'm using @simple_layout('layouts/autohold.yaml') for the test?19:43
Shrewsi was hoping a call to self.fake_gerrit.addFakeChange() would be enough, but apparently not19:44
corvusit should be -- that should happen for all builds19:45
corvusShrews: maybe you could point me at the not-working code and i can poke at it?19:45
Shrewscorvus: yeah, 1 sec... trying to test the hold request auto-delete stuff....19:45
openstackgerritDavid Shrewsbury proposed zuul/zuul master: WIP: Auto-delete expired autohold requests  https://review.opendev.org/66376219:46
Shrewscorvus: the new test in ^^^19:46
Shrewsyou may even have a better way to test that19:46
Shrewsbrb... moar coffee needed19:49
corvusShrews: ah i see the issue :)19:50
corvusShrews: left comments19:53
Shrewscorvus: ah, thx. it didn't work, so I'm gonna suspect a bug in my code at this point and go from there19:57
corvusShrews: i haven't traced it all through, but you may need another build run through the system to trigger the expired code path...20:03
smcginnisBack looking at getting updated third party CI instructions written down. Running into an odd one.20:03
smcginnisGot one deployment working, so tried to replicate it on a fresh install to capture more notes.20:04
smcginnisFirst one would trigger on upstream ci-sandbox changes, new one does not.20:04
corvussmcginnis: the new way is to just make an image and have everyone deploy that in production.  ;)20:04
smcginnisI notice a difference in the pipeline event processing, even though the definitions are the same.20:04
smcginniscorvus: That would be nice. :)20:05
smcginnisHere's what I get on the first one that works, followed by the second one that does not:20:05
smcginnismatched        <GerritEventFilter types: comment-added ignore_deletes: True event_approvals: Verified:1> in pipeline <IndependentPipelineManager thirdpartyci>20:05
smcginnisdoes not match <GerritEventFilter types: comment-added ignore_deletes: True event_approvals: Verified:1, username:zuul> in pipeline <IndependentPipelineManager thirdpartyci> because False20:05
smcginnisNew one has "event_approvals: Verified:1, username:zuul" but one that works does not mention zuul.20:06
smcginnisBut the exact same pipeline definition.20:06
smcginnisAnd new-comment Verified:1 is coming from the zuul user.20:06
clarkbsmcginnis: that looks like a gate pipeline? or are you wanting third party ci to not run until zuul passes it?20:06
*** jamesmcarthur has joined #zuul20:07
smcginnisclarkb: Correct. In Cinder we "recommend" not running until zuul has left +1 to reduce load. Though I think very few actually run that way.20:07
pabelangerIIRC, rdoproject does that20:07
clarkbsmcginnis: can you share your pipeline definition?20:07
pabelangerlet me find pipeline stanza20:08
corvussmcginnis: i'd start from the assumption that it is somehow not the same pipeline definition and try to figure out why that is.  that's a pretty straightforward repr of the filter that zuul creates out of a pipeline trigger.20:08
smcginnisclarkb: http://paste.openstack.org/show/752641/20:08
Shrewscorvus: oh, we process autoholds only on failures, so my req expiration code won't get hit unless a build fails.20:08
corvusor, if you don't really care that they're different and just want the second one to work, we can ignore that and go from there.20:08
smcginniscorvus: I guess I don't care too much, just want it to work, but I can do another stare and compare to see if somehow there was a copy paste error.20:09
Shrewscorvus: not sure how i feel about that, but that's really the only place to do that check currently20:09
corvusShrews: self.executor_server.failJob can help make a failed job20:09
corvussmcginnis: let's just roll forward then :)20:10
smcginnisIt feels like it has to be really close, so I will not be surprised if there is one character missing in a yaml file or something.20:11
*** jamesmcarthur has quit IRC20:12
clarkbneed to dedent the username20:12
corvussmcginnis: can you paste all of your scheduler logs from the time the gerrit event is received until it's done with it?20:12
clarkbusername is a field of the comment not the vote (at least how zuul is processing it)20:13
smcginnisGetting fresh logs...20:13
corvusclarkb: username is valid in either location20:14
clarkbcorvus: even in a trigger? I see we do it that way for requires20:14
smcginnisI couldn't find a detailed guide on options for that pipeline definition, so if there is a better way to define it so it is only triggered on zuul +1, I'm open to any suggestions.20:14
clarkb(I'm guessing it has to do with the structure of the trigger event from gerrit)20:14
corvusclarkb: yeah, we have it that way in our trigger20:15
smcginnisSomeone added this long ago: https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_trigger_my_CI_to_rerun_on_gerrit_comments.3F20:15
smcginnisTHat actually used require-approval, but based on last convo here that sounded wrong.20:15
corvussmcginnis: we have very detailed docs -- https://zuul-ci.org/docs/zuul/admin/drivers/gerrit.html#trigger-configuration20:15
pabelangersmcginnis: looks like we never migrated it to zuulv3, but https://github.com/rdo-infra/review.rdoproject.org-config/blob/eed6606ab1436012d89cbd9a81a9abb34290373c/zuul/upstream.yaml#L22 was v2 version of openstack-check-verified.20:16
pabelangermaybe be some help20:16
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Auto-delete expired autohold requests  https://review.opendev.org/66376220:16
Shrewscorvus: got it. thx for the help20:16
smcginnispabelanger: Thanks, maybe that does help.20:16
smcginnisShould the username be under approval or at the same level as event and approval?20:17
corvusclarkb: oh, our username is on require approval, not approval20:17
pabelangersmcginnis: and where we deleted, with new zuul user name20:17
smcginnisIn mine, https://github.com/rdo-infra/review.rdoproject.org-config/blob/eed6606ab1436012d89cbd9a81a9abb34290373c/zuul/upstream.yaml#L37 is indented20:17
pabelangerhttps://github.com/rdo-infra/review.rdoproject.org-config/commit/4f0733e0b7cd71d7d094d24fba26af20f275f8fb#diff-56448f4b4b65ff4e7b61a23290de1b96L3420:17
corvusclarkb: i think you might be right20:18
clarkbya and we document it that way too20:18
*** bhavikdbavishi has quit IRC20:19
pabelangeryah, line 72 in pb looks indented 1 too many20:19
corvussmcginnis: ^ so yeah, assuming you want to stick with 'approval' rather than 'require-approval' (which i think you do), you should dedent the username20:19
smcginniscorvus: Cool, test running right now.20:19
smcginniscorvus, clarkb, pabelanger: Thank you! That worked.20:20
smcginnisI still don't understand how my first setup was working right, but I'm not going to dwell on that right now.20:20
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Add autohold-info CLI command  https://review.opendev.org/66248720:22
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Record held node IDs with autohold request  https://review.opendev.org/66249820:22
openstackgerritDavid Shrewsbury proposed zuul/zuul master: Auto-delete expired autohold requests  https://review.opendev.org/66376220:22
openstackgerritDavid Shrewsbury proposed zuul/zuul master: WIP: Mark nodes as USED when deleting autohold  https://review.opendev.org/66406020:41
Shrewsmordred: that WIP ^^ is the last puzzle piece20:41
Shrewsand quite the puzzle it was20:42
Shrewsthough there is also the integration with the web admin spec stuff, but not worried about that right now20:47
evgenylA quick question on nodepool, when I configure my openstack provider, can I use the images that are already present in glance, instead of having a builder process doing the build and uploading the images?21:11
clarkbevgenyl: yes you can specify images to use instead21:11
evgenylclarkb: Do I need a builder process running in this case?21:12
clarkbevgenyl: https://zuul-ci.org/docs/nodepool/configuration.html#attr-providers.[openstack].cloud-images21:12
clarkbno you won't need a builder in that case21:12
evgenylclarkb: This is awesome, thank you!21:13
mattw4Hi Zuul team: this might not be the right forum, but can anyone tell me which role is supposed to clone devstack before role:orchestrate-devstack runs?21:19
mnasermattw4: zuul itself clones devstack afaik21:20
mnaserbecause it's listed as required-projects: in the job definition21:20
fungievgenyl: you will, however, need to be able to provide access credentials for zuul (rather ansible) to be able to authenticate to the instances booted from those images21:20
clarkbmnaser: correct, part of zuul's job is putting all the repos a job needs on disk in the test env21:20
mnaseri'm speaking about the general use case anyways21:20
clarkbfungi: nodepool too21:20
mattw4mnaser, clarkb : do I need move devstack into /opt/stack/devstack with another role?21:21
SpamapSIIRC the role that pushes it from zuul-executor -> nodes is prepare-workspace21:21
SpamapSmattw4:why not just use it where it is, {{ zuul.projects['openstack/devstack'].src_dir }}21:21
clarkbI think the zuulv3 native jobs do run devstack in place21:22
clarkbonly the legacy jobs do the moving around21:22
mattw4SpamapS, I figured that was where it would end up, but the run-devstack role seems to expect it there21:22
fungiclarkb: doesn't the job (or one of its parents, for example the base job) need the mirror-workspace-git-repos role to take care of getting that repo (and others) onto the remote node?21:22
clarkbfungi: its the one SpamapS pointed out21:23
clarkbfungi: iirc its documented as part of base job set up21:23
fungiahh, yeah, we were typing it simultaneously it seems21:23
evgenylfungi: Will specifying `key-name` in nodepool.yaml and matching `executor.private_key_file` in zuul.conf be sufficient to provide the access?21:23
fungievgenyl: as long as your cloud provider exposes those keys in such a way that the booted instances can consume them (for example from a metadata server or configdrive record)21:24
evgenylfungi: I see, thank you.21:24
clarkbmattw4: you are right that devstack_base_dir seems to default to /opt/stack21:24
fungievgenyl: so if your images have cloud-init or glean or something like that preinstalled then should work fine21:25
clarkbso maybe that was kept in the job conversion?21:25
clarkbthankfully we can look at jobs that have run to get more info21:25
mattw4clarkb: yeah, I figured Zuul would move devstack into the right place, but maybe I've misconfigured a variable?21:26
fungiclarkb: i think there's a role in devstack which copies the repos from the zuul-provided copies into the stack user home21:26
mattw4fungi: that's what I was expecting21:26
clarkbfungi: wow so we copy from /opt/ to /home/ then back again amazing21:26
fungihah21:26
clarkbmattw4: look in devstack's pre.yaml21:27
clarkbsetup-devstack-source-dirs is a role called there21:27
clarkbya that does it21:27
clarkbno wonder these jobs are so slow on rax nodes21:27
clarkb(/opt is a separate device there)21:28
fungiyeah, since /opt and /home are on separate devices there21:28
fungiless of an issue on providers with a coalesced rootfs21:28
fungisince the data isn't shuffled around, just a bunch of hardlinks added21:28
mattw4clarkb: I've got devstack source in /root/src/opendev.org/openstack/devstack, but not in /opt/stack/devstack.  Wonder what I did :/21:28
clarkbmattw4: looks like your jobs use the root user (not zuul user) and you aren't running the devstack pre.yaml?21:29
clarkbor the find in that setup playbook isn't finding the files due to the paths (though they are relative so that should work despite the path chagne I think)21:30
mattw4clarkb: most of the Ansible seems to be as root, where can I specify that the job user as stack?21:30
clarkbmattw4: in our case we run the jobs as the 'zuul' user21:30
mattw4clarkb, I think it's the setup playbook not finding them21:30
clarkbmattw4: that is a setting of nodepool and zuul I think21:30
clarkbnodepool sets that and passes it to zuul21:31
mattw4clarkb: yeah, I should specify the zuul user in nodepool21:31
clarkbhttps://zuul-ci.org/docs/nodepool/configuration.html#attr-diskimages.username21:31
clarkbif it is a file path issue that may fix it. Though I don't think it is a filepath issue. Can you look in your logs for when that role runs to see what it is doing?21:32
mattw4clarkb: here's the setup-devstack-dirs role running under devstack/pre.yaml: http://paste.openstack.org/show/752643/21:34
mattw4so I have all the project dirs including nova, neutron, placement, swift, etc. in /opt/stack, but no devstack there :/21:36
*** rlandy|ruck has quit IRC21:37
clarkbmattw4: you might need to add devstack as a required project if it isn't already?21:38
mattw4clarkb, that makes sense - lemme check21:38
mattw4clarkb, it's a required project in the job definition. Should that be a list of all the projects that the devstack job will setup?21:40
clarkbya its all the source repos devstack needs to function21:41
clarkbmaybe check permissions? could be the copy is failing due to that?21:45
fungii would hope the copy failing would show up in the console log21:48
mattw4fungi: I pasted the role activity above.  It seems to work just fine then moves on21:49
clarkbya its almost like devstack isn't in the find list21:50
clarkbwhich might happen due to perms?21:50
fungioh, maybe if it's not readable21:50
mattw4I had devstack in my required-projects list and in tenant config.  That should be it, right?  The devstack dir i nsrc/opendev is owned by root (as are the other there), and the repos in /opt/stack are all owned by stack.21:51
*** pcaruana has quit IRC21:51
*** EvilienM is now known as EmilienM22:42
fungibaffled by this unit test result: http://logs.openstack.org/70/662870/3/check/tox-py36/74aaa81/job-output.txt.gz#_2019-06-05_17_54_38_38809523:02
fungii'm guessing something about the change is causing some sort of infinite looping/recursion in a test?23:02
fungi(this is for the password lookup plugin addition)23:03
fungithe tests i add in 662870 aren't any of the one which ran immediately prior to the exception being raised in subunit23:05
fungialternatively, has our debug output for unit tests simply outgrown subunit's capacity?23:06
fungialso, i add 5 plugin tests... are those perhaps far too expensive to be so liberal with?23:06
fungi(i notice we're missing a bunch of coverage for the previously-allowed plugins)23:07
clarkbI cant get it to load currently but subunit does have a buffer limit23:10
clarkb(and it isnt huge)23:10
*** michael-beaver has quit IRC23:24
*** tjgresha has joined #zuul23:29

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