[01:36] <tlm> any idea how to fix this warning when building juju "failed to update distro info: open /usr/share/distro-info/ubuntu.csv: no such file or directory"
[01:42] <wallyworld_> tlm: update deps, there was a bug in juju/os
[01:42] <wallyworld_> that or install distro-info dep
[01:42] <tlm> ah sweet
[01:47] <hpidcock> tlm: stickupkid: I think landed a fix to develop
[01:47] <hpidcock> on k8s we don't have the apt package installed
[01:47] <hpidcock> so the error was happening
[01:48] <hpidcock> also on centos
[03:36] <wallyworld_> thumper: were you looking for a new 2.7 sha for QA testing?
[03:37] <thumper> wallyworld_: why did we need another? rick_h_ said he had passed on the previous one
[03:37] <wallyworld_> thumper: you asked for the race fix to be targetted to 2.7
[03:38] <thumper> wallyworld_: ah, no
[03:38] <thumper> we don't need that for 2.7.5
[03:38] <thumper> just that if we are going to fix it, should do it on that branch first
[03:38] <thumper> since we know the problem is there too
[03:38] <wallyworld_> yup, no worries, just wanted to clarify
[03:38] <wallyworld_> i was hoping we would not do a new sha
[04:26] <thumper> Review for anyone that feels the need: https://github.com/juju/juju/pull/11350
[04:26] <thumper> or desire
[04:26] <thumper> or whatever
[04:26] <wallyworld_> ok
[04:27] <thumper> wallyworld_: thanks
[04:28] <thumper> wallyworld_: it may be easier to review the commits one by one
[04:28] <thumper> I made sure they made sense individually
[04:28] <wallyworld_> because you care
[04:28] <thumper> yes, I care
[04:28] <thumper> they even have decent commit messages
[04:28] <thumper> IMO
[04:29] <wallyworld_> not too shabby
[04:39] <hpidcock> wallyworld_: found the bug
[04:39] <hpidcock> you approved it :)
[04:40] <wallyworld_> oh :-(
[04:40] <tlm[m]> :(
[04:40] <hpidcock> I'm assuming daemonset support was only in develop?
[04:40] <hpidcock> or did it get backported to 2.7?
[04:40] <wallyworld_> yeah
[04:40] <wallyworld_> only develop
[04:41] <hpidcock> sweet, unreleased bug then
[04:41] <wallyworld_> what was it?
[04:41] <hpidcock> ensureStatefulSet was missing else { return nil } on the create
[04:41] <hpidcock> so it would create
[04:41] <hpidcock> then immediately update it
[04:42] <wallyworld_> bollocks
[04:42] <hpidcock> I was this "" close to thinking it was a k8s bug
[04:43] <wallyworld_> so that explains all the symptoms?
[05:06] <hpidcock> wallyworld_: at least the deployment failure
[05:13] <wallyworld_> thumper: lgtm with a few comments
[05:21] <thumper> thanks
[05:21] <thumper> I'm EODing, and away tomorrow, will look Thursday
[05:21] <wallyworld_> enjoy the drive
[06:42] <wallyworld_> jam: did you want to land your jujuc PR and we can pick it up? easier than forking and re-proposing
[06:43] <wallyworld_> we can do the common socket code refactor etc
[06:43] <jam> wallyworld[m]: sure
[06:43] <wallyworld_> ty
[07:11] <flxfoo> Hi all
[07:12] <flxfoo> how do I see all permissions for  a user? I have two superuser but only one can perform system calls, the other one receives permission denied...
[07:39] <wallyworld_> flxfoo: juju show-model will show the users with acess to that model and what permissions they have
[07:39] <wallyworld_> juju show-user <fred> will also show a specific user
[07:43] <flxfoo> wallyworld_: thanks
[07:46] <flxfoo> wallyworld_: I tried to automate the backup (percona-cluster run-action backup) of the percona cluster, with  a cronjob.. at the end user needs to be superuser+admin ... any other idea to do that?
[07:49] <wallyworld_> flxfoo: i can't recall what level of permission is needed to run an action. i can try it
[07:54] <wallyworld_> flxfoo: i just tested a user with write access to a model containing a deployed application, and that user could run an action on that app
[09:08] <achilleasa> jam: I pushed the PR for relation-created. Can you take a look? https://github.com/juju/juju/pull/11341
[09:09] <achilleasa> manadart: if curious how I worked around that interface limitation that we were chatting about you might also want to take a look at ^
[09:16] <manadart> achilleasa: Ack, will take a look.
[09:29] <flxfoo> wallyworld_: mmm interesting... and just calling `run()` ?
[09:31] <wallyworld_> flxfoo: "juju run-action" on a client
[10:00] <wallyworld_> hpidcock: lgtm with a question about cm generations
[10:00] <wallyworld_> i don't quite get how we handle a mismatch
[10:22] <stickupkid> manadart, is anyone calling UpdateSpace, from my initial grepping, it seems like update-space and UpdateSpace method do nothing, is that correct?
[10:23] <stickupkid> manadart, seems like I could propose a PR to remove old stuff at the very least
[10:24] <manadart> stickupkid: Yes, I believe there are some commands not implemented that date from the spaces MVP.
[10:24] <stickupkid> manadart, let me do that first, it's very confusing to have UpdateSpace that will panic
[10:31] <stickupkid> manadart, https://github.com/juju/juju/pull/11353
[10:42] <stickupkid> manadart, I've got some other dead code to remove, if you've got a sec
[10:43] <manadart> stickupkid: Yep.
[11:02] <stickupkid> manadart, https://github.com/juju/juju/pull/11353 <- removed - I have a question about this though (https://github.com/juju/juju/pull/11353/files#diff-bfb621f2a13c2cf9efe1d5eaee1a31c7), everything else came out clean
[11:06] <manadart> stickupkid: I'd remove that method from API too.
[11:06] <stickupkid> manadart, agreed, just wanted another set of eyes
[11:08] <stickupkid> manadart, done
[11:22] <flxfoo> wallyworld_: no sorry I meant, if I `run('ls -l')  on remote machine, I have permission denied
[11:59] <manadart> stickupkid: https://github.com/juju/juju/pull/11354.
[12:00] <stickupkid> manadart, you can delete the checklist from the PR, it's just away to make you remember :D
[12:01] <manadart> stickupkid:
[12:01] <manadart> Done.
[12:05] <stickupkid> manadart, done
[12:11] <jam> stickupkid: any chance you could help me understand an issue with compiling Juju for windows?
[12:11] <stickupkid> jam, of course
[12:11] <stickupkid> daily?
[12:11] <jam> sure
[12:54] <stickupkid> manadart, do we want `juju move-to-space db-space 172.31.1.0/28 172.31.16.0/20` or `juju move-to-space db-space id1 id2`?
[13:08] <stickupkid> jam, "success"
[13:32] <jam> stickupkid: indeed :0
[14:53] <achilleasa> rick_h_: this is how the who-departed will work: https://paste.ubuntu.com/p/KVFDYrhnXQ/ did I miss anything?
[15:06] <stickupkid> manadart, if I use SubnetsByCIDR to gather the tags for calling MoveSubnets, what's a tag in the params.SubnetsResults?
[15:06] <stickupkid> manadart, the ID?
[15:06] <manadart> stickupkid: Yes.
[15:06] <stickupkid> yolo
[15:06] <stickupkid> that's not confusing, tags are IDs
[15:06] <stickupkid> :|
[15:07] <rick_h_> achilleasa:  looking
[15:08] <rick_h_> achilleasa:  is that first number the relation id?
[15:08] <achilleasa> yes this is a debug log entry
[15:08] <rick_h_> achilleasa:  that looks right to me
[15:08] <achilleasa> the plan is to expose the departing unit to charms via the JUJU_DEPARTING_UNIT envvar
[15:09] <achilleasa> (only present when running relation-departed hooks)
[15:10] <rick_h_> achilleasa:  +1
[15:19] <achilleasa> rick_h_: is this the bug we are targeting or is there a newer one out there? https://bugs.launchpad.net/juju-core/+bug/1417874
[15:19] <mup> Bug #1417874: [RFE] Impossible to cleanly remove a unit from a relation <canonical-is> <charms> <feature> <hooks> <sts> <sts-rfe> <juju:Triaged> <juju-core:Won't Fix> <https://launchpad.net/bugs/1417874>
[15:21] <rick_h_> achilleasa:  let me check. I think I added the one to the checklist on the main card
[15:21] <rick_h_> achilleasa:  yea, that's the right looking one
[15:22] <achilleasa> rick_h_: cool; I will mark that as in-progress
[15:23] <rick_h_> achilleasa:  woot woot
[15:33] <stickupkid> manadart, why do these exist here? https://github.com/juju/juju/blob/develop/core/network/space.go#L26-L49
[15:37] <manadart> stickupkid: Not sure where those are used in conversion, but they might be better closer to usage...
[15:37] <stickupkid> manadart, yeah, these aren't core, esp. if we want to rip out the CLI, thise makes it super hard
[15:38] <stickupkid> oh god, they're like fucking view models and core models - yikes
[15:39] <stickupkid> manadart, got a sec
[15:39] <stickupkid> ?
[15:40] <manadart> stickupkid: Yep.
[16:08] <flxfoo> hi all,
[16:08] <flxfoo> we have an issue with rackspace, when trying to deploy a new unit we have "cannot run instance: failed to run a server with nova.RunServerOpts{Name:"juju-00f9f6-v5-prod-50", FlavorId:"general1-2", ImageId:"6e731e8e-ff3d-4e27-be6c-147fde688b7c", UserData:[]uint8{0x1"
[16:09] <flxfoo> where the imageID is no longer available
[16:09] <flxfoo> support told me to use another image ID
[16:09] <flxfoo> but I don't know how to tell juju to use that new image ID...
[16:09] <flxfoo> any idea?
[17:16] <achilleasa> I think I just found the function with the longest signature in juju! https://github.com/juju/juju/blob/develop/worker/uniter/runner/context/export_test.go#L156
[17:16]  * rick_h_ dies just a little more inside
[17:16] <rick_h_> wow, that...is impressive
[17:17] <achilleasa> Its call-site is even more impressive: https://github.com/juju/juju/blob/develop/worker/uniter/runner/context/env_test.go#L113
[17:18] <achilleasa> I will ... structurify it :D
[17:19] <rick_h_> hah, good luck!
[17:19] <achilleasa> I need to add an extra field there so...
[20:10] <flxfoo> hi all
[20:10] <rick_h_> howdy flxfoo
[20:10] <flxfoo> I find the reference if the "bad" image Id in /var/lib/juju/bootstrap-params file in the controller instance
[20:11] <flxfoo> refered as a custom-image-metada
[20:11] <flxfoo> can I remove or change that value?
[20:13] <rick_h_> flxfoo:  normally that's set via controller-config I believe. Is this a running controller?
[20:16] <flxfoo> rick_h_: yeah running controller
[20:17] <rick_h_> flxfoo:  ok, let me dbl check if it's model-config or controller-config you'd set to change that value
[20:18] <flxfoo> rick_h_: I have neither that key in controller-config nor model-config :(
[20:19] <flxfoo> or I don't look at the  right place?
[20:20] <rick_h_> flxfoo:  yea, refreshing. I think you're into https://discourse.jujucharms.com/t/cloud-image-metadata/1137
[20:20] <rick_h_> flxfoo:  which is using the metadata-source arg on bootstrap.
[20:21] <rick_h_> flxfoo:  and you can see some metadata related config in the model-config `juju model-config | grep meta`
[20:21] <rick_h_> flxfoo:  I'd be curious what those are currently set to?
[20:22] <flxfoo> rick_h_: agent-metadata-url defalt ""
[20:22] <flxfoo> rick_h_: agent-metadata-url default ""
[20:22] <flxfoo> rick_h_: container-image-metadata-url default ""
[20:23] <flxfoo> rick_h_: image-metadata-url default ""
[20:23] <flxfoo> that's what I got
[20:23] <flxfoo> I think the issue is related to that thread https://discourse.jujucharms.com/t/rackspace-cloud-london-region-missing-images/1339/5
[20:24] <flxfoo> where had been applied a "temporary" fix... using simplestream... and I think it should revert... but I don't know how... :(
[20:24] <rick_h_> flxfoo:  oh ok, good question.
[20:24] <flxfoo> this `custom-image-metadata should probably be empty or so..
[20:25] <flxfoo> rick_h_: I suppose if I change that `bootstrap-params` file that won't change anything... right?
[20:29] <rick_h_> flxfoo:  yea looking. I'd not expect that to do anything now that bootstrap is over. Since it's a bootstrap arg, and not config, it's not really a thing that's got a knob for "changing it"
[20:29] <rick_h_> flxfoo:  so trying to validate if there's a clear path to changing it or not. I'd hate to bork things even more.
[20:30] <flxfoo> rick_h_:ok thanks... do you a location where i could check that as well? or is it source code only?
[20:31] <rick_h_> flxfoo:  yea in this case I'm just poking at source trying to see
[20:31] <flxfoo> rick_h_: k
[20:31] <rick_h_> flxfoo:  honestly might have to wait and ask wallyworld for his expertise in this area
[20:31] <flxfoo> and he is the one who was appearing in the thread... so...
[20:32] <flxfoo> rick_h_: is he around sometime... better tomorrow?
[20:32] <rick_h_> flxfoo:  he'll be online in the next couple of hours
[20:33] <flxfoo> ok will try to wait a little then... thanks for your time... I though i was going crazy... (not to mention the quarantine)
[20:33] <flxfoo> maybe you could answer that following question though...
[20:34] <flxfoo> so i have this `custom-image-metadata` with at least a image id which is causng trouble because not theire anymore...
[20:34] <flxfoo> then the following lines defines the regions etc...
[20:35] <flxfoo> controller-cloud: name:rackspace. etc... regions etc...
[20:35] <rick_h_> right, that's the general cloud definition baked in. It tells the contrller things like api endpoints to use/etc
[20:36] <flxfoo> I suppose that custom-image-metadata is taking precedence on the that following list... am I making a correct assumption?
[20:37] <rick_h_> flxfoo:  well it's filling in the images specific data and not everything there. It can't refer to a region that the cloud list doesn't know about, for instance
[20:37] <rick_h_> flxfoo:  but it's tied together for sure
[20:38] <flxfoo> custom-image-metadata: '[{"id":"6e731e8e-ff3d-4e27-be6c-147fde688b7c","virt":"pvhvm","arch":"amd64","version":"18.04","crsn":"LON","region":"LON","endpoint":"https://lon.identity.api.rackspacecloud.com/v2.0/"}]'
[20:39] <flxfoo> here it would tell to use that particular image in case of region LON endpoint reached...
[20:39] <rick_h_> flxfoo:  right so that's saying that image is avilable in that region
[20:39] <flxfoo> ok
[20:39] <rick_h_> flxfoo:  there could be more images with different architectures/etc as well.
[20:39] <rick_h_> flxfoo:  in particular different ubuntu series like 14.04, 16.04, 18.04 but we know not all regions have the same things, etc
[20:40] <flxfoo> rick_h_: that's my point, the URL (thread) I posted was saying that for some time images were not available for LON region... so a custom bootstrap was made... then the images are then available... but the controller does not know about it
[20:41] <flxfoo> I am curious what would look like a setting when images are provided by region...
[20:42] <rick_h_> flxfoo:  right, so this gets interesting as the use case for htis is more bootstrapping on openstack and defifining things for that. I'm not sure how it's mutated/managed over time
[20:42] <rick_h_> flxfoo:  in theory all this data should be pulled from an online stream url. If the stream is valid, and Juju is looking at that url, it might just be a cause of removing this.
[20:43] <rick_h_> flxfoo:  but in looking at the code a metadata directory is setup on the machine and such so I think there's more to it than that
[20:43] <rick_h_> so that's where I don't want to mess you up and wait for wallyworld
[20:43] <flxfoo> rick_h_: exactly... obviouslly it is not manageable, because now that rackspace upgraded their images (That I suppose is my issue) then my model is just no its own,  I can not deploy or up.dwon scale anything
[20:44] <rick_h_> flxfoo:  yea :( maybe you can use that model config to set the image-metadata-url to the official one?
[20:44] <flxfoo> rick_h_: ok thanks...
[20:44] <rick_h_> flxfoo:  but it's not clear who wins priority atm
[20:45] <flxfoo> rick_h_: right, well I have to check... would it be the images endpoint url?
[20:46] <flxfoo> rick_h_: (if I cURL rackspace api I can get a list of available images)
[20:46] <rick_h_> flxfoo:  so I was thinking the model-config parameter image-metadata-url
[20:46] <rick_h_> flxfoo:  we can test this by adding a new model if you can?
[20:46] <rick_h_> and then set that value, and see if you can `juju add-machine`
[20:47] <flxfoo> rick_h_: I suppose I won't interfere with the current model?
[20:47] <flxfoo> rick_h_: sorry I am a bit new to juju...
[20:47] <flxfoo> rick_h_: what are the risks? :p
[20:48] <rick_h_> flxfoo:  right, but doing it in a new model we're reducing any risk
[20:48] <rick_h_> flxfoo:  once we're done with the test we can just remove the model
[20:49] <flxfoo> rick_h_: sure I got that, not playing with the current model but a new one...
[20:51] <flxfoo> rick_h_: I don't have any config to pass to a new model though
[20:55] <rick_h_> flxfoo:  do you know the url that rackspace hosts for the image data normally?
[20:57] <flxfoo> http://cloud-images.ubuntu.com/releases/streams/v1/com.ubuntu.cloud:released:rax.json could it be this?
[20:57] <flxfoo> naaaa
[20:57] <flxfoo> sorry
[20:59] <flxfoo>  https://lon.images.api.rackspacecloud.com/v2/<tenantid>/images
[21:00] <flxfoo> through their api...
[21:00] <flxfoo> so you got a json list of image definitions with other details...
[21:00] <rick_h_> hmm, so the question is can you set that in the new model using `juju model-config image-metadata-url="https://lon.images.api.rackspacecloud.com/v2/<tenantid>/images"`
[21:04] <flxfoo> rick_h_:  as the controller has the `tenant-name` + the identity endpoint defined by region , i suppose it should be just https;//lon.images.api.rackspace.com/v2
[21:05] <rick_h_> flxfoo:  yea, might be. That I'm not 100% sure on. one thing we can do is make sure to crank up logging and watch for what it's doing in the actual requests.
[21:06] <rick_h_> flxfoo:  juju model-config logging-config="<root>=DEBUG;unit=TRACE"
[21:06] <rick_h_> well probably not unit-trace
[21:06] <rick_h_> flxfoo:  juju model-config logging-config="<root>=DEBUG;"
[21:10] <flxfoo> rick_h_: can that debug configuration load machines?
[21:11] <timClicks> progress report for last week is live https://discourse.jujucharms.com/2807
[21:12] <rick_h_> flxfoo:  what do you mean by "load machines"?
[21:12] <rick_h_> flxfoo:  it'll make all logging at debug level until it's set back to info
[21:14] <flxfoo> ok
[21:15] <flxfoo> I will try now to see if that gives something
[21:17] <flxfoo> rick_h_: should I add a charm like memcached or something small?
[21:19] <rick_h_> flxfoo:  just `juju add-machine`
[21:19] <rick_h_> flxfoo:  and see if you can get a new machine to come up
[21:22] <flxfoo> ok I have something different
[21:22] <rick_h_> hah, not sure if that's a good sign or a bad one
[21:23] <flxfoo> failed to start machine 0 (multiple networks with label "": [5836eb06-731c-4653-87ac-bebcd97f1a18 dd3389c6-cc70-43bf-a8ec-489be09855cb
[21:23] <flxfoo> :)
[21:24] <flxfoo> To resolve this error, set a value for "network" in model-config or model-defaults;
[21:24] <flxfoo> or supply it via --config when creating a new model), retrying in 10s (10 more attempts)
[21:25] <rick_h_> flxfoo:  ok, so have to set the model value for that
[21:25] <rick_h_> flxfoo:  exactly
[21:25] <rick_h_> flxfoo:  so have to add that to the model-config for our test model
[21:25] <rick_h_> flxfoo:  juju model-config network=XXXXXX (not sure which one you want)
[21:27] <flxfoo> rick_h_: wait not sure what I am suppose to put here
[21:29] <rick_h_> flxfoo:  one of those uuids from above
[21:30] <rick_h_> flxfoo:  we might have to check and see if there's a value in your other working model?
[21:30] <rick_h_> flxfoo:  I would assume that was needed there as well
[21:30] <rick_h_> flxfoo:  you can get the current config values by just doing `juju model-config network`
[21:45] <flxfoo> rick_h_: ok passes, but still have the original error line from custom-metadata-url content
[21:45] <flxfoo> :(
[21:50] <flxfoo> rick_h_: so I suppose the custom-metadata-url gets precedence
[22:12] <flxfoo> rick_h_: which code did you look at for `custom-metadata-url`?
[22:18] <babbageclunk> hey timClicks, how should I fix a bug in the docs?
[22:20] <wallyworld> flxfoo: if you bootstrapped with --metadata-source arg, then that custom image metadata is stored in mongo and takes precidence. you'll need to delete those image metadata records. to do that you'll need to turn on the image-metadata feature flag on the controller and on the client. to set on the controller, "juju controller-config features=[image-metadata]". you might need to bounce the controller agent systemd, not sure. then
[22:20] <wallyworld>  on the client, export JUJU_DEV_FEATURE_FLAGS=image-metadata. after that, you can juju metadata delete-image <id>. you can also juju metadata list-images
[22:21] <flxfoo> wallyworld: ok, thanks... I will need to read that several times... :)
[22:22] <wallyworld> sure, it's a bit messy because image metadata manipulation is not something normally exposed out of the box - you need a feature flag enabled and if not done at bootstrap, you need to turn it on afterwards. if anything is unclear, just ask. i would expect there will be questions
[22:23] <flxfoo> wallyworld: thanks a lot... give me a bit time :)
[22:23] <wallyworld> i assume you had custom jsom image metadata at bootstrap time? and you bootstrapped with --metadata-source
[22:24] <wallyworld> in any case, once the feature flag is enabled, you'll have access to add/list/delete custom image metadata commands
[22:24] <wallyworld> to see what your controller is using
[22:29] <flxfoo> wallyworld: correct bootstrapped with --metadata-source (I did not do that personally but the person in charge at the time)
[22:32] <flxfoo> wallyworld: so I understood properly, we will tell the juju client to use the `image-metadata` with the JUJU_DEV_FEATURE_FLAGS env var. Then by setting the related controller config entry `features`... restart the controller agent (which I need to check which process it is)... did I get things right?
[22:33] <flxfoo> wallyworld: I mean , If you undrestand what I am writing... I look tired :)
[22:33] <flxfoo> wallyworld: I think I got the picture...
[22:33] <flxfoo> wallyworld: are you around about that time usually?
[22:36] <flxfoo> wallyworld: the fact that I modified the `image-metadata-url` would have an incidence?
[22:37] <babbageclunk> flxfoo: that sounds right to me - I think wallyworld might have afk'd for a moment
[22:40] <babbageclunk> flxfoo: you can bounce the juju agent on the controller with `sudo systemctl restart jujud-machine-0.service`
[22:40] <babbageclunk> (assuming this is just a one-machine controller?)
[22:40] <flxfoo> babbageclunk: yes
[22:41] <flxfoo> babbageclunk: thanks
[22:41] <wallyworld> flxfoo: sorry, was caught up with something else. yeah, summary is correct. first step is to get the feature flag enabled and use the list-images command to see what the controller is using
[22:41] <flxfoo> wallyworld: nm
[22:41] <wallyworld> tz here is GMT+10
[22:41] <flxfoo> wallyworld: k
[22:43] <wallyworld> to restart the controller agent, ssh into the controller machine (ususally juju ssh -m controller 0) and then restart the juju-machine-0 systemd service
[22:43] <flxfoo> wallyworld: I will try that tomorrow morning.. and will let you know... I think things/issues come from there https://discourse.jujucharms.com/t/rackspace-cloud-london-region-missing-images/1339/5
[22:44] <flxfoo> wallyworld: many thanks, I would not have found that by myself for sure... :)
[22:45] <wallyworld> np, here to help you get this sorted. good that rackspace has complete image metadata but a mess to clean up for sure
[22:45] <flxfoo> wallyworld: and they are not helping... you are... thanks guys
[22:46] <flxfoo> I am out... good night/day :)
[22:46] <wallyworld> ttyl :-)