[01:02] <wallyworld> kelvinliu: here's a small PR to fix the pod spec parsing issue https://github.com/juju/juju/pull/10603
[01:02] <kelvinliu> wallyworld: yep looking now
[01:04] <kelvinliu> lgtm thanks
[01:55] <anastasiamac> wallyworld: ask-or-tell add-credential PTAL https://github.com/juju/juju/pull/10604
[05:28] <thumper> https://github.com/juju/juju/pull/10605
[05:30] <thumper> jam ^^
[06:15] <wallyworld> hpidcock: did you need a review of your draft PR?
[06:15] <hpidcock> wallyworld: if you want, I think that would be good seeing as I'm still writing tests, so if something needs to change I'd rather do it now
[06:16] <wallyworld> ok
[06:16] <wallyworld> for tomorrow, i have the next actions PR up
[06:17] <kelvinliu> wallyworld: got 2mins HO? wanna confirm one thing about rbac.
[06:17] <wallyworld> sure
[06:18] <wallyworld> kelvinliu: in standup
[06:18] <kelvinliu> wallyworld: me2. in different room?
[06:22] <wallyworld> hpidcock: got to go AFK until team meeting, will look at PR after that
[06:24] <hpidcock> np no rush at all
[10:31] <stickupkid> achilleasa, CR https://github.com/juju/python-libjuju/pull/355 ?
[10:36] <stickupkid> achilleasa, yeah good shout, i'll fix that
[11:09] <stickupkid> achilleasa i updated and fixed
[11:36] <Parlos> Im deploying Openstack using the bundle (61), all looks fine in 'juju status'. But when I try to upload an image, I get "Error finding address for... Broken pipe". Found a bug report,https://bugs.launchpad.net/glance/+bug/1833009. which seemed to have a similar problem. It was however solved, so Im wondering if the issue in the 'bug' has been addre
[11:36] <Parlos> ssed in the current bundle, and/or this could be something else...
[11:36] <mup> Bug #1833009:  openstack image create fails with [Errno 32] Broken pipe  for openstack rocky and stein <glance> <juju> <openstack> <Glance:New> <https://launchpad.net/bugs/1833009>
[12:54] <magicaltrout> i'm not sure whats more broken
[12:54] <magicaltrout> the uk political system
[12:54] <magicaltrout> or my attempts to test juju on k8s
[12:54] <magicaltrout> https://discourse.jujucharms.com/t/cant-bootstrap-internal-k8s/2032/3
[12:54] <magicaltrout> if anyone has any ideas
[12:55] <magicaltrout> (we all know the correct answer is the uk political system)
[13:00] <stickupkid> magicaltrout,  the uk political system <- this
[13:03] <danboid> What happened to juju-gui / juju-quickstart? Is it dead?
[13:04] <magicaltrout> juju gui is still juju gui
[13:04] <rick_h> danboid:  basically, the gui is in maintenance mode while they do a new gui tool for management
[13:04] <magicaltrout> juju-quickstart is conjure-up now
[13:04] <magicaltrout> ish
[13:04] <magicaltrout> or whatever rick_h says... he clearly knows
[13:11] <danboid> After having a quick look at the conjure-up site, I don't think it is a (web) UI to juju, more like a wrapper of some sort?
[13:11] <danboid> It obvs depends on juju
[13:11] <rick_h> yea
[13:14] <magicaltrout> well juju gui exists if you've got a bootstrapped controller
[13:14] <magicaltrout> you just run
[13:14] <magicaltrout> juju gui
[13:14] <magicaltrout> its just not getting love from the devs
[13:36] <danboid> When you run 'juju register' what does it do? ie why is it taking multiple minutes on my i7 w/ 16GB RAM, gigE etc to register
[13:38] <danboid> I expected it would've been instantanous? Maybe its gone wrong?
[13:38] <danboid> It asked me for a password and the controller name but that was a good few minutes ago
[13:45] <rick_h> danboid:  it's trying to reach out to the controller and login
[13:48] <danboid> rick_h, Seems it failed. What port needs to be open on the controller?
[13:49] <danboid> ERROR Provided registration token may have been expired.
[13:50] <danboid> but it took several  minutes to show that
[13:53] <danboid> 17017 ?
[13:54] <rick_h> danboid:  the normal 17017 yea
=== ISDADS\sgs548_ is now known as danboid
[15:44] <stickupkid> rick_h, another merge forward of changes pylib https://github.com/juju/python-libjuju/pull/356
[15:45] <rick_h> stickupkid:  +1
[15:45] <stickupkid> rick_h, ta
[15:52] <jhobbs> rick_h: we're seeing this when attempting to bootstrap juju against openstack; any ideas? http://paste.ubuntu.com/p/FbVmmJv8xX/
[15:52] <rick_h> jhobbs:  looking
[15:52] <jhobbs> i'm not sure how key management with juju and openstack works; openstack doens't show any keypairs associated with the instance
[15:53] <rick_h> jhobbs:  have you tried to clear the ssh key in known_hosts for 10.244.32.187 on the client?
[15:54] <rick_h> jhobbs:  quick glance it looks like the VM comes up, gets an IP, and the client attempts to connect to the controller over the IP and fails due to an existing (different key) for the controller IP
[15:55] <jhobbs> yeah so it's using that tmp file for keys
[15:55] <jhobbs> which juju owns
[15:55] <jhobbs> /tmp/juju-known-hosts764870299:1
[15:55] <jhobbs> if i remove the key with the command it suggests, I get this instead:
[15:55] <jhobbs> 15:55:34 DEBUG juju.provider.common bootstrap.go:576 connection attempt for 10.244.32.187 failed: No RSA host key is known for 10.244.32.187 and you have requested strict checking.
[15:55] <jhobbs> Host key verification failed.
[15:56] <rick_h> jhobbs:  oic, hmmm not seen anything with that to date.
[15:56] <rick_h> jhobbs:  is there an entry in that file?
[15:56] <rick_h> jhobbs:  in /tmp/juju-known-hosts764870299 ?
[15:57] <jhobbs> let me see
[15:59] <jhobbs> 10.244.32.187 ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCzZr0m8iigEmkMoZva1pdaJ7U9eC61yg+wwq1isIbZPokHnBBGSKq74KojG8MJOVYSO2eeAharfGIXxfdHtqy6/5DFOF0SfL2IhVz3rDvBBGmuL1OrNO9vcZn/SNRK2ZaJm82r3BsA2M6kcJFxeq+PZ8gukcaqYAGq269Pz5+QWueVKHbiIQEPaLhuhDI+AnaqoGtmldz38xohvAglRfDTJtSfrHZzyley/3wLjZ+kC7IGeoWhGQ5pG6Sl+jjGoYom4GANDUFUDFIXxMfE/w0TCZbR6YeOliEjZJshzO4fM9fOgbxPZHkgOcj7k4jtNeJeOez7x4cKTB7G/ZN9N9E7 juju-bootstrap
[16:00] <jhobbs> maybe juju prepopulates that file with the key for the instance? maybe it gets it from the openstack api?
[16:01] <hml> jhobbs: there’s an ssh key in the cloud init used to create the instance.
[16:02] <hml> no keys via the openstack api directly
[16:02] <jhobbs> ok
[16:03] <jhobbs> so maybe it's not getting that cloud-init
[16:03] <hml> jhobbs:  bootstrapping to checkout a few things
[16:04] <hml> jhobbs:  there is a key created to use during bootstrap.
[16:06] <jhobbs> ok
[16:06] <jhobbs> I think the instance isn't getting the metadata for some reason
[16:06] <jhobbs> the cloud-init userdata from the metadata server
[16:08] <hml> then another key once it’s up for system
[16:16] <stickupkid> rick_h, achilleasa, the last pylibjuju commit around bundle changes https://github.com/juju/python-libjuju/pull/357
[16:16] <rick_h> hml:  thanks for helping out, I've got to get ready to go to that family thing and will be afk for a bit
[16:17] <hml> jhobbs: what’s odd too, is that the tmp file is created, used and removed during bootstrap
[16:18] <jhobbs> hml: right
[16:18] <jhobbs> hml: i think the instance is generating its own ssh server key because it's not getting the one from metadata
[16:18] <jhobbs> hml: so it's getting a mismatch
[16:18] <hml> jhobbs:  are you using the edge snap?
[16:18] <jhobbs> no hml, 2.6.8
[16:25] <hml> jhobbs:  i can’t reprod myself with openstack  ; but i do get it trying to directly ssh to the controller instance.
[16:28] <hml> though juju ssh works… it’s using a different key… so there are 3 over the process of bootstrap and configuring a machine.
[16:39] <hml> jhobbs: what’s configured via the model_defaults.yaml  ?
[16:53] <achilleasa> stickupkid: approved; on a sidenote, the relevant juju PR enountered CI errors on merge
[16:54] <stickupkid> achilleasa, :(
[16:56] <stickupkid> achilleasa it was an intermittent failure
[22:25] <wallyworld> babbageclunk: can you jump in standup HO?
[22:25] <babbageclunk> sure sure