On 13/06/16 13:56, Rick Harding wrote:
> I've felt like the least oddball of things was to tie the command to
> remove the entry to the command you used to add it and so we've been
> running with unregister.
+1
At one stage we were using login with different parameters instead of
register; I'm
On Mon, Jun 13, 2016 at 7:45 PM Thodoris Sotiropoulos <
theo...@admin.grnet.gr> wrote:
> I checked the entries of the database after the error. Specifically,
> this is the document for the Model collection.
>
> [
> {
> "_id" : "d96ef8ae-36ca-4af7-870f-7914d844df68",
>
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
On 13/06/16 22:58, Rick Harding wrote:
> On Sat, Jun 11, 2016 at 6:32 PM Ian Booth wrote:
>
>> We are also storing any config specified in clouds.yaml separately. These
>> items,
>> such as apt-mirror, are shared between models and are used by default if
>> not
>>
On Sat, Jun 11, 2016 at 6:32 PM Ian Booth wrote:
> We are also storing any config specified in clouds.yaml separately. These
> items,
> such as apt-mirror, are shared between models and are used by default if
> not
> specified in a hosted model. But you can override any
On Sat, Jun 11, 2016 at 11:33 AM Mark Shuttleworth wrote:
> On 10/06/16 19:20, Cheryl Jennings wrote:
> > - Addition of a `juju unregister` command to remove references to
> > controllers
>
> Seems we have two different cases
>
> * the opposite of register
> * the opposite of
I checked the entries of the database after the error. Specifically,
this is the document for the Model collection.
[
{
"_id" : "d96ef8ae-36ca-4af7-870f-7914d844df68",
"life" : 0,
"migration-mode" : "",
"name" : "test",
"owner" : "admin@local",