Re: CI hates juju, maybe the feelings are mutual

I think without the -- before the -o the position is not relevant, that -- was added in a patch not long ago iirc as a revert of a previous fix, but it does not seem to be doing what is expected. On Thu, Apr 10, 2014 at 9:23 AM, John Meinel wrote: > Note that copying off the all-machines log se

Re: Juju is now on Github

Thanks for the info Ian, you guys have done a wonderful job and have been very helpful during the day. On Tue, Jun 3, 2014 at 8:49 PM, Ian Booth wrote: > Hi folks > > The migration of Juju source from Launchpad to Github is now complete for > phase > one. The final location is at https://github

Re: Getting commit emails now - possible?

This seems to be close to what you want http://stackoverflow.com/questions/8371173/how-to-get-notified-when-someone-pushes-into-a-github-branch On Thu, Jun 5, 2014 at 8:43 PM, Tim Penhey wrote: > Hi All, > > When Juju was on launchpad, I had subscribed to the trunk branch so I > got an email fo

End Of Review marker

Hey, I don't know if this bugs everyone or just me but it happens very often that I am working while people are reviewing my code on gh. While people is reviewing and commenting on the code I keep getting mails and the diff page from the pr keeps changing. To know when its all done and I can finall

Re: End Of Review marker

The idea of the original proposal was, as John says, to act as a chess watch. All the reviews I got so far make much more sense if I read them and answer them as a whole instead of disconnected inline comments. The idea of the EOR comment is to mark the review pass as complete and give place to the

backup/restore broken again

Dear all, backup and restore is yet again broken. In this case: restore for HA Nate suggested that I sent an email at the end of my day to see if anyone wanted to cooperate so here goes a very short report of my findings so far, please excuse the disorder this is data as it streamed form my head.

Re: Running juju tests on windows

ask gsamfira @ freenode he is one of the guys from cloudbase they have a very interesting howto on getting juju working on windows for which I sadly misplaced the link. (I assume it includes the link for the right mongo) On Wed, Jul 16, 2014 at 10:40 AM, David Cheney wrote: > Hello, > > I have

Re: Master has been broken for 4 weeks

Im on the restore bug On Wed, Jul 23, 2014 at 12:38 PM, Nate Finch wrote: > I'm on the nonce.txt bug. > > > On Wed, Jul 23, 2014 at 11:34 AM, Curtis Hovey-Canonical > wrote: >> >> This is the current list of regressions that block a release >> >> C:/Juju/lib/juju/nonce.txt does not exist, bootst

Re: CI regressions will block merges

Since $$fixes-1342937$$ is already committed I changed the state by hand in the bug report sorry I did not do that before, I forgot it was no longer automatic. On Tue, Jul 29, 2014 at 3:05 PM, Curtis Hovey-Canonical < cur...@canonical.com> wrote: > Magicians. > > I have updated the rules that t

determine if juju is upgrading

Hey, I have been running several CI tests lately and find very often the following error: 2014-08-04 22:27:42 ERROR juju.cmd supercommand.go:323 upgrade in progress - At least when my machine is not under heavy load and I am at decent network reach of amazon. I wonder, is there a way to poll juju t

Re: Making peergrouper accept a manual replicaset entry?

take a look at restore, it does that by hand look for rs.config on the code. On Tue, Aug 5, 2014 at 5:33 PM, Wayne Witzel wrote: > A user had some issues after an upgrade put them on the unstable Juju > path. We've been working to get them back on stable and finally have them > upgraded to 1.20

Re: avoiding unnecessarily entering "upgrade mode"

You had my verbal SGTM but have it written also On Tuesday, August 5, 2014, David Cheney wrote: > SGTM. > > On Wed, Aug 6, 2014 at 11:10 AM, Menno Smits > wrote: > > Right now, a Juju machine agent is in "upgrade mode" from the moment it > > starts until the upgrade-steps worker is finished. Du

issuing a jujud restart

Hey, I am currently working on restore command for juju state servers. I find myself in the need, after putting all the back-up parts in place, of restarting jujud, from within jujud. Can anyone shed some light on how to do that? Thank you all. Cheers -- Horacio Durán -- Juju-dev mailing list Juju

Re: getting rid of all-machines.log

Hey, In an effort to move forward with juju's windows integration I have summarized what seems to be the core points of this discussion to the best of my ability (please excuse me if I missed or misunderstood something). The two core points of discussion on this thread are: * should we remove all-m

Re: Is ReviewBoard a good thing?

We will all be seeing each other in 2 weeks we can discuss it then On Friday, September 19, 2014, Eric Snow wrote: > On Fri, Sep 19, 2014 at 7:55 AM, Matthew Williams > > wrote: > > I do think it's too early to tell though. Why not give it another week > or 2 > > then discuss in the cross teams

Re: mongodump/mongorestore and oplog.bson

Well that file should only contain something if the db got changed while you where performing the dump. The usual test db is rather small and one usually is only doing the dump during the test so this becomes a bit hard to achieve. I really would hope the content of oplog.bson are somehow documente

Re: Can we removed all devel agents from released streams.

I can add a bunch of detail, actually: The install was: 1.18.4-trusty-amd64 The persons machine: $ juju --version 1.20.11-trusty-amd64 upgrade was: juju upgrade-juju --upload-tools --version=1.20.11 The resulting files: drwxr-xr-x 2 root root 4096 Jul 29 17:52 1.18.4-trusty-amd64 drwxr-xr-x 2

Re: juju min version feature

Ideally we will provide tools for the user to determine this, unless I understood wrongly the requirement. On Mon, Dec 15, 2014 at 1:55 PM, Rick Harding wrote: > Then we should take up the burden to help others realize that their code > will work with older versions of juju. Perhaps I am assumi

git clients vulnerability found

Heads up people https://github.com/blog/1938-vulnerability-announced-update-your-git-clients apparently there is a vulnerability in git client that might be exploited via pushing certain snippets to the repos. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe at: h

Re: git clients vulnerability found

em, right ? > > On Fri, Dec 19, 2014 at 8:32 AM, Horacio Duran > wrote: > > Heads up people > > > https://github.com/blog/1938-vulnerability-announced-update-your-git-clients > > apparently there is a vulnerability in git client that might be exploited > &

dependency branches for 1.21

Hey, I have been backporting licencing fixes into utils, syslog and testing for 1.21 release. While doing this I noticed that the revs testing and utils used in 1.21 are quite far from what we use in master so, in order to prevent bringing unwanted changes to 1.21 by bumping the deps to HEAD I bran

coloring juju logs a bit

So, for those like me, that usually end up hunting for what broke your tests and find themselves swimming in a sea of log output, I have added a bit of setup to my supercat to get some useful coloring. I most likely will be doing this in a more serious and less hacky (and more juju dev oriented) wa

Re: 1.23-beta1 needs features for release notes.

I have added a section about improvements in backup and restore On Friday, March 13, 2015, Curtis Hovey-Canonical wrote: > Our release notes document is looking sparse. Thank you Anastasia for > keeping me posted. > > https://docs.google.com/a/canonical.com/document/d/1V6AU2mEbTOXQygsn-9eZg-DHjx

Re: restoring juju state

Nope this is not very accurate I believe that you got some parts wrong out of our conversation. I am currently on vacation but upon return I'll submit a writeup with some graphic flows explaining how this all works (the recover part I agree with, in any case what is being recovered/restored is the

Re: restoring juju state

This is a bit rough, I have not had time to make it better or add the other less common use cases or HA but should give a more decent explanation https://docs.google.com/a/canonical.com/document/d/1AtAo-uxED5TvXahJNytF-PIswRv9T0lewcyu699Rpyk/edit?usp=sharing On Wed, Mar 25, 2015 at 3:44 PM, Eric S

Re: coloring juju logs a bit

ittle tool. here is the url https://github.com/natefinch/nolog and here is a sample of output: http://imgur.com/qRuaROh On Fri, Mar 6, 2015 at 2:31 PM, Horacio Duran wrote: > So, for those like me, that usually end up hunting for what broke your > tests and find themselves swimming in a sea

Re: coloring juju logs a bit

to it so it better colors > juju logs would be a win I think. FWIW, I and others in eco have been using > it for a while on a variety of application outputs including juju > > Marco > > On Tue, Apr 28, 2015 at 4:30 PM, Horacio Duran < > horacio.du...@canonical.com > &

Re: Uniter tests for update-status hook - BLOCKER

On 20/07/15 07:57, William Reade wrote: > On Mon, Jul 20, 2015 at 6:42 AM, Tim Penhey > wrote: > > Hi folks, > > Earlier today I was investigating this CRITICAL BLOCKER bug: > https://bugs.launchpad.net/juju-core/+bug/1475724 > > > I'll talk a

Re: workers using *state.State

There is lazy and there is also "I just based in that other worker" which happens, I am the proud parent of statushistorypruner and a rewrite is underway too, sorry. On Tuesday, September 8, 2015, Tim Penhey wrote: > On 09/09/15 11:22, Andrew Wilkins wrote: > > On Wed, Sep 9, 2015 at 6:14 AM Ian

Re: Defaulting tests internal to the package

I have two points, which might be biased by my personal opinion here: 1) API end points tests are good, they exercise that what you are advertising to the public is what you meant, for the cases you are interested. If they are properly coded you should need to export the least amount of things in e

Re: Diffing string checker

You are my new personal hero On Thursday, 25 February 2016, Andrew Wilkins wrote: > Howdy, > > Occasionally I'll change a test, and some string equality test will fail > with a wall of text. Sometimes we shouldn't be checking the whole string, > but sometimes it's legitimate to do so, and it can

Re: LXD support (maybe)

be aware though, iirc that ppa replaces your go version with 1.6 (or used to) which can mess your env if you are using go from ubuntu. On Thu, Feb 25, 2016 at 12:11 PM, Andrew McDermott < andrew.mcderm...@canonical.com> wrote: > I took a quick look through it as I was OCR - comments in RB. > > On

Re: Usability issues with status-history

I think you are attributing too much importance to some data that can hardly be considered information let me try to mention some points that I think are valid here. 1) Not every message is valuable, you state that every message we throw away makes it harder to debug, but certainly a message like "

Re: Unable to kill-controller

I might be biased by years of apt-get but purge makes me think that you are going to do what kill is supposed to do, forget sound more aligned whit what you are really aiming to. On Wednesday, 6 April 2016, Andrew Wilkins wrote: > On Tue, Apr 5, 2016 at 2:29 AM Cheryl Jennings < > cheryl.jenni..

Re: Unable to kill-controller

; kill-controller? > > juju kill-controller --cleanup > > > > On 6 April 2016 at 11:05, Horacio Duran > wrote: > >> >> I might be biased by years of apt-get but purge makes me think that you >> are going to do what kill is supposed to do, forget sound m

Re: Unable to kill-controller

Strong +1 to what Andrew just proposed On Wednesday, 6 April 2016, Andrew Wilkins wrote: > On Wed, Apr 6, 2016 at 7:35 PM Rick Harding > wrote: > >> +1 to the -1 of a new command for this. I'd like to raise the discussion >> with the technical board as I'd like understand why the change the cha

Re: Unable to kill-controller

nds needed). > > On Wed, Apr 6, 2016 at 8:41 AM Horacio Duran > wrote: > >> Strong +1 to what Andrew just proposed >> >> On Wednesday, 6 April 2016, Andrew Wilkins > > wrote: >> >>> On Wed, Apr 6, 2016 at 7:35 PM Rick Harding >>> wrote: &

Re: LXD v2.0.0-rc8 does not work with Juju v2.0-beta3

yes, that workaround works, also you can change /etc/default/lxd-bridge and restart the lxd-bridge service. On Wed, Apr 6, 2016 at 6:12 PM, Casey Marshall wrote: > On Wed, Apr 6, 2016 at 2:51 PM, Alexis Bruemmer < > alexis.bruem...@canonical.com> wrote: > >> >> Hi All, >> >> As recently highligh

I think master is leaking

Hey, this is more of an open question/sharing. I was a good half hour trying to find why reboot test was timeouting and found that I had a couple of lxcs that I dont recall creating (at least one of them was a juju api server) and a good 5-8 mongos running. I killed the test, the mongos and the lxc

a few notes on common windows breaking mistakes.

Hello all, this past week I have spent some time fixing Wintows tests for go 1.6, many errors where caused by http being more strict on what it will take on a Get and therefore many innocent mistakes often made in tests where suddenly not so innocent, so just as a friendly reminder. * Always join

Re: Connecting to the controller database w/mongodb 3.2

By connect I assume you mean to use the shell, for this you need the mongodb-org papa and install mongodb-org-shell, I am currently on the phone but as soon as I get to a computer I'll send you links On Friday, 13 May 2016, Casey Marshall wrote: > I seem to be unable to connect to the Juju 2.0 c

Re: Connecting to the controller database w/mongodb 3.2

rsh...@canonical.com> wrote: > On Fri, May 13, 2016 at 10:52 AM, Horacio Duran < > horacio.du...@canonical.com> wrote: > >> By connect I assume you mean to use the shell, for this you need the >> mongodb-org papa and install mongodb-org-shell, I am currently on the phone >>

Re: Today I submitted 5 PR's to be merged, 3 failed because mongo shat itself

For now we are trying to go around mongo issues that make the tests 100x slower (yes one hundred) once this is fixed we should start using mongo 3.2 exclusively since 2.4 iirc is EOL or near. The issue lies in the new storage engine, which we could skip if mmapv1 ( the old one) wasn't also nearing

Re: go test github.com/juju/juju/state takes > 10 minutes to run

Uh, ill take a look at that, I am the author of said test On Fri, May 20, 2016 at 6:50 AM, roger peppe wrote: > The state tests "only" take 10m26s for me. > > I built a thing to analyse gocheck output > https://play.golang.org/p/veBCtrmmPR > and used it on the state test output. > > total suites

Re: The CI build time continue to rise alarmingly

So as a follow up of this, the fault is in "7fb39bdfbd8a7a668c7db53923836ac42cd640ec" that removed --nojournal from " github.com/juju/testing" mgo.go file, which is good for mongo 3.2 but kills 2.4, this needs to check what version of mongo is running and use flags accordingly, its EOD for me but i

Re: Automatic commit squashing

+1 on Dave's suggestion On Thursday, 16 June 2016, David Cheney wrote: > Counter suggestion: the bot refuses to accept PR's that contain more > than one commit, then it's up to the submitter to prepare it in any > way that they feel appropriate. > > On Thu, Jun 16, 2016 at 6:44 PM, roger peppe

Re: Automatic commit squashing

On second thought, this might be a problem for feature branches but we can device a way to tell the bot that something is a fb On Thursday, 16 June 2016, Horacio Duran wrote: > +1 on Dave's suggestion > > On Thursday, 16 June 2016, David Cheney > wrote: > >> Counter s

Re: Automatic commit squashing

Much like communism, it's still in practice at small territory On Thursday, 16 June 2016, David Cheney wrote: > I thought feature branches, like communism, sounded good but had > failed in practice. > > On Thu, Jun 16, 2016 at 7:06 PM, Horacio Duran > > wrote: > >

about to land a breaking change

I am about to land a change in the way we persist user permissions, this will not change API but existing models/controllers will stop working so please be aware of this before pulling the latest version of the code. -- Juju-dev mailing list Juju-dev@lists.ubuntu.com Modify settings or unsubscribe

Re: about to land a breaking change

This just landed fyi. On Tue, Jun 21, 2016 at 8:36 AM, Horacio Duran wrote: > I am about to land a change in the way we persist user permissions in juju > core master, this will not change API but existing models/controllers will > stop working so please be aware of this before pu

updates in permission handling

As of 02c2b10067bbe2169c2b7a7cfb88c66f9bc69700 in master, there are new permission options available. The current permissions, formerly known as **acls** and used to "**share models**" allow controller administrators to give both internal and external users different permissions in models and cont

Re: Reviews on Github

Also +1 for that source not being review board On Wed, Sep 14, 2016 at 5:23 PM, Reed O'Brien wrote: > Also +1 for a single source of truth. > > On Wed, Sep 14, 2016 at 1:20 PM, Rick Harding > wrote: > >> /me is always +1 on reducing the number of things we have to maintain and >> keeping things

Re: Reviews on Github

I disagree, once the discussion is over and the merge is ready, an amend/squash is in order to avoid useless tree nodes. On Wed, Sep 21, 2016 at 8:41 PM, Reed O'Brien wrote: > Two things I've noticed today while doing OCR duties are: > 1. There's no way to tell if a PR has a review when looking

Re: Reviews on Github

Sep 21, 2016 at 4:43 PM, Horacio Duran < > horacio.du...@canonical.com > > wrote: > >> I disagree, once the discussion is over and the merge is ready, an >> amend/squash is in order to avoid useless tree nodes. >> > You make a good point and I agree with you

Re: Github Reviews vs Reviewboard

+1 to Github, I prefer the papercuts of githubs to the swordcuts from reviewboard. On Fri, Oct 14, 2016 at 12:09 PM, Dimiter Naydenov < dimiter.nayde...@canonical.com> wrote: > +1, Nate said what I was thinking :) > > On 10/14/2016 05:34 PM, Nate Finch wrote: > > +1 > > > > Keeping the PR and rev

Re: Github Reviews vs Reviewboard

Shouldn't we leave it for historic purposes? On Monday, 24 October 2016, Menno Smits wrote: > The votes are in: Github 8, Reviewboard 5. It looks like we stick with > Github Reviews. > > I'm going to email some people now about tearing down the Reviewboard > instance. > > On 15 October 2016 at 0

Re: to symlink or not to symlink?

Yo me the question is, does systems allow this practice? Or at least does it discourage it? If not this sounds a lot like a Maas bug that could potentially bite them with different services. I was not the one to write that code but I know it's written that way to avoid the need to call on systemd r

Re: LXD certificate expiry issue

Is there a but for this in lxd? I believe this is quite a papercut for most users of lxd in local machines. On Mon, Feb 13, 2017 at 4:48 AM, Menno Smits wrote: > Today Juju bootstraps started failing for me with the following error: > > cmd supercommand.go:458 new environ: creating LXD client: G