Friday, 2018-11-16

*** jesusaur has quit IRC00:00
*** jesusaur has joined #zuul00:11
manjeetsianw, still there one more question https://zuul-ci.org/docs/zuul/admin/nodepool_static.html is host-key a private key for which public should be node authorized_keys in static_node ?00:51
manjeetsshould be added to  authorized_keys in static_node that;s being added to nodepool ?00:52
ianwmanjeets: host-key will be the host key of the server connecting to00:53
ianwzuul will authenticate as the zuul user (or whatever you're running as) so the authorized_keys you want on the static node is the public key of the zuul user's private key00:54
ianwdoes that make sense?00:54
manjeetsianw, zuul user is actually on static target node we add here https://zuul-ci.org/docs/zuul/admin/nodepool_static.html?00:57
manjeetsit login as username:zuul or whatever i give to ip given in name: field ?00:58
manjeetsit logs into static node from somewhere in one of the containers ? so public key of privatekey for that container should be added ?00:59
ianwmanjeets: yes, the zuul executor logs in to the static node, so it's public key needs to be in the authorized_keys of the static node01:00
manjeetswhat is this host-key in https://zuul-ci.org/docs/zuul/admin/nodepool_static.html ? sorry i still don't get it ?01:01
ianwmanjeets: that's the, well host key of the remote host01:05
ianwyou know when you log into a new machine, and it prompts you "do you want to trust this" and gives you the fingerprint01:05
ianwthat01:05
manjeetsohk got it thanks !01:06
manjeetsI screwed previous run by thinking its sorta public key01:06
manjeetsdumb I01:06
manjeetsthanks ianw01:06
*** rlandy is now known as rlandy|biab01:09
*** openstackgerrit has quit IRC02:22
*** rlandy|biab is now known as rlandy02:45
*** rlandy has quit IRC02:45
*** bhavikdbavishi has joined #zuul04:10
*** bhavikdbavishi1 has joined #zuul04:22
*** bhavikdbavishi has quit IRC04:23
*** bhavikdbavishi1 is now known as bhavikdbavishi04:23
*** bhavikdbavishi has joined #zuul04:24
*** chandankumar has joined #zuul04:33
*** bhavikdbavishi has quit IRC04:34
*** bhavikdbavishi has joined #zuul04:35
*** chandankumar is now known as chkumar|ruck04:36
*** bhavikdbavishi1 has joined #zuul04:54
*** bhavikdbavishi has quit IRC04:54
*** bhavikdbavishi1 is now known as bhavikdbavishi04:54
*** bhavikdbavishi has quit IRC04:59
*** bjackman has joined #zuul05:09
*** ianychoi_ has joined #zuul06:30
*** ianychoi has quit IRC06:33
*** bhavikdbavishi has joined #zuul06:55
*** bhavikdbavishi has quit IRC07:58
*** quiquell has joined #zuul08:19
quiquellGood morning08:19
quiquellfungi: You there ?08:19
fungiquiquell: not really, packing up and about to go catch a bus to the airport08:21
quiquellfungi: ack, next week then, have a good trip !!!08:22
*** openstackgerrit has joined #zuul08:28
openstackgerritQuique Llorente proposed openstack-infra/zuul master: Setup model before connection  https://review.openstack.org/61848408:28
*** pcaruana has joined #zuul08:39
*** bhavikdbavishi has joined #zuul08:41
*** jpena|off is now known as jpena08:45
*** bhavikdbavishi has quit IRC08:51
*** hashar has joined #zuul08:53
*** panda|rover|off is now known as panda09:03
*** chkumar|ruck has quit IRC09:04
*** bjackman has quit IRC09:13
*** chandankumar has joined #zuul09:15
*** chandankumar is now known as chkumar|ruck09:27
*** ParsectiX has joined #zuul09:35
*** ParsectiX has quit IRC09:37
*** bjackman has joined #zuul09:38
*** panda is now known as panda|rover09:39
*** ParsectiX has joined #zuul09:49
*** openstackgerrit has quit IRC09:52
*** dkehn has quit IRC09:52
*** dkehn_ has joined #zuul09:52
*** goern has quit IRC09:53
*** lennyb has quit IRC09:53
*** lennyb has joined #zuul09:54
*** gtema has joined #zuul09:59
*** ParsectiX has quit IRC10:00
*** goern has joined #zuul10:05
fungiquiquell: i have a few minutes now that i'm through airport security. what was your question?10:10
quiquellfungi: Just checking ci of the patch about makedirs .ssh10:11
quiquellfungi: I think the failure there is not related, but don't know for sure10:11
quiquellfungi: At gerritconfig.log "Invalid SSH Key\n" adding admin ssh key10:12
quiquellhttp://logs.openstack.org/84/617984/6/check/zuul-quick-start/4fe60cf/container_logs/gerritconfig.log10:12
quiquellfungi: but the change is at merger.py I think it's not run there10:12
quiquellfungi: but maybe it mess up the .ssh dir10:12
fungiquiquell: yes, i don't think they're related either based on which job was impacted, but i didn't have an opportunity to dig into the logs from the failure10:12
fungiquiquell: i also just noticed corvus pushed up basically the same change two days ago https://review.openstack.org/61795510:15
quiquellfungi: Then we just need to merge that, I also refactor working_root stuff10:16
fungiwhich i've approved now, but i have a feeling it's going to get a verify -2 for failing quickstart job in the gate10:16
fungistarting to dig into what has regressed that job now10:17
quiquellfungi: The difference with corvus is the working_dir, corvus's is passing10:17
quiquellworking_root I mean10:17
*** ParsectiX has joined #zuul10:18
fungiahh, true10:18
*** ParsectiX has quit IRC10:23
fungithe failure looks like zuul-web is returning a 404 not found for requests to /a/accounts/zuul/sshkeys10:33
fungiyeah, as suspected, 617955 is failing in the gate pipeline on the same job10:42
fungiin the same way10:43
fungiso this is likely a regression which has cropped up in the past two days since that change passed in check10:44
fungibut i'm about to board my flight now so need to disconnect. i can try to pick the shovel up again later if nobody else gets a chance10:45
*** electrofelix has joined #zuul10:46
*** ParsectiX has joined #zuul10:49
fbohi, is there a way to tell Zuul to read variables from some yml files via the job definition ? I have some variables files I want to expose to my job and the files are in a required-project and I don't want to duplicate using job.vars.11:11
clarkbfbo you can use include_vars11:14
fboclarkb: but include_vars is executed from the executor and seems bubblewrap deny the access to the vars file I expect to read.11:18
clarkbhrm I thought we usee it in places for distro specific flags11:20
clarkbbut maybe I am mistaken11:20
fboWell I need to check again my include_vars path might be wrong11:21
*** hashar has quit IRC11:32
quiquellfungi: ahh so it's regression11:42
*** dkehn_ has quit IRC11:44
*** gtema has quit IRC11:48
*** quiquell is now known as quiquell|brb11:53
quiquell|brbclarkb: Do you know what options at zuul can help up speed thinks up regarding cloning repo and the like ?11:56
quiquell|brbclarkb: Feels like recloning everythign after consequitive changes in the same review11:56
*** ParsectiX has quit IRC12:10
*** EmilienM is now known as EvilienM12:24
*** quiquell|brb is now known as quiquell12:25
*** jpena is now known as jpena|lunch12:29
*** gtema has joined #zuul12:32
*** hashar has joined #zuul12:42
tobiashfbo: include_vars should work if you use a safe path12:48
fbotobiash: yes I figured out my mistake, works now :)12:50
tobiash:)12:50
tobiashquiquell: what do you mean with recloning? The executor clones from a local cache dir12:51
quiquelltobiash: I don't really know what I mean exactly :-)12:52
tobiash(using hard links if the cached repo and workspace are on the same filesystem)12:52
quiquelltobiash: will do some investigations first to come with more specifics12:52
tobiashOk12:52
quiquelltobiash: How is this hardlink thing ? do we have a role or something to do that already ?12:53
*** bjackman has quit IRC12:55
*** mordred has quit IRC12:55
*** chkumar|ruck has quit IRC12:56
*** ParsectiX has joined #zuul13:11
quiquelltobiash: The 'console.log' zuul streams is from executor ?13:23
*** quiquell is now known as quiquell|lunch13:32
*** quiquell|lunch is now known as quiquell13:35
*** jpena|lunch is now known as jpena13:37
quiquellI have the zuul executor running at docker and it get stuck I see playbook progressing in the node but not the executor13:42
*** rlandy has joined #zuul13:46
*** quiquell is now known as quiquell|lunch14:09
*** ParsectiX has quit IRC14:13
fungiquiquell|lunch: the "hard linking" in question is simply git clone's default behavior if you give it a source file path instead of a remote url and the destination doesn't traverse mountpoints from the source14:16
fungiit creates hardlinks for all the objects in the tree rather than copying them into new files14:16
quiquell|lunchfungi: nice! will try thanks14:18
*** ParsectiX has joined #zuul14:19
fungiyeah, in theory it's nearly instantaneous since it only has to write out the additional inode entries14:28
fungier, handles for them i mean14:28
quiquell|lunchfungi: That's going to speed thinks up, the other issue I face is executor get stuck14:29
quiquell|lunchfungi: I see the playbook finishing correctly at the node14:29
quiquell|lunchfungi: but console.log stream is stuck and also job-output.txt at the bubblewrap thingy14:29
quiquell|lunchfungi: And one of the task in the middle (long one)14:29
quiquell|lunchMaybe I have to configure some timeout14:30
*** quiquell|lunch is now known as quiquell14:30
*** toabctl has quit IRC14:31
Diabelkocorvus: is there any common place where Zuul publications/presentations land?14:33
DiabelkoI faintly recall someone mentioning something like it on the mailing list, but I do not remember the conclusion at all14:34
*** toabctl has joined #zuul14:34
fungii wonder if we could/should commit them to the zuul-website-media repo14:35
quiquellfungi: But the clone stuff is executed by zuul code and it does not clone from cached repo14:38
*** ianychoi_ is now known as ianychoi14:41
fungiare you talking about on the executor or on a job node?14:43
fungii think on the executor it does have to copy from the cache instead of linking, for safety reasons, but i'm not in a position to confirm that right now14:45
quiquellfungi: in node I think14:46
fungithe executor needs to create the repository state and then push it onto the job node. zuul itself doesn't perform any cloning i'm aware of on job nodes (though your job definitions may do so)14:47
quiquellfungi: ok, will investigate14:48
fungiquiquell: the role that does the bit i was describing to push the workspace copy onto job nodes is https://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/mirror-workspace-git-repos/tasks/main.yaml14:52
fungier, i mean https://git.zuul-ci.org/cgit/zuul-jobs/tree/roles/mirror-workspace-git-repos/tasks/main.yaml14:53
quiquellfungi: thanks so much, want to fix the stuck issue first14:58
*** ParsectiX has quit IRC15:17
*** ParsectiX has joined #zuul15:18
*** ParsectiX has quit IRC15:23
*** ParsectiX has joined #zuul15:26
quiquellfungi: Damn I don't know why my executor get stuck, I see tasks running at node15:35
quiquellfungi: but executor is stuck at one of them like forever15:35
quiquellfungi: Could be related to socket to run shell at cloud ?15:36
quiquellfungi: Maybe I have some timeouts at my cloud that closes the socket15:37
quiquellfungi: after some inactivity15:37
*** pcaruana has quit IRC15:56
rlandyhello ... at what point does zuul apply zuul.change (ref) to the repos on the nodes? https://github.com/openstack-infra/zuul-jobs/blob/master/roles/mirror-workspace-git-repos/tasks/main.yaml#L35 looks like it checks out master16:00
*** ParsectiX has quit IRC16:10
*** quiquell is now known as quiquell|off16:13
*** j^2 has joined #zuul16:17
rlandyfungi: ^^ hi - can you point me to where the zuul change gets applied?16:25
*** hashar has quit IRC16:32
*** hashar has joined #zuul16:34
*** openstackgerrit has joined #zuul16:37
openstackgerritMarkus Hosch proposed openstack-infra/zuul master: Allow to select the merge method in GitHub  https://review.openstack.org/61794916:37
*** electrofelix has quit IRC16:56
*** mordred has joined #zuul17:20
SpamapSquiquell|off: if you could look at what's running under the executor process... maybe 'docker exec zuul-executor-container ps auxfw' ... it should be running bwrap -> ansible-playbook17:20
SpamapSrlandy: zuul prepares all projects' git trees in the executor17:21
SpamapSrlandy: and then https://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/mirror-workspace-git-repos/tasks/main.yaml sends the prepared git workspaces to job nodes17:22
rlandySpamapS: ok - this task? https://git.openstack.org/cgit/openstack-infra/zuul-jobs/tree/roles/mirror-workspace-git-repos/tasks/main.yaml#n917:24
SpamapSrlandy: right, that's what copies the git states as they are from executor -> nodes17:25
SpamapSthe git state is updated inside the executor here.... https://github.com/openstack-infra/zuul/blob/master/zuul/executor/server.py#L2285-L230317:26
SpamapSand most of the deep stuff happens in updateRepo in the merger.. https://github.com/openstack-infra/zuul/blob/master/zuul/merger/merger.py#L511-L56317:28
rlandySpamapS: hmmm ... I am following a local run and I see u'checkout': u'master' on that step - not the change branch I was looking for17:28
SpamapSSo, if the change is stacked on top of master, that's normal.17:29
SpamapSYou'll checkout master, and then merge the change on top of it.17:29
SpamapShttps://github.com/openstack-infra/zuul/blob/master/zuul/merger/merger.py#L60217:29
SpamapSIn fact you won't realy "merge" at that stage, you'll just checkout the ref.17:30
SpamapSthe merge happens at a different point17:30
rlandyok - let me rerun and I'll watch again - thank you17:31
SpamapSrlandy: anyway, when the scheduler enqueues your change, it adds change info to the job, and the executor will definitely only run the job on the change that is referred to. I've never seen that not work as expected.17:31
SpamapSIt's worth noting that the way a job is triggered, what type of pipeline it is, and a few other things, all will affect what git states get sent out.17:32
SpamapSLike, if you trigger on a commit, not a change (for instance, in a post-merge pipeline), that won't have a zuul.change.17:33
SpamapSOr if you are in a 'dependent' pipeline, there may be multiple changes merged before yours.17:33
SpamapSAnyway, just to say: please don't hesitate to ask here if you're not sure what you're seeing. There are a lot of factors.17:33
*** gtema has quit IRC17:35
*** jpena is now known as jpena|off17:46
*** quiquell|off has quit IRC17:51
*** hashar has quit IRC17:53
*** ParsectiX has joined #zuul17:58
rlandySpamapS: thanks - that info was very helpful18:03
rlandyI see the ref now ...18:05
rlandy2018-11-16 00:28:10.956994 | secondary -> localhost | To git+ssh://zuul@198.72.124.122//home/zuul/src/git.openstack.org/openstack-infra/tripleo-ci18:05
rlandy2018-11-16 00:28:10.957428 | secondary -> localhost |    803a036..ce9ab51  master -> master18:05
*** ParsectiX has quit IRC18:14
manjeetshi guys, I'm trying to locate logs for nodepool services (logs like if executor ever sshed to machine allocated from nodepool) etc, I'm trying to run a job on static baremetal machine bu using ip and username etc. but dont see any error happen on where all the zuul services were executed, but I get NODE_FAILURE on job18:29
manjeetsso where exactly in examples_logs container I can get nodepool specific logs (like was the machine ever got allocated) or ssh success etc18:30
SpamapSmanjeets: nodepool's logs are usually configured with a logging.conf... are you using the docker compose quick start?18:31
manjeetsSpamapS, yes using docker compose18:31
*** rfolco has quit IRC18:31
SpamapSmanjeets: ok, the container that it spins up for "logs" is for the job logs, not zuul and nodepool component logs18:33
manjeetsohk but where can I find nodepool, zuul logs, Its streaming on machine I'm running but hard to locate error from there like NODE_FAILURE18:34
SpamapSmanjeets: did you try just 'docker logs launcher' ?18:35
manjeetsSpamapS, you mean zuul/nodepool-launcher ?18:36
SpamapSoh, right18:36
* SpamapS hasn't used it, I'm spinning it up for the first time right now actually ;)18:36
manjeetsSpamapS, I found some logs for nodepool launcher18:39
manjeetsthanks !18:39
SpamapSnp18:40
manjeetsSpamapS, from logs I figured out there was host-key mismatch error, I think it could be bug in upstream the way nodepool set up things19:31
manjeetsso I changed the host-key in nodepool.yaml and kill docker-compose run and re ran docker-compose up19:32
manjeetssince host-key for static node was right it was still matching with wrong key (I guess one stored in db or somewhere which older')19:32
manjeetsthen I killed all the containers, and images and rebuilt then error was gone19:33
SpamapSmanjeets: I haven't done much with static nodes, but that sounds plausible. If nothing else it may be confusing.19:38
*** rlandy has quit IRC20:47
*** panda|rover is now known as panda|rover|off21:03
*** goern has quit IRC21:17
*** j^2 has quit IRC21:18
manjeetsHi SpamapS quick question on ssh private key path in executor config section in zuul.conf21:43
manjeetsso private_key_path here is private key in executor container whose public key should be added to static node (added for jobs) ?)21:44
SpamapSmanjeets: correct21:45
manjeetsSpamapS, after lots of error I was able to use a static baremetal node and execute a sample command as part of test using that pipeline22:14
manjeetsits cool ! thanks for you help22:14
SpamapSmanjeets: congrats!22:43
*** EvilienM is now known as EmilienM22:55

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