Monday, 2020-11-23

*** evrardjp has quit IRC00:05
*** tosky has quit IRC00:06
*** evrardjp has joined #zuul00:15
*** ikhan has quit IRC00:16
-openstackstatus- NOTICE: Our Gerrit upgrade maintenance has concluded successfully; please see the maintenance wrap-up announcement for additional details: http://lists.opendev.org/pipermail/service-announce/2020-November/000014.html00:55
*** hamalq has joined #zuul01:32
*** hamalq has quit IRC01:37
*** zenkuro has quit IRC01:46
*** bhavikdbavishi has joined #zuul03:00
*** bhavikdbavishi1 has joined #zuul03:31
*** bhavikdbavishi has quit IRC03:33
*** bhavikdbavishi1 is now known as bhavikdbavishi03:33
*** hamalq has joined #zuul03:33
*** hamalq has quit IRC03:37
*** bhavikdbavishi has quit IRC04:23
*** bhavikdbavishi has joined #zuul04:24
*** evrardjp has quit IRC05:33
*** evrardjp has joined #zuul05:33
*** jfoufas1 has joined #zuul05:39
*** bhavikdbavishi1 has joined #zuul05:57
*** bhavikdbavishi has quit IRC05:59
*** bhavikdbavishi1 is now known as bhavikdbavishi05:59
*** openstackgerrit has joined #zuul06:17
openstackgerritMerged zuul/zuul master: web: store status filter in the location hash  https://review.opendev.org/c/zuul/zuul/+/75996906:17
*** danpawlik has quit IRC06:24
*** danpawlik has joined #zuul06:25
*** saneax has joined #zuul06:40
*** bhavikdbavishi has quit IRC06:54
*** saneax has quit IRC06:55
*** mach1na has joined #zuul06:58
*** mach1na has quit IRC07:02
*** iurygregory has joined #zuul07:06
*** mach1na has joined #zuul07:08
*** mach1na has quit IRC07:13
*** mach1na has joined #zuul07:19
*** bhavikdbavishi has joined #zuul07:29
*** rpittau|afk is now known as rpittau07:29
*** bhavikdbavishi1 has joined #zuul07:32
*** bhavikdbavishi has quit IRC07:34
*** bhavikdbavishi1 is now known as bhavikdbavishi07:34
*** saneax has joined #zuul07:55
*** jcapitao has joined #zuul08:05
*** tosky has joined #zuul08:38
*** holser has joined #zuul08:53
*** jpena|off is now known as jpena08:54
openstackgerritSimon Westphahl proposed zuul/zuul master: Prepare Zookeeper for scale-out scheduler  https://review.opendev.org/c/zuul/zuul/+/71726909:02
openstackgerritSimon Westphahl proposed zuul/zuul master: Mandatory Zookeeper connection for ZuulWeb in tests  https://review.opendev.org/c/zuul/zuul/+/72125409:02
openstackgerritSimon Westphahl proposed zuul/zuul master: Merge Zookeeper connection methods  https://review.opendev.org/c/zuul/zuul/+/75436009:02
openstackgerritSimon Westphahl proposed zuul/zuul master: Connect merger to Zookeeper  https://review.opendev.org/c/zuul/zuul/+/71622109:02
openstackgerritSimon Westphahl proposed zuul/zuul master: Connect fingergw to Zookeeper  https://review.opendev.org/c/zuul/zuul/+/71687509:02
openstackgerritSimon Westphahl proposed zuul/zuul master: Connect executor to Zookeeper  https://review.opendev.org/c/zuul/zuul/+/71626209:03
openstackgerritSimon Westphahl proposed zuul/zuul master: Improve typings in context of 744416  https://review.opendev.org/c/zuul/zuul/+/75357809:03
openstackgerritSimon Westphahl proposed zuul/zuul master: Make Zookeeper mandatory for Scheduler  https://review.opendev.org/c/zuul/zuul/+/75671609:03
openstackgerritSimon Westphahl proposed zuul/zuul master: Make ConnectionRegistry mandatory for Scheduler  https://review.opendev.org/c/zuul/zuul/+/75709509:03
openstackgerritSimon Westphahl proposed zuul/zuul master: Improve typings in context of 756716 and 757095  https://review.opendev.org/c/zuul/zuul/+/75714809:03
*** zenkuro has joined #zuul09:03
openstackgerritSimon Westphahl proposed zuul/zuul master: Instantiate executor client, merger, nodepool and app within Scheduler  https://review.opendev.org/c/zuul/zuul/+/75714909:03
openstackgerritSimon Westphahl proposed zuul/zuul master: Improve typings in context of 756304  https://review.opendev.org/c/zuul/zuul/+/75709709:03
openstackgerritSimon Westphahl proposed zuul/zuul master: Driver event ingestion  https://review.opendev.org/c/zuul/zuul/+/71729909:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Component Registry in ZooKeeper  https://review.opendev.org/c/zuul/zuul/+/75918709:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Move management and result events to model  https://review.opendev.org/c/zuul/zuul/+/76116309:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Allow (de-)serialization of management events  https://review.opendev.org/c/zuul/zuul/+/76116409:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Allow (de-)serialization of result events  https://review.opendev.org/c/zuul/zuul/+/76116509:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Add and fix fields in driver trigger event models  https://review.opendev.org/c/zuul/zuul/+/76116609:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Allow (de-)serialization of trigger events  https://review.opendev.org/c/zuul/zuul/+/76116709:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Interface to get a driver's trigger event class  https://review.opendev.org/c/zuul/zuul/+/76116809:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Clear list of Zookeeper connections after tests  https://review.opendev.org/c/zuul/zuul/+/76116909:04
openstackgerritSimon Westphahl proposed zuul/zuul master: Implementation of Zookeeper backed event queues  https://review.opendev.org/c/zuul/zuul/+/76117009:05
*** nils has joined #zuul09:11
*** arxcruz is now known as arxcruz|ruck09:19
*** arxcruz|ruck is now known as arxcruz|rover09:19
*** hamalq has joined #zuul09:36
*** hamalq has quit IRC09:40
*** mach1na has quit IRC09:58
openstackgerritSorin Sbârnea proposed zuul/zuul master: Improve summary build layout  https://review.opendev.org/c/zuul/zuul/+/76333310:00
*** wuchunyang has joined #zuul10:18
*** holser has quit IRC10:20
*** wuchunyang has quit IRC10:22
*** hashar has joined #zuul10:27
*** zenkuro has quit IRC10:30
*** zenkuro has joined #zuul10:31
*** mordred has quit IRC10:34
*** Eighth_Doctor has quit IRC10:34
*** iurygregory has quit IRC10:39
*** mordred has joined #zuul10:42
*** jpena is now known as jpena|off10:49
*** jpena|off is now known as jpena10:56
*** masterpe has joined #zuul11:00
*** Eighth_Doctor has joined #zuul11:00
*** wuchunyang has joined #zuul11:04
*** zenkuro has quit IRC11:06
*** zenkuro has joined #zuul11:07
*** holser has joined #zuul11:14
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add option to install kubernetes with kind  https://review.opendev.org/c/zuul/zuul-jobs/+/74093511:20
*** bhavikdbavishi has quit IRC11:28
*** mach1na has joined #zuul11:32
*** hamalq has joined #zuul11:36
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add option to install kubernetes with kind  https://review.opendev.org/c/zuul/zuul-jobs/+/74093511:37
*** saneax has quit IRC11:39
*** hamalq has quit IRC11:41
*** rfolco has joined #zuul11:46
*** rfolco is now known as rfolco|ruck11:47
*** jcapitao is now known as jcapitao_lunch11:49
*** bhavikdbavishi has joined #zuul11:53
*** iurygregory has joined #zuul11:58
*** wuchunyang has quit IRC12:05
*** mach1na has quit IRC12:07
*** wuchunyang has joined #zuul12:09
*** zenkuro has quit IRC12:10
*** zenkuro has joined #zuul12:10
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Add option to install kubernetes with kind  https://review.opendev.org/c/zuul/zuul-jobs/+/74093512:14
*** wuchunyang has quit IRC12:14
*** saneax has joined #zuul12:24
*** jpena is now known as jpena|lunch12:35
*** jcapitao_lunch is now known as jcapitao12:52
*** rlandy has joined #zuul12:56
*** mach1na has joined #zuul12:58
*** saneax has quit IRC13:15
*** jpena|lunch is now known as jpena13:31
*** rlandy is now known as rlandy|PTO13:31
openstackgerritSimon Westphahl proposed zuul/zuul master: Driver event ingestion  https://review.opendev.org/c/zuul/zuul/+/71729913:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Component Registry in ZooKeeper  https://review.opendev.org/c/zuul/zuul/+/75918713:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Move management and result events to model  https://review.opendev.org/c/zuul/zuul/+/76116313:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Allow (de-)serialization of management events  https://review.opendev.org/c/zuul/zuul/+/76116413:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Allow (de-)serialization of result events  https://review.opendev.org/c/zuul/zuul/+/76116513:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Add and fix fields in driver trigger event models  https://review.opendev.org/c/zuul/zuul/+/76116613:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Allow (de-)serialization of trigger events  https://review.opendev.org/c/zuul/zuul/+/76116713:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Interface to get a driver's trigger event class  https://review.opendev.org/c/zuul/zuul/+/76116813:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Clear list of Zookeeper connections after tests  https://review.opendev.org/c/zuul/zuul/+/76116913:37
*** ikhan has joined #zuul13:37
*** hamalq has joined #zuul13:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Increase default test wait timeout to 120s  https://review.opendev.org/c/zuul/zuul/+/76375413:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Implementation of Zookeeper backed event queues  https://review.opendev.org/c/zuul/zuul/+/76117013:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Implementation of Zookeeper event watcher  https://review.opendev.org/c/zuul/zuul/+/76117113:37
openstackgerritSimon Westphahl proposed zuul/zuul master: Switch to Zookeeper backed trigger event queues  https://review.opendev.org/c/zuul/zuul/+/76117213:38
openstackgerritSimon Westphahl proposed zuul/zuul master: Switch to Zookeeper backed management event queues  https://review.opendev.org/c/zuul/zuul/+/76173813:38
openstackgerritSimon Westphahl proposed zuul/zuul master: Use logical timestamp to detect outdated changes  https://review.opendev.org/c/zuul/zuul/+/76375513:38
*** jfoufas1 has quit IRC13:39
*** bhavikdbavishi has quit IRC13:41
*** hamalq has quit IRC13:42
*** jfoufas1 has joined #zuul14:24
*** rpittau is now known as rpittau|brb14:36
*** Goneri has joined #zuul14:55
*** rpittau|brb is now known as rpittau15:01
corvuszuul-maint: fyi i'm on vacation this week15:12
zbrcorvus: enjoy it!15:13
fungithanks for the heads up!15:20
*** hamalq has joined #zuul15:38
*** hamalq has quit IRC15:42
*** ikhan has quit IRC16:00
*** mach1na has quit IRC16:27
*** EmilienM has quit IRC16:31
*** EmilienM has joined #zuul16:33
*** y2kenny has joined #zuul16:39
y2kennyHi, I have been debugging a job that seems to stuck in a retry loop.  According to the scheduler log, the executor keep saying "Build complete, result None" while other jobs return "Build complete, result SUCCESS".  What determines if the result is SUCCESS or None?16:42
clarkby2kenny: I think a none result happens if the job loses network connectivity16:43
clarkbthats the signal upstream in the scheduler that it should be retried16:43
clarkby2kenny: in your executor logs look for the exit codes from ansible for that job. I think exit code 4 is ansible's indication of a network issue16:43
y2kennyclarkb: this should be something else because it's very repeatable.  It's a particular job that I keep getting retry.16:44
zbrfungi: i implemented last remarkes on the summary UI one: https://review.opendev.org/c/zuul/zuul/+/76333316:44
y2kennyclarkb: this is after I refactor the job a bit to inherit another job to get around the security fix for the executor.16:45
clarkby2kenny: we've seen networking issues if the job kills networking somehow or crashes the host. I would start with the executor logs and work back from there though to see what the executor is saying when the job completes16:45
y2kennyclarkb: ok... I will take a look at the executor16:45
y2kennyclarkb: um... the executor looks ok (I am tracing the build ID of the result None.)  Is the 'result' value related zuul_return at all?16:53
clarkby2kenny: no zuul_return is for internal data structure passing and separate from the build result16:53
clarkby2kenny: do all of the ansible processes exit 0? the executor should log that at the end of each play iirc16:53
y2kennyclarkb: From tracing the build ID, the last log entry I see is "Job execution took: 919.726 seconds"16:55
clarkby2kenny: should be up from that but probably not very far16:55
y2kennyclarkb: unless the entry is not key to the same job ID, I don't see anything like that.  The one previous entry for the same job is "Checking out .... branch... "16:57
clarkby2kenny: do you log at debug level?16:57
y2kennyclarkb: damn... I might have turned that off.16:58
y2kennyok... I will try again16:58
*** hamalq has joined #zuul17:01
*** rpittau is now known as rpittau|afk17:03
*** nils has quit IRC17:14
*** y2kenny has quit IRC17:16
*** jcapitao has quit IRC17:16
*** hamalq has quit IRC17:43
*** hamalq has joined #zuul17:43
openstackgerritSorin Sbârnea proposed zuul/zuul-jobs master: Build sphinx with python3 instead  https://review.opendev.org/c/zuul/zuul-jobs/+/73592317:46
pabelangerI managed to bring a zuul-regsitry online over the weekend17:48
pabelangerI am curious how the pruge flag works, how often should I be running that?17:48
*** weshay|ruck is now known as weshay|interview17:57
*** wuchunyang has joined #zuul17:58
*** y2kenny has joined #zuul18:03
*** wuchunyang has quit IRC18:03
*** saneax has joined #zuul18:04
*** saneax has quit IRC18:05
*** saneax has joined #zuul18:07
y2kennyclarkb: ok I think I see what you were referring to (Ansible exit code: 4, Ansible complete, result RESULT_UNREACHABLE)18:09
y2kennyand that was because my artifact server was not reachable.  Thanks for the help!18:10
y2kenny(not able to store the output.)18:10
*** y2kenny44 has joined #zuul18:12
*** y2kenny has quit IRC18:15
*** y2kenny44 has quit IRC18:17
*** y2kenny has joined #zuul18:18
*** y2kenny has quit IRC18:22
*** jfoufas1 has quit IRC18:23
*** y2kenny has joined #zuul18:26
y2kennyclarkb: looking back at the web interface job console, I noticed a task appears to be "green"/OK even when the task is "unreachable:true".  I am not sure if this is a bug or by design.18:26
clarkby2kenny: my guess is that is a bug18:27
y2kennyI think I've seen yellow (changed), blue (skip), red (fail), green (ok)18:27
y2kennynot sure if there should be other color or if  reachable should group under fail18:27
*** jpena is now known as jpena|off18:34
*** saneax has joined #zuul18:43
pabelangerso, for pull-from-intermediate-registry role. Should we pull the image we plan to build? To try and get some of the already built layers?18:44
pabelangerIs that a thing when you run podman build18:44
openstackgerritJeremy Stanley proposed zuul/zuul-jobs master: Use Python 3.x with launchpadlib  https://review.opendev.org/c/zuul/zuul-jobs/+/76383419:25
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Switch to container-images for push-to-intermediate-registry  https://review.opendev.org/c/zuul/zuul-jobs/+/76383619:44
openstackgerritPaul Belanger proposed zuul/zuul-jobs master: Switch to container_images for push-to-intermediate-registry  https://review.opendev.org/c/zuul/zuul-jobs/+/76383619:44
pabelangerin zuul.a.c we don't want to use docker_images in zuul jobs, so ^ should allow us to use container_images19:45
pabelangerwhile not breaking other people19:46
pabelangertristanC: are you running zuul-registry in sf.io? Or do you know if rdo is19:48
pabelangernot sure how is point on rdo now for zuul19:48
tristanCpabelanger: rdo is using an openshift registry19:49
pabelangerk19:50
pabelangerwant to make sure nothing breaks for them19:50
tristanCpabelanger: and we have some jobs that can uses an intermediate registry here: https://softwarefactory-project.io/cgit/zuul-images-jobs/tree/playbooks/image/promote.yaml  , but the job can also works with the local container/storage instead19:52
pabelangertristanC: do you promote on quay.io ?19:53
pabelangerthat is the next job I plan to write19:53
tristanCpabelanger: yes, this promote job pushes to quay19:55
pabelangertristanC: how do you delete the existing tag? can that be done with podman cli?19:57
pabelangerlooking at promote zuul-job for docker, it is using curl to do it via their PAI19:57
pabelangerAPI*19:57
tristanCpabelanger: we only push the final image there, and we don't delete tags19:58
pabelangerk19:58
*** wuchunyang has joined #zuul19:59
*** hamalq has quit IRC20:01
tristanCpabelanger: the image has the buildset in the tag for testing, e.g.: https://softwarefactory-project.io/cgit/zuul-images-jobs/tree/playbooks/image/test.yaml#n2420:01
tristanCpabelanger: and before promotion it is tagged to latest, e.g.: https://softwarefactory-project.io/cgit/zuul-images-jobs/tree/playbooks/image/promote.yaml#n2920:02
-openstackstatus- NOTICE: The Gerrit service on review.opendev.org is being restarted quickly to troubleshoot an unexpected error condition, downtime should be less than 5 minutes20:02
pabelangertristanC: so, if I follow, in your promote pipeline you still build the image again?20:02
*** openstackgerrit has quit IRC20:02
pabelangerrather then, upload in gate pipeline?20:02
*** y2kenny has quit IRC20:02
tristanCpabelanger: the pipeline runs three jobs: 'build -> test -> promote'20:03
pabelangertristanC: for gate?20:04
*** wuchunyang has quit IRC20:04
tristanCpabelanger: yes20:05
tristanCor periodically to update the image20:05
pabelangerokay20:06
tristanCwe are also doing that with rpm, the idea is to not merge a change if the publication failed20:06
pabelangeryah, I'm unsure how you ensure the promote job works as expected if merge fails for some reason.20:07
pabelangerand main reason why zuul-jobs is setup for promote pipeline20:08
*** hamalq has joined #zuul20:13
*** jhesketh has quit IRC20:16
*** hamalq has quit IRC20:19
*** jhesketh has joined #zuul20:23
*** hamalq has joined #zuul21:01
*** weshay|interview is now known as weshay|ruck21:46
*** hamalq has quit IRC21:55
*** hamalq has joined #zuul21:56
*** openstackgerrit has joined #zuul21:58
openstackgerritJeremy Stanley proposed zuul/zuul-jobs master: Use Python 3.x with launchpadlib  https://review.opendev.org/c/zuul/zuul-jobs/+/76383421:58
openstackgerritJeremy Stanley proposed zuul/zuul-jobs master: Pin keystoneauth1 when using older Python  https://review.opendev.org/c/zuul/zuul-jobs/+/76386621:58
*** hamalq has quit IRC21:59
*** iurygregory has quit IRC22:05
*** iurygregory has joined #zuul22:06
*** y2kenny has joined #zuul22:06
y2kennyWith the way pre-run and post-run are done, I understand that any pre- or post- run can fail and failing the whole job.  Is there a mechanism for the parent job to short circut the job such that the children job will not run? (An example use case might be a parent job that tries to fetch something from cache.  If the fetch is unsuccessful, children22:12
y2kennywill get run.  If successful, short shortcut, not run the job but the job still succeed.)22:12
clarkby2kenny: yes you can set up job dependencies22:13
clarkbwhere parent has to succeed before chidlren are started22:13
y2kennyclarkb: um...  so this is separate from the pre- post- mechanism?  Does the job dependencies support conditional (i.e. if success run A, if fail run B?)22:15
y2kennyclarkb: with the pre- post- mechanism, I was thinking of something like this (since the pre- post- thing looks like the interceptor pattern):22:16
clarkby2kenny: yes pre and post is within a job. The dependencies are between jobs. For conditionals you have to use zuul_return for that iirc. Your parent job uses zuul_return somehow to indicate which jobs to execute next22:16
clarkbtristanC: ^ I think you use that, do you know what the details are?22:16
y2kennycase A:) grandparent-pre -> parent-pre -> child pre -> child-run -> child post -> parent-post -> grandparent-post22:17
clarkby2kenny: https://zuul-ci.org/docs/zuul/reference/jobs.html#skipping-child-jobs22:18
clarkboh that gets more complicated. For that you also need to use pause22:18
clarkbhttps://zuul-ci.org/docs/zuul/reference/jobs.html#pausing-the-job22:18
y2kennycase B:)  grandparent-pre -> parent-pre -> skipped -> parent-post -> grandparent-post22:18
clarkbbut I think it is doable via zuul_return for both sides of that goal22:18
y2kennyclarkb: ok... I will take a look at the links22:18
y2kennyclarkb: oh... the skipping child job is probably what I am looking for22:19
y2kennyand the pause job is interesting too... good to learn about it22:20
*** iurygregory has quit IRC22:20
*** rfolco|ruck has quit IRC22:25
*** rfolco|ruck has joined #zuul22:25
*** iurygregory has joined #zuul22:35
*** openstackgerrit has quit IRC22:37
tristanCclarkb: y2kenny: yep, i think zuul_returns child_jobs is the only to achieve conditional run22:44
*** iurygregory_ has joined #zuul23:02
*** holser has quit IRC23:03
*** holser has joined #zuul23:04
*** iurygregory has quit IRC23:04
*** iurygregory_ is now known as iurygregory23:08
*** rlandy|PTO has quit IRC23:29
*** hashar has quit IRC23:45

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!