Re: I think master is leaking

If the test suite panics, especially during a tear down from a failure set up, you leak mongos and data in /tmp. I have a cron job that runs a few times a day to keep this leaking below a few gig. On Sat, Apr 9, 2016 at 8:13 AM, Horacio Duran wrote: > Hey, this is

Re: charmstore client authentication(help! :) )

> On Apr 8, 2016, at 11:56 , Tom Barber wrote: > > Hi Martin > > Thanks for reaching out, a solution to keep me moving would be much > appreciated. > > In an ideal world, you guys could delete the f-tom-n charms, they are old > duplicates of whats in spicule

sync-tools downloads to controller?

Barring the use of a local download ('--destination'), does 'sync-tools' download to a cloud's controller? If so, confirm there is no necessity to invoke again before an 'upgrade-juju' of another of the controller's models? -- Peter Matulis CDO Documentation Canonical -- Juju-dev mailing list

Re: charmstore client authentication(help! :) )

Hi Martin Thanks for reaching out, a solution to keep me moving would be much appreciated. In an ideal world, you guys could delete the f-tom-n charms, they are old duplicates of whats in spicule nothing more, they are also named the same, so you'll have an interesting merge situation on your

Re: charmstore client authentication(help! :) )

Hi Tom, Sorry about this, being locked out if you change your launchpad username is a limitation of the system that we do know about, and are currently investigating how to fix. We can probably update charmstore's databases manually to use the new username, but it will mean that the charms that

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

On 08/04/16 15:03, Pete Vander Giessen wrote: > @Charles: Aha! The various destroy commands don't have a --force flag; I > didn't know about the "remove-machine" command, which does accept --force. > > That seemed to work. Thank you :-) > We should definitely clean that up in 2.0 final. Mark --

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

Happy to help! Glad it got you sorted. All the best > On Apr 8, 2016, at 10:03 AM, Pete Vander Giessen wrote: > > @Charles: Aha! The various destroy commands don't have a --force flag; I > didn't know about the "remove-machine" command, which does accept --force. > > That

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

@Charles: Aha! The various destroy commands don't have a --force flag; I didn't know about the "remove-machine" command, which does accept --force. That seemed to work. Thank you :-) ~ PeteVG On Fri, Apr 8, 2016 at 9:47 AM Charles Butler wrote: > I haven't

Re: Is there a way to let juju know that an lxc container has gone away and isn't coming back?

I haven't validated this but you can try to remove the machine forcibly Juju remove-machine ## --force That should force removal of the container from the controller and let you destroy-service to remove it from the model. > On Apr 8, 2016, at 8:56 AM, Pete Vander Giessen

Is there a way to let juju know that an lxc container has gone away and isn't coming back?

Hi All, Let's say that someone (okay, me) is experimenting with juju2 (develop) locally, and I've rudely destroyed an lxc container that had a juju charm deployed to it (lxc stop && lxc delete ). Is there a way to convince juju that the charm is no longer deployed? juju destroy-service and juju

[Review Queue] ubuntu-devel, Openjdk, OpenAirInterface LTE eNB-UE simulator, ELK and more...

Hi all, Here is what the big data team has been reviewing the past weeks. April 7, 2016: Cory/Kevin/Kostas - Bird lint fixes - https://code.launchpad.net/~johnsca/charms/trusty/bird/lint/+merge/287962 - Fixes lint errors - Merged - haproxy

Re: charmstore client authentication(help! :) )

I'm a company of one currently so it doesn't matter a great deal also I didn't know you could do such a thing on Launchpad :) Sorry! Misunderstood, I went looking for a debug method. I got it built but I don't understand go enough to setup the debugger, I just wanted to prod the webservice to see

Re: charmstore client authentication(help! :) )

While not an answer, I have some hindsight comments. Of you're going to register a company on Launchpad it'd be best to do as a team instead of a user. That way other users could be added and removed from that team without breakage. Finally, I pointed you to the gh repo to file bugs, building it

charmstore client authentication(help! :) )

(apologies juju-dev moderators, sent this to the wrong place) Hi folks, I'm like the guy who just does stuff to annoy developers! :) When I registered for launchpad my assigned name was f-tom-n, when I registered a company for Juju related stuff I changed my launchpad ID to spicule. Last night