Monday, 2020-04-13

*** jamesmcarthur has quit IRC00:08
*** jamesmcarthur has joined #zuul00:38
*** jamesmcarthur has quit IRC00:59
*** jamesmcarthur has joined #zuul01:00
*** jamesmcarthur has quit IRC01:05
*** swest has quit IRC01:21
*** swest has joined #zuul01:35
*** jamesmcarthur has joined #zuul01:38
*** sanjayu__ has quit IRC01:45
*** jamesmcarthur has quit IRC01:46
*** msuszko has quit IRC02:12
*** msuszko has joined #zuul02:13
*** jamesmcarthur has joined #zuul02:33
*** jamesmcarthur has quit IRC02:40
*** jamesmcarthur has joined #zuul02:41
*** jamesmcarthur has quit IRC02:42
*** jamesmcarthur has joined #zuul02:47
*** jamesmcarthur has quit IRC02:55
*** jamesmcarthur has joined #zuul02:56
*** bhavikdbavishi has joined #zuul03:01
*** jamesmcarthur has quit IRC03:01
*** bhavikdbavishi1 has joined #zuul03:09
*** bhavikdbavishi has quit IRC03:11
*** bhavikdbavishi1 is now known as bhavikdbavishi03:11
*** jamesmcarthur has joined #zuul03:22
*** jamesmcarthur has quit IRC03:26
*** Goneri has quit IRC03:44
*** ysandeep|off is now known as ysandeep|rover04:07
*** bhavikdbavishi has quit IRC04:07
*** bhavikdbavishi has joined #zuul04:09
*** bhavikdbavishi has quit IRC04:15
*** Guest78227 has quit IRC04:23
*** bhavikdbavishi has joined #zuul04:32
*** evrardjp has quit IRC04:37
*** evrardjp has joined #zuul04:37
*** bhavikdbavishi has quit IRC04:45
*** bhavikdbavishi has joined #zuul04:46
*** sgw has joined #zuul04:56
*** bhavikdbavishi has quit IRC04:57
*** bhavikdbavishi has joined #zuul04:58
*** bhavikdbavishi has quit IRC05:02
*** sanjayu__ has joined #zuul05:05
*** msuszko has quit IRC05:06
*** msuszko has joined #zuul05:06
*** msuszko has quit IRC05:54
*** msuszko has joined #zuul05:55
*** gtema has joined #zuul06:28
*** gtema has quit IRC06:36
*** bhavikdbavishi has joined #zuul06:37
*** avass is now known as Guest5019606:43
*** avass has joined #zuul06:43
*** avass has quit IRC07:03
*** bhavikdbavishi has quit IRC07:04
*** Guest50196 is now known as avass07:23
openstackgerritAlbin Vass proposed zuul/zuul-operator master: Use ensure-* roles  https://review.opendev.org/71940107:25
openstackgerritAlbin Vass proposed x/pbrx master: Use ensure-* roles  https://review.opendev.org/71940207:32
*** bhavikdbavishi has joined #zuul07:34
*** jpena|off is now known as jpena07:44
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Remove install-* roles  https://review.opendev.org/71932207:52
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Remove install-* roles  https://review.opendev.org/71932207:52
*** ysandeep|rover is now known as ysandeep|lunch08:07
*** bhavikdbavishi has quit IRC08:17
*** bhavikdbavishi has joined #zuul08:38
*** bhavikdbavishi has quit IRC08:50
*** bhavikdbavishi has joined #zuul08:53
*** ysandeep|lunch is now known as ysandeep|rover09:05
*** tosky has joined #zuul09:25
*** arxcruz is now known as arxcruz|off10:23
*** msuszko has quit IRC10:25
*** msuszko has joined #zuul10:37
*** armstrongs has joined #zuul10:38
armstrongsWhat is the best way to find out which nodepool server created a vm. Is this info contained in any zuul variables? Was looking for something similar to zuul.executor.hostname10:41
*** armstrongs has quit IRC10:50
*** ysandeep|rover is now known as ysandeep|coffee11:02
*** bhavikdbavishi has quit IRC11:16
*** bhavikdbavishi has joined #zuul11:23
*** ysandeep|coffee is now known as ysandeep|rover11:35
*** jpena is now known as jpena|lunch11:38
*** smyers_ has joined #zuul11:42
*** smyers has quit IRC11:42
*** smyers_ is now known as smyers11:42
*** rlandy has joined #zuul12:07
*** sugaar has quit IRC12:10
*** jpena|lunch is now known as jpena12:32
*** armstrongs has joined #zuul12:35
*** harrymichal has joined #zuul12:44
*** armstrongs has quit IRC12:46
avassarmstrongs: I don't think that's possible12:49
*** rfolco has joined #zuul12:52
*** rfolco is now known as rfolco|bbl12:53
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Test base-test  https://review.opendev.org/71945713:13
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Test base-test  https://review.opendev.org/71945713:14
openstackgerritAlbin Vass proposed zuul/zuul master: Enables whitelisting and configuring callbacks  https://review.opendev.org/71726013:18
*** lseki has joined #zuul13:24
*** rfolco|bbl is now known as rfolco13:52
*** bhavikdbavishi has quit IRC13:54
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Adds roles to install and run hashicorp packer  https://review.opendev.org/70929214:04
corvustristanC, tobiash: i think the zk tls stack is ready -- https://review.opendev.org/712733 could use some +2s14:07
corvustobiash: and https://review.opendev.org/713545 could use a +2 from from you14:07
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Adds roles to install and run hashicorp packer  https://review.opendev.org/70929214:10
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Adds roles to install and run hashicorp packer  https://review.opendev.org/70929214:11
*** ysandeep|rover is now known as ysandeep|away14:12
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Increase scheduler wait to timeout and improve logs collection  https://review.opendev.org/71816214:18
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Increase scheduler wait timeout and improve logs collection  https://review.opendev.org/71816214:18
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275914:27
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Test base-test  https://review.opendev.org/71945714:27
avasscorvus: how do I prove that the cleanup phase works for that ^ ? since we don't save logs for the cleanup-run and it doesn't set the job result14:32
tristanCcorvus: it seems like we need to better specify how a zuul-operator user would configure an external zk service. For database we set a secret with a `dburi` string value.14:32
tristanCfor zk, should it be a list of secret tuple that contains ({`hostname`, `port`}, {`tls.crt`, `tls.key`, `ca.crt`}) ?14:34
corvustristanC: i would think a single secret with structured information would be best; we only need/want one cert, so probably something that looks like the zuul zk connection info config structure?14:36
tristanCcorvus: oh, so multiple zk service can use a common cert?14:38
corvustristanC: a client needs only a single cert to talk to multiple zk servers.  the zk servers each need their own cert, but in the case that an external zk is being used, we don't worry about that.14:39
corvusavass: that looks like a test of zuul rather than a test of any roles or jobs in zuul-jobs.  zuul has a unit test that verifies that cleanup playbooks work.14:39
corvusavass: so in short, i don't think you need that change at all14:39
corvusavass: but if there were some role that was typically run in a cleanup playbook and we wanted to test that role in zuul-jobs, then i would suggest a test job that ran the role in the 'run' playbook14:40
tristanCcorvus: oh i see, the `zookeeper-tls` configuration is global to all zookeeper servers14:40
corvustristanC: yeah, so generally speaking, the secret should have a (list of host+ports) and one (cert, key, and ca-cert).14:41
avasscorvus: it's for https://review.opendev.org/#/c/708871/414:41
avassGuess I should add that to the change heh :)14:41
tristanCcorvus: ok perfect. It seems easier to request a secret per certificate with the default `tls.crt`, `tls.key` and `ca.crt` so that user can provide a direct reference to a secret created by cert-manager14:42
tristanCcorvus: i did that for the registry where the user info and certificates are split in two secrets14:43
corvusavass: ack -- then yeah, if we want to test the add-remove ssh key roles, we should put those in a run playbook.  i would test them together in the run playbook.14:43
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add schema validation error message  https://review.opendev.org/71899914:44
openstackgerritAlbin Vass proposed zuul/zuul-jobs master: Adds roles to install and run hashicorp packer  https://review.opendev.org/70929214:44
avasscorcus: ah, but the test is not for the roles themselves, rather to make sure that moving remove-build-ssh key from post to cleanup doesn't break anything14:47
*** cdearborn has joined #zuul14:49
corvusavass: i don't think that's testable; and i think the existing tests for the "base" roles also don't rely on their being in any particular playbook (they're all tested in run)14:49
avasscorvus: since cleanup-run doesn't really work for child jobs if you remove the build key during post :)14:49
avasscorvus: yeah, that's why we merge base-test -> check that it works -> merge base14:49
corvus++14:50
avasscorvus: so it's testable, but a bit hard to review without rechecking the change that using base-test as parent14:50
corvusyeah, i should have said i don't think it's testable in the framework we have in zuul-jobs :)14:51
avassah :)14:51
avasshow do we test that then?14:52
corvusavass: i don't think we can.  i think we trust your local testing of the change :)14:54
corvusavass: i think the most we can do in zuul-jobs is test that a sequence of roles works as expected14:55
avasscorvus: I guess rechecking and looking at the live logs is the way to review that then :)14:56
corvusavass: you already did that though, right?  you made the move from post to cleanup using base-test, right?14:57
corvusooooh14:58
avasscorvus: yep, but I mean for making sure that it works before we merge: https://review.opendev.org/#/c/717827/14:58
corvusi see14:58
corvusthere is confusion here14:58
corvusnothing in opendev uses zuul-base-jobs14:58
avasscorvus: now I'm confused14:59
fungithat repository was created initially as an example, because our documentation said you need a base job, and we wanted a minimal one to point to in the docs14:59
corvusyep.  opendev overrides all of the jobs that are defined in zuul/zuul-base-jobs in the opendev/base-jobs repo.  so changes to that repo have no effect on any jobs running in opendev.15:00
avasssure, but I mean, it would be good to make sure those examples are valid15:00
fungii agree, testing the zbj repo sounds like a good idea15:01
corvusavass: indeed, though in order to do that, we would probably need a job (like zuul-quick-start) which set up an entire zuul system.15:01
corvusAJaeger: ^ fyi re 71782715:04
AJaegercorvus: ah! Sorry, avass for the confusion!15:05
corvus(and even then, it would probably only be able to test a static fileserver log upload role)15:05
*** zxiiro has joined #zuul15:07
avassalright :)15:08
avassAJaeger: I think I migrated all of the install-* roles to ensure-* now.15:11
AJaegeravass: yes, looks like. We need to wait at least 2 weeks after the announcement before we merge this, maybe a bit longer this time15:11
openstackgerritMerged zuul/zuul-base-jobs master: Remove ssh key in base cleanup run.  https://review.opendev.org/71782715:12
avasssure15:13
avassI guess we should announce that in zuul-discuss15:13
fungideprecations usually also get announced to the zuul-announce ml, i think15:16
fungi(with followup discussion on the zuul-discuss ml)15:16
avassthat's actually what I meant... guess it's time to get some coffee15:17
openstackgerritMerged zuul/zuul master: Remove David Shrewsbury from Zuul Maintainers  https://review.opendev.org/71871215:19
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add a zuul-ensure-database-passwords role  https://review.opendev.org/71788015:21
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275915:22
openstackgerritMerged zuul/zuul master: Add Albin Vass to zuul-jobs maintainers  https://review.opendev.org/71871315:30
corvusavass: can you join #opendev ?  we're fixing up your gerrit account :)15:37
corvusavass: ping me there when you're around again15:40
avasscorvus: I'm here!15:41
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add zuul-registry deployment  https://review.opendev.org/71065015:44
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add initial withCertManager input toggle  https://review.opendev.org/71884015:44
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add gearman tls secret provided by cert-manager  https://review.opendev.org/71911015:44
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add registry tls secret provided by cert-manager  https://review.opendev.org/71918515:44
*** olaph has quit IRC15:45
corvusavass: you should have +2 access in the zuul-jobs repos now :)15:46
tristanCavass: congrats!15:47
AJaegeravass: congrats - and thanks!15:48
avassI do! and thanks! :)15:55
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275915:58
AJaegercorvus: could you review 718284 again, please? avass left a comment...15:58
corvusgreat, lgtm; i think the only outstanding question is from tristanC about whether we should start documenting role outputs, bat that was a +2 question so i think we can merge and move forward16:01
corvus(i think maybe documenting role outputs is a good idea)16:01
corvus+316:02
corvusthe container registry roles have some outputs too16:02
AJaegerthanks, corvus16:05
AJaegerany reviewers for the rest of the stack to change the way how we install pip, please? see https://review.opendev.org/#/c/71763916:06
AJaegerany additional reviewer for a simple linter fix for zuul-jobs, please? https://review.opendev.org/71905416:09
openstackgerritMerged zuul/zuul-jobs master: ensure-tox: make idempotent and update testing  https://review.opendev.org/71828416:12
*** y2kenny has joined #zuul16:16
*** harrymichal has quit IRC16:18
*** armstrongs has joined #zuul16:22
openstackgerritTristan Cacqueray proposed zuul/nodepool master: config: add environment variable substitution  https://review.opendev.org/71959916:30
openstackgerritMerged zuul/zuul-jobs master: Fix check_jobs_documented linter  https://review.opendev.org/71905416:31
avassAJaeger: left a comment on 71763916:34
AJaegeravass: thanks16:35
avassAJaeger: checking ansible_python.version looks inconsistent but I'm not sure if there's a reason for that16:35
*** evrardjp has quit IRC16:37
*** evrardjp has joined #zuul16:37
AJaegerlet's see what ianw says once he's awake ^16:40
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275916:46
*** harrymichal has joined #zuul16:48
openstackgerritTristan Cacqueray proposed zuul/nodepool master: config: add environment variable substitution  https://review.opendev.org/71959916:51
*** rlandy is now known as rlandy|biab16:52
*** armstrongs has quit IRC16:53
*** jpena is now known as jpena|off17:01
openstackgerritTristan Cacqueray proposed zuul/nodepool master: config: add environment variable substitution  https://review.opendev.org/71959917:05
tristanCzuul-maint: a two-liner change on zuul-registry is waiting for review to unlock a few other already approved changes: https://review.opendev.org/71776717:12
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275917:20
*** olaph has joined #zuul17:22
*** rlandy|biab is now known as rlandy17:51
*** harrymichal has quit IRC17:52
tristanCmordred: thank you for the review!17:53
*** rlandy is now known as rlandy|lunch17:57
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275917:58
openstackgerritMerged zuul/zuul-registry master: Use explicit provides/requires for container jobs  https://review.opendev.org/71776718:03
*** y2kenny has quit IRC18:12
*** igordc has joined #zuul18:13
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add zuul-registry deployment  https://review.opendev.org/71065018:13
openstackgerritTristan Cacqueray proposed zuul/zuul-registry master: config: add environment variable substitution  https://review.opendev.org/71064418:13
*** y2kenny has joined #zuul18:17
*** rlandy|lunch is now known as rlandy18:19
tobiashcorvus, tristanC: tls zk stack lgtm18:27
y2kennyis the pipeline config for the OpenStack CI available on opendev somewhere?  (I have seen opendev/system-config but I believe that is just the job definitions.)18:30
y2kennyI am curious about your deploy and periodic pipeline18:30
clarkby2kenny: https://opendev.org/openstack/project-config/src/branch/master/zuul.d is the bulk of that data for openstack18:31
tristanCtobiash: i'm hoping to have successful tls setup again with the zuul-operator soon18:31
clarkbpipelines file in particular but some of the other bits may be useful too18:31
y2kennyclarkb: ah, under project-config.  Great, thanks!18:32
clarkb(note that we'll eventually migrate those CD specific bits into opendev but its a long ish process of untangling things)18:32
corvusyeah, most of the "opendev/" repos are actually still in the openstack tenant because we haven't separated them out yet18:32
corvuswhen we do that, we'll probably move the 'deploy' pipeline into opendev/project-config instead of openstack/project-config18:33
corvusand i think we're close18:33
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: ci: pin minikube version to 1.8.2  https://review.opendev.org/71544318:39
tristanCcorvus: mnaser: not sure what is the exact frequencies, but install-kubernetes seems to be quite often not working (e.g. running kubectl get pods  failing with timeout or connection failure)18:40
mnasertristanC: do you have any logs or examples? i personally have almost never had issue with it ever18:41
tristanCmnaser: in a recent run, in the logs it says `Failed to list *v1.Pod: pods is forbidden: User "system:kube-scheduler" cannot list resource "pods"` : https://zuul.opendev.org/t/zuul/build/e5137f0ad29642bd8e9eeede5cb593be/log/docker/k8s_kube-scheduler_kube-scheduler-ubuntu-bionic-rax-ord-0015882324_kube-system_5795d0c442cb997ff93c49feeb9f6386_0.txt#1718:43
tristanCand the build failed because kubectl was not able to connect to the api18:43
mnasertristanC: it would be nice if you refactored your 'describe resources' task into collect-kubernetes-logs or whatever we neded up calling that role18:44
corvustristanC: are you suggesting that running the latest means running unstable code (of k8s itself) and 1.8.2 will be more stable?18:44
mnaserwe already do that for pods and i guess it would be useful for other resources18:44
tristanCi added a simple `kubectl get pods` to the pre-run of the zuul-operator, and it seems to prevent quite a few issue, in the current status page you can see a job on it's 3rd attempt to get a functionning k8s api18:45
tristanCcorvus: i don't know the frequency of the failure as they are mostly prevented by the extra pre-run check, but it seems to be happening a lot more recently.18:46
mnaserhttp://zuul.opendev.org/t/vexxhost/builds?job_name=openstack-operator%3Afunctional18:46
mnaserall those failures are failures that are real failures18:46
tristanCmnaser: it is refactored in https://review.opendev.org/#/c/718162/18:47
tristanCmnaser: yes, the retried failure are not reported in the builds interface18:47
tristanCmnaser: thanks to https://opendev.org/zuul/zuul-operator/src/branch/master/playbooks/zuul-operator-functional/pre-k8s.yaml#L16-L1718:48
mnasersomething seems to be restarting the whole stack fwiw18:48
mnaserall containers seem to be restarted18:48
*** zxiiro has quit IRC18:48
tristanCit used to happens once in a while, hence the addition of the pre task to limit the issue, but since this week end i see more and more job being retried once or twice before reaching the run phase18:49
mnaseralso i wonder if minikube doesnt full wait for the cluster to settle before reporting ok18:49
mnaserand the fact that you're doing a kubectl get pods right away after is triggering a race18:50
corvusis it the use-buildset-registry role?18:50
mnaserbecause inside ensure-kubernetes, we actually don't "verify" if the cluster is up18:50
mnasercorvus: ooooh there you go that's a good lead18:51
tristanCcorvus: that could be it indeed18:51
mnaserit does restart docker18:51
corvusso maybe we need that to wait a bit longer before returning?18:51
corvus(maybe it should do a kubectl get pod in a loop or something?)18:51
mnaseri think the better thing is to run use-buildset-registry *before* ensure-kubernetes18:52
mnaseraka docker should be settled before we get k8s on top of it (but yes, kubectl get pod doesn't hurt too)18:52
mnaseri think i added the abiltiy to run use-buildset-registry inside ensure-docker18:52
mnaserso you should be able to set that and be good t go18:53
corvusmaybe i should have put this in the ubr role: https://opendev.org/zuul/zuul-jobs/src/branch/master/test-playbooks/registry/buildset-registry-k8s-crio.yaml#L13-L1818:54
tristanCmnaser: do you remember the option name to activate that ability?18:55
corvusmnaser: i don't think we currently use ensure-docker (i think we let ensure-k8s handle it)18:55
corvusah, ensure-k8s calls ensure-docker18:55
corvusso maybe we can add the same option to ensure-k8s and pass it through18:56
corvusmnaser, tristanC: use-buildset-registry does some work that only happens if k8s is already installed18:56
corvushttps://opendev.org/zuul/zuul-jobs/src/branch/master/roles/use-buildset-registry/tasks/user-config.yaml#L51-L6218:57
corvusthat depends on k8s already having been installed18:57
mnaseroh, so my change is probably broken then18:57
mnaserwell, partly broken18:57
mnaserworks if you use ensure-docker, broken if you try and use it with k8s including it18:58
corvus(essentially k8s has its own docker user config, so that puts it in place)19:00
tristanCcorvus: fun fact, zookeeper java tls library doesn't work if the ca has the `.crt` extension (as provided by cert-manager), and it only works when the file has the `.pem` extension19:00
corvustristanC: hrm, i think it uses the extension to detect whether it's a pcks8 or 11 file19:01
corvustristanC, mnaser: quick fix: put that cluster-info loop in use-build-set-registry to run iff kubelet exists19:01
mnasercorvus: i wonder if we can wire minikube to put the right config from the get-go if we need to use the buildset registry19:01
corvustristanC, mnaser: longer term fix: maybe make ensure-buildset-registry idempotent and call it twice in ensure-k8s?19:01
corvusmnaser: that would be even better19:02
tristanCshouldn't all zuul jobs use the buildset-registry unless specified otherwise?19:02
mnaserhttps://github.com/kubernetes/minikube/issues/608019:02
corvustristanC: maybae so19:03
mnaserhttps://minikube.sigs.k8s.io/docs/handbook/filesync/19:03
mnaserwe could use that.19:03
*** Goneri has joined #zuul19:03
mnaseror we have this too: https://minikube.sigs.k8s.io/docs/handbook/registry/19:05
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Increase scheduler wait timeout and improve logs collection  https://review.opendev.org/71816219:05
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275919:05
tristanCcorvus: so, would you like me to port the kubectl get retry loop to zuul-jobs from https://review.opendev.org/#/c/718162/5..6/playbooks/zuul-operator-functional/pre-k8s.yaml ?19:06
corvustristanC: yeah, let's try that; that should be easy/fast and we can look at the sync idea later19:21
*** cloudnull has joined #zuul19:25
openstackgerritTristan Cacqueray proposed zuul/zuul-jobs master: use-buildset-registry: wait for kubernetes service to be available  https://review.opendev.org/71967319:27
*** y2kenny has quit IRC19:32
*** sanjayu__ has quit IRC19:39
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275919:51
*** irclogbot_1 has quit IRC19:51
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add initial withCertManager input toggle  https://review.opendev.org/71884019:52
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add gearman tls secret provided by cert-manager  https://review.opendev.org/71911019:52
*** irclogbot_0 has joined #zuul19:53
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add registry tls secret provided by cert-manager  https://review.opendev.org/71918519:54
tristanCsorry for the gerritbot spam, it is tricky to get operator test works reliably with cert-manager and zookeeper tls... i hope this will be stable soon!19:56
*** igordc has quit IRC19:58
*** olaph has quit IRC20:01
*** olaph has joined #zuul20:01
*** olaph has quit IRC20:02
openstackgerritMerged zuul/zuul-jobs master: use-buildset-registry: wait for kubernetes service to be available  https://review.opendev.org/71967320:19
*** y2kenny has joined #zuul20:27
*** olaph has joined #zuul20:29
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275920:44
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add schema validation error message  https://review.opendev.org/71899920:45
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add a zuul-ensure-database-passwords role  https://review.opendev.org/71788020:45
*** sgw has quit IRC20:57
*** sgw has joined #zuul21:18
tristanCcorvus: tobiash: at last, zookeeper tls configuration passed the operator tests. It took longer than expected because the launcher service addition was merged after the initial tls change was proposed.21:18
tristanChere is the build: https://zuul.opendev.org/t/zuul/build/706551ec4881438f84a1b97636bb94e7 , in particular: https://zuul.opendev.org/t/zuul/build/706551ec4881438f84a1b97636bb94e7/log/docker/k8s_zk_zuul-zk-0_default_278f1d30-2270-4af9-9854-051bcf6a5079_0.txt#10321:20
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Increase scheduler wait timeout and improve logs collection  https://review.opendev.org/71816221:22
*** y2kenny has quit IRC21:39

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