Tuesday, 2020-04-14

*** openstack has joined #zuul09:56
*** ChanServ sets mode: +o openstack09:56
*** dpawlik has joined #zuul09:56
*** rpittau is now known as rpittau|bbl10:23
*** ysandeep is now known as ysandeep|afk10:37
*** ysandeep|afk is now known as ysandeep|rover10:53
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: WIP: tox: allow tox to be upgraded  https://review.opendev.org/69005710:54
*** jcapitao is now known as jcapitao_lunch10:57
*** bhavikdbavishi has quit IRC11:11
tristanCzuul-maint, could you please have a look at the zk-tls changes, https://review.opendev.org/712733 and https://review.opendev.org/712531 . They already have 2 +2, would it be ok to merge them soon?11:18
*** cdearborn has joined #zuul11:30
*** jpena is now known as jpena|lunch11:36
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add schema validation error message  https://review.opendev.org/71899911:38
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add a zuul-ensure-database-passwords role  https://review.opendev.org/71788011:38
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add zuul-registry deployment  https://review.opendev.org/71065011:38
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Add TLS configuration to ZooKeeper service  https://review.opendev.org/71275911:38
*** ysandeep|rover is now known as ysandeep|coffee11:39
*** gtema has quit IRC11:46
*** gtema has joined #zuul11:51
*** ysandeep|coffee is now known as ysandeep11:51
*** ysandeep is now known as ysandeep|rover11:56
*** hashar has joined #zuul12:02
*** bhavikdbavishi has joined #zuul12:04
*** rlandy has joined #zuul12:14
*** jcapitao_lunch is now known as jcapitao12:17
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: tox: allow tox to be upgraded  https://review.opendev.org/69005712:28
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor the input in schemas files  https://review.opendev.org/71993212:30
*** rpittau|bbl is now known as rpittau12:31
zbrtristanC: clarkb: can we do the update of create-react-app? https://review.opendev.org/#/c/716305/12:36
*** jpena|lunch is now known as jpena12:40
tristanCzbr: that change seems to be broken12:45
*** gtema has left #zuul12:57
zbrtristanC: how did you get to that error?13:05
zbryour comment may explain why my own patch did not work, but i want to see the error on that patch.13:06
*** Goneri has joined #zuul13:10
tristanCzbr: i clicked the preview website link13:15
*** sgw has quit IRC13:16
zbrinteresting, now I get a not found error but minutes ago it was loading correctly.13:16
zbrthe multi-site one is loading13:18
tristanCzbr: you need to load it from the zuul build page, direct access result in not found error because of the way react router works13:25
*** gtema_ has joined #zuul13:34
*** sgw has joined #zuul13:34
*** gtema has joined #zuul13:46
openstackgerritMonty Taylor proposed zuul/zuul master: Update to create-react-app 3.4.1  https://review.opendev.org/71630513:47
mordredtristanC: updating redux as well fixed it for me locally ^^13:47
mordredlet's see if it fixes it in the gate13:48
*** gtema_ has quit IRC13:48
*** evgenyl has quit IRC13:50
*** stevthedev has quit IRC13:50
*** rpittau has quit IRC13:50
*** stevthedev has joined #zuul13:51
*** evgenyl has joined #zuul13:51
*** rpittau has joined #zuul13:51
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor file creation to function files  https://review.opendev.org/71996513:54
tristanCmordred: nice, let see13:55
*** gtema has left #zuul13:55
tristanCcorvus: mordred: tobiash: clarb: i've started to refactor the dhall files with https://review.opendev.org/719932 and https://review.opendev.org/719965 . I think it's better like that, but that's not necessary, it's purely cosmetic. what do you think? Should i continue to split the resources.dhall file?13:57
*** zxiiro has joined #zuul14:00
mordredtristanC: I like the second one (the files one) better than the first. for the second one, it's nice because you get the main file content in context that looks a bit more like the final file rather than indented in the middle of the page ... for the first one, the original resources file just seems easier to read all together to my eyeball. but I don't have strong opinions one way or the other14:03
corvusare those alternatives, or are they two steps in the same process?14:04
tristanCcorvus: they are atomic14:05
corvus(because the second one seems to depend on the first)14:05
corvustristanC: so the choices you are offering are (a) 932 or (b) 932+965 ?14:06
tristanCcorvus: it doesn't have too, it's just easier for me to keep a single stack14:06
tristanCcorvus: (a) keep only input and resources, (b) split all the schemas with 932, (c) split the configuration files, (d) b+c14:07
tristanCbut i agree (b) requires being able to have many files open at once, and i don't mind keeping the single `input` file14:07
tristanCthen i'd like to work on (e) move KubernetesComponent to their own file, so that we have conf/zuul/Components/{Scheduler,Executor,Registry,...}14:08
*** bhavikdbavishi has quit IRC14:09
corvusi think i agree with mordred, which i think means i like (c).  mostly i think about if i'm looking at a schema, and i see that it requires a 'gerrit' i don't have to go to the gerrit file to see what that looks like.  but also, i am generally more comfortable with big files than other folks.  :)14:15
tristanCalright, thank you for the feedback, i'll drop 93214:18
tristanCi figured big files are not an issue, considering the zuul/executor and web modules :) but it's also nice to isolate objects that are independent14:18
corvustristanC: sounds good, but also you may get feedback from clarkb if you wait another 30-60 minutes :)14:19
*** sshnaidm has joined #zuul14:29
*** sshnaidm has quit IRC14:30
clarkbI'm distracted by the osf board call but pulling up those changes now to see14:40
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor file creation to function files  https://review.opendev.org/71996514:44
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor kubernetes resources constructor to the function file  https://review.opendev.org/71999114:44
clarkbcorvus: tristanC mordred I think  Itoo prefer the second change over the first. I don't mind either though. One thing with splitting though is you lose a bit of context so we may need a bit more commentary in some places? https://review.opendev.org/#/c/719965/1/conf/zuul/files/nodepool.yaml.dhall for example seems like the identity function on its own14:48
clarkbwithout context it seems unnecessary (and maybe it is?)14:48
tristanCclarkb: sure i can add comment. thank you for the review14:49
*** ysandeep|rover is now known as ysandeep|away14:50
*** bhavikdbavishi has joined #zuul15:17
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor deployment and statefulset functions  https://review.opendev.org/72000715:29
tobiashcorvus: re topic 'where to configure allow-cyclyc-deps' did we we decide to change cdep to be allowed in the project pipeline in a config project or shall we leave that in the tenant config?15:37
corvusmnaser: https://review.opendev.org/717371 has a WIP title and 2x +2s -- is it ready to go?15:38
corvustobiash: ah, let me catch up on that15:38
fungitobiash: (and armstrongs if he sees this in the web log) opendev manages to peak at around 80-100 concurrent builds per executor, but it likely depends on the characteristics of the executors themselves, the typical workloads, and maybe other factors as well15:40
corvusmnaser, tristanC, mordred: i think i see potential problems with https://review.opendev.org/71781715:41
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor backend services  https://review.opendev.org/72001915:43
tristanCcorvus: indeed. It seems like using include_role from a role should be explicit in the role documentation15:44
corvustobiash: based on what we wrote in the spec: https://zuul-ci.org/docs/zuul/reference/developer/specs/circular-dependencies.html i think that maybe putting the allow-circular-dependencies setting on the new Queue object may work and be intuitive.  what do you think?15:45
corvustobiash: specifically "Changes with cross-repo circular dependencies are required to share the same change queue." makes me think this makes sense15:45
tristanCcorvus: mordred: tobiash: clarb: (e) is proposed in https://review.opendev.org/720019 for Backend service. I'd like to do the same for Zuul and Nodepool too, does that seems right to you?15:45
tobiashhrm, interesting thought15:46
corvustristanC: lgtm15:49
tobiashcorvus: I think that's a good idea, I'll discuss it tomorrow with Simon15:50
corvustobiash: i like the queue change15:51
tobiashcorvus: cool, then I'll finish up that change with docs and reno15:54
*** rpittau is now known as rpittau|afk16:02
tobiashcorvus: re cdep and the flag on the queue object, how would we handle independent pipelines with this?16:10
tobiashwould we allow cyclic deps on those in any case?16:10
*** sanjayu__ has quit IRC16:10
corvustobiash: hrm, good q; let me think about that16:10
*** rlandy is now known as rlandy|brb16:14
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor backend services  https://review.opendev.org/72001916:23
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor Zuul services  https://review.opendev.org/72002416:23
corvustobiash: maybe this does need to be a tenant-level config :/16:32
*** rlandy|brb is now known as rlandy16:35
*** evrardjp has quit IRC16:37
*** evrardjp has joined #zuul16:37
tobiashcorvus: ok, so then this matches the current implementation16:48
corvustobiash: because i think we shouldn't allow a cycle in a check pipeline unless it's at least possible that the same cycle could be enqueued in gate.  however, even if we make it a tenant-level config, we can still have a case where it can't be enqueued in gate if all the projects don't share a queue.  i don't think there's anything we can do about that.  but it seems like if we put the setting on the queue16:49
corvusobjects, then in addition to that potential problem, we would also have the potential problem where they might share a queue in gate, but the queue doesn't actually allow cycles.  so we've doubled the number of cases where the configuration in check wouldn't match gate.16:49
*** hashar has quit IRC16:49
corvusthe only way i could see to make that work would be to attach the queue object to gate as well.16:50
corvusand that would be weird because we won't actually share the queue there.  we would just use it to get those settings.16:50
corvusokay, we *could* move the queue from the pipeline to the project16:50
corvusso that you can't have different shared queues for different dependent pipelines16:51
corvuswhich, to be honest, probably makes more sense anyway.  but it's a bigger change (it would actually mean a deprecation in zuul config syntax)16:51
tobiashhrm, that sounds like a lot of effort16:53
corvustobiash: okay, so i think our choices are (a) make it a tenant config option as written in the spec; (b) put in on the queue object, move the queue object to be a project-level config, depcreate the pipeline level "queue" attribute.  then the queue object determines shared queue membership for dependent pipelines, and determines whether projects can have cyclic dependencies (and with which other projects) in16:53
corvusall pipelines.16:53
*** jcapitao has quit IRC16:54
corvus(b) is a lot of work for us, but honestly, probably not that much more work than we're going to do anyway.  it's a little work for users too, but we can make the upgrade seamless (and we have a bunch of major version bumps coming up, so we can probably even remove the old queue pipeline attribute by zuul v5)16:54
tobiashcorvus: let me think about it, since (a) is already fully implemented and battle tested in our deployment with several projects16:55
corvus(b) may be better because it makes it easier for 'check' to be a proper simulation of 'gate' in these complex situations16:56
corvustobiash: yeah, we did also write a spec, which we do to try to avoid design-after-the-fact16:56
tobiashyeah, the implementation matches the spec :)16:57
corvustobiash: i'm not sure this would be worth it for either feature on its own, but when you consider them both together, they touch 95% of what would be needed for this, so suddenly it may be worth it16:57
tobiashcorvus: so your suggestion would be to change 718531 to match per project queue instead of per pipeline and then rebase cdep on top of this and adapt it to use that?16:58
corvustobiash: i think so16:58
tobiashhow would we handle the (unlikely) case of two dependent pipelines with different queues on the same project?16:59
corvustobiash: during the backwards compat period, we might be able to keep the current scheme (and have those pipelines have different queues)17:00
tobiashok, so pipeline takes precedence with a fall-back to project and later pipeline is ignored17:01
corvusyeah17:01
tobiash(or better config error)17:01
tobiashok, I think I would even do this logic as its own change on top of 718531 which introduces the queue element17:03
tobiashand then on top of this cdep17:04
tristanCmordred: create-react-update still failed, and this time the unit test also found an issue (the expected links where not there)17:05
*** jpena is now known as jpena|off17:05
*** sgw has quit IRC17:07
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor file creation to function files  https://review.opendev.org/71996517:08
mordredtristanC: yeah. I'm not sure yet what's up with it :(17:10
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor file creation to function files  https://review.opendev.org/71996517:12
tristanCmordred: perhaps updating the main redux dependency would help (it seems to be pined at <4.0.0)17:13
openstackgerritSorin Sbarnea proposed zuul/zuul-jobs master: Improve 404 error message on download-logs.sh  https://review.opendev.org/72003517:13
mordredtristanC: maybe - I'll try17:21
*** Goneri has quit IRC17:23
openstackgerritMonty Taylor proposed zuul/zuul master: Update to create-react-app 3.4.1  https://review.opendev.org/71630517:25
*** sgw has joined #zuul17:29
*** Goneri has joined #zuul17:52
*** dpawlik has quit IRC18:02
*** bhavikdbavishi has quit IRC18:02
*** tobiash has quit IRC18:16
*** tobiash has joined #zuul18:17
tristanCzuul-maint , it would be really nice if https://review.opendev.org/719932 operator change and its parent can be reviewed and/or merged, or at least https://review.opendev.org/718999 where there are a few branches that grow from it.19:08
tristanCthe registry, zookeeper tls, cert-manager and today's refactor are kind of stuck until those key changes are integrated. Thanks in advance!19:09
*** armstrongs has joined #zuul19:12
*** armstrongs has quit IRC19:17
*** Goneri has quit IRC19:57
*** Goneri has joined #zuul19:58
*** tobberydberg_ has quit IRC20:17
*** fdegir4 has quit IRC20:19
*** fdegir4 has joined #zuul20:19
*** gtema has joined #zuul20:20
*** fdegir4 has quit IRC20:20
*** tobberydberg has joined #zuul20:22
*** gtema has quit IRC20:27
*** tobberydberg has quit IRC20:30
*** tobberydberg has joined #zuul20:36
*** tobberydberg has quit IRC20:37
*** tobberydberg has joined #zuul20:42
*** tobberydberg has quit IRC20:43
*** tobberydberg has joined #zuul20:45
*** tobberydberg has quit IRC20:45
*** tobberydberg has joined #zuul20:46
*** tobberydberg has quit IRC20:46
*** tobberydberg has joined #zuul20:46
*** tobberydberg has quit IRC20:47
*** tobberydberg has joined #zuul20:47
*** tobberydberg has quit IRC20:47
*** tobberydberg has joined #zuul20:51
openstackgerritMerged zuul/zuul-registry master: config: add environment variable substitution  https://review.opendev.org/71064420:52
*** tobberydberg has quit IRC20:55
*** tobiash has quit IRC21:18
*** tobiash has joined #zuul21:20
*** y2kenny has joined #zuul21:21
y2kennyIf I want to specify an executor only job, what do I use for nodeset?21:22
clarkby2kenny: [] an empty list21:23
y2kennyclarkb: Ah ok.  thanks.  I tried taking out nodeset entirely but I think it ended up just waiting.21:24
corvusclarkb, tristanC, mordred: this looks like a real openstack failure of the nodepool job: https://zuul.opendev.org/t/zuul/build/1ca928db99d84a22aa9382576ff556c5/console21:33
corvusboth nodepool-functional-openstack and nodepool-functional-openstack-src broke on that change, but they previously passed21:33
corvusi wonder if openstack changed out from under us21:34
corvusianw: ^21:34
openstackgerritMerged zuul/zuul master: Add TLS support for ZooKeeper  https://review.opendev.org/71253121:35
openstackgerritMerged zuul/zuul master: Move zuul-quick-start requires to pipeline and reparent  https://review.opendev.org/71354521:35
clarkbcorvus: 2020-04-14 21:13:36,408 INFO nodepool.NodeLauncher: [e: 2349321546eb43b3a2e134177fbae37b] [node_request: 900-0000000000] [node: 0000000000] Node is ready from the nodepool log21:38
tristanCnot sure to understand what is the failure, is this because the cloud-init content is incorrect?21:38
corvusyeah, if i'm reading the log right, it sort of looks like we're checking cloud config output or something?21:39
corvustristanC: that's what it looks like to me but i also am not sure21:39
openstackgerritMerged zuul/zuul master: Add release note for zookeeper tls support  https://review.opendev.org/71731221:39
clarkboh I see its failing after sshing into the host21:39
y2kennyclarkb:  I tried having [] for nodes but looks like the job is stuck just like not defining nodeset21:42
corvusclarkb, tristanC: yeah, that's exactly what's going on: https://opendev.org/zuul/nodepool/src/branch/master/tools/functional-test-check.sh#L70-L7521:42
clarkby2kenny: it should be nodeset: [] iirc21:42
clarkby2kenny: let me see if I can find an example21:42
y2kennyalso... Is there a way to kill a stuck job? (do I just dequeue?)21:43
corvusy2kenny, clarkb: nodeset: {nodes: []}21:43
corvuswe usually put that on 2 lines like:21:43
corvus    nodeset:21:43
corvus      nodes: []21:43
clarkbcorvus: tahnks21:43
y2kennyum... I tried that, but I got a stuck job...21:43
corvusy2kenny: dequeue is best; another option would be stop the executor21:44
clarkbcorvus: ah its testing that the userdata set by nodepool ends up on the node21:44
clarkbhttps://opendev.org/zuul/nodepool/src/branch/master/playbooks/nodepool-functional-openstack/templates/nodepool.yaml.j2#L37-L42 that comes from there21:45
corvusclarkb, tristanC, ianw: so somehow either devstack stopped passing that through, or glean isn't writing it?21:47
clarkbcorvus: in this case it is cloud-init not glean, but ya21:47
corvusoh, we use cloud-init in that test?21:47
clarkbcorvus: or I suppose it could be that openstacksdk stopped giving it to the service21:48
clarkbcorvus: ya glean doesn't support that functionality21:48
corvusah21:48
clarkbI seem to recall we dump the console logs somewhere? that might give us a clue if I can find it21:48
clarkbhttps://zuul.opendev.org/t/zuul/build/1ca928db99d84a22aa9382576ff556c5/log/instances/2c6ceb1c-47f9-492e-9459-6a713dab3588/console.log is the log21:49
clarkbok that image did run glean21:49
clarkbso that probably explains it21:49
corvusoh but wait -- it looks like that check is comparing what's in the nova user data with the expected value21:50
corvusso we're not checking what's on disk, the data is missing from 'nova show'21:50
clarkbcorvus: aha that woudl explain why it works even when not using cloud-init before. Ok so we aren't checking cloud-init ran just that nova did the appropriate things21:50
corvusthat narrows it down to nodepool/sdk not submitting the data, or the nova show output not showing it (or devstack/openstack losing it)21:50
corvusthat's the only time we run nova show, and we don't save the whole output21:51
corvusso we can't see what it looked like (either now or before)21:52
clarkbwas just going to ask if we have that output anywhere21:52
clarkbmaybe we should add a nova show to just before that and capture the output?21:52
corvus++21:52
openstackgerritJames E. Blair proposed zuul/nodepool master: WIP: run nova show  https://review.opendev.org/72008821:53
ianwyeah it makes sense as a "does this config in .yaml get through to nova" test21:53
corvusi'm guessing 'nova show' is from python-novaclient?21:54
ianwit probably just predates more extensive use of "openstack"?21:56
corvusthere was a release on april 1121:56
clarkbcorvus: yes re nova show21:57
corvusthat was the date of the last time this job passed21:57
corvusi see some changes in re dropping python 2 support21:57
corvusis it possible we're installing that in a py2 env, and the error we're going to see is "this doesn't support py2 anymore"?21:57
clarkbits possible that openstack server show would work too, but may need fiddling to get the user data back (I've never had good luck with osc and getting back specific api fields)21:57
clarkbcorvus: oh heh that could be21:58
ianwcorvus: very likely21:58
corvuswhat's the solution for that?  do we need to set some devstack flag?  or switch to 'openstack server show'?21:59
clarkbcorvus: well if it was installed by devstack I would expect it to just work22:02
clarkbcorvus: judging by the devstack output I think it installed under python 3.622:04
clarkbya it installed a py3 only wheel too22:05
clarkbMy guess is that hte output simply changed22:05
ianwahh yes a recheck i did before the dib gate now shows it too22:09
clarkbreading the git diff its possible this is a python string handling change? thats the bulk of the difference22:09
clarkbtransform_userdata was updated22:11
corvusoh cool that sounds promising22:12
corvusclarkb: what's the sha of that change?22:12
clarkbcorvus: c4c44bcb2df01b77089139b267b1219008f9421e22:14
clarkbchange to remove six22:15
clarkbit should be noted that I think the input to the api side is all handled by openstacksdk and doesn't touch this. So this would just be read out the otherside problems?22:15
corvuslooks like it at least wasn't intending to change the output22:16
ianwcorvus/clarkb: https://storage.gra.cloud.ovh.net/v1/AUTH_dcaab5e32b234d56b626f72581e3644c/zuul_opendev_logs_3e2/720088/1/check/nodepool-functional-openstack/3e282ea/job-output.txt22:49
ianwit does seem user_data is ... gone22:49
corvusayup22:51
corvusmordred, clarkb, ianw: ^ what do you think the next step is?22:51
ianwOS-EXT-SRV-ATTR:user_data22:52
ianwis it something to do with versions, and that extra bit on it22:52
corvusianw: is that from a prod system or something?22:53
ianwi'm just grepping nova source22:53
ianwdo we think the openstackclient will show it?22:56
ianwdoh, or even https://opendev.org/openstack/python-novaclient/commit/03dca4bc823c82054869dfaf6925d5e1e068ac5122:57
ianwDon't print user_data for 'nova show'22:57
ianwwhich is exactly the problem ...22:57
corvushow did i miss that one22:59
ianwi'm asking on -nova if maybe there's a better way to check23:00
*** rlandy has quit IRC23:00
ianwi guess it's not worth a flag in the client, it sounds like generically it's not useful -- just in this case when we're doing end-to-end testing it is23:01
ianwcorvus: to get thing back on track, maybe just update that wip to comment out the check, until we come up with something else?23:02
corvusianw: yep -- though i was just going to remove it and we can revert it back in later -- that ok?23:03
openstackgerritJames E. Blair proposed zuul/nodepool master: Stop checking user_data in func test  https://review.opendev.org/72008823:04
openstackgerritJames E. Blair proposed zuul/nodepool master: Add ZooKeeper TLS support  https://review.opendev.org/71273323:04
ianweither or, it seems like we probably still want to test it if we can?23:04
corvusianw: yeah, i'd be happy to test it23:04
corvusi just removed it to avoid ending up with comment detritus if it doesn't make it back in23:04
ianwprobably a few lines calling the nova client binding directly23:04
*** sanjayu__ has joined #zuul23:05
corvusor maybe 'openstack server show' has a way for that23:05
corvushonestly, i think putting it behind a flag makes a lot of sense23:05
corvus"real users" are going to want to know "did my userdata really make it to nova?" just like we do23:05
corvusalso, it's not really binary data, right?23:06
corvusit's base64 data23:06
corvus(so i don't see a problem with showing it on the cli)23:06
corvusmakes sense if the idea is "dont show it by default because it's big"23:06
ianwyeah, although i see the argument that it's an interactive focused tool, so dumping base64 isn't helpful to a human, and tests like us should probably go via api calls23:08
corvusi get "don't dump base64 by default" but i totally think that *some* tool (likely openstackclient) should output it when asked23:09
corvusbecause it's a legit debug tool for users23:09
corvus"confirm garbage out == garbage in" is a pretty basic debug tool in all situations23:09
corvusso if i set some user data to install a key, and the key isn't there, the first thing i want to know is "did the user data make it to the cloud?"23:10
corvusit's actually the same debugging process we just went through :)23:11
ianwdoesn't look like it will be too hard to add a -- flag, i'll take a look23:11
*** tosky has quit IRC23:20
mordredcorvus: openstacksdk totally retrives and shows user data in the server record23:23
mordredso if osc doesn't have it ... we should add it - at least behind a flag23:24
mordredthere's already a user-data flag in openstack server show23:25
corvuscool, so this should be a one-liner fix23:25
mordredoh - no - I take that back23:26
mordredthere's a flag to set it23:26
mordredstill looking23:26
mordredconfirms openstacksdk has it23:27
mordredI don't see it in the osc output - but I don't know if that's just because I don't have a server booted with user data23:32
mordredosc isn't stripping it from the return struct23:33
mordredbut - osc is using novaclient for this - and god only knows what that's doing23:33
openstackgerritIan Wienand proposed zuul/nodepool master: diskimage.username setting was not read from configuration file  https://review.opendev.org/71919123:52
openstackgerritIan Wienand proposed zuul/nodepool master: Test alternative username in unit tests  https://review.opendev.org/72010123:52
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor kubernetes resources constructor to the function file  https://review.opendev.org/71999123:53
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor deployment and statefulset functions  https://review.opendev.org/72000723:57
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor backend services  https://review.opendev.org/72001923:57
openstackgerritTristan Cacqueray proposed zuul/zuul-operator master: Refactor Zuul services  https://review.opendev.org/72002423:58

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