Matt Bruzek

Something is wrong with my conjure-up-localhost-763 controller. I am not able to list the models nor can I add a model, each command hangs for me. ``` $ juju status...

@battlemidget this error left the localhost controller running on my system. I am unable to destroy it using juju commands: ``` $ juju destroy-controller conjure-up-localhost-763 WARNING! This command will destroy...

kill-controller does not work either: ``` $ juju kill-controller conjure-up-localhost-763 WARNING! This command will destroy the "conjure-up-localhost-763" controller. This includes all machines, applications, data and other resources. Continue? (y/N):y ERROR...

Hey @battlemidget I installed conjure-up from the beta channel (2.1.2 Rev 120) and tried to "conjure-down" today. The terminal appears to hang, and when I hit return I get a...

@battlemidget I can confirm that after I entered the password for the other controller, I was able to conjure-down the model that was deployed

Yeah I also got this same error (twice) on my Windows machine, Chrome browser Version 56.0.2924.87 (64-bit). I don't know how to debug Javascript when it comes to this error....

I got the error a third time on Windows, and this time I was up-to-date. Version 57.0.2987.133 (64-bit) Google Chrome is up to date.

I think we should discuss having one config file with many contexts. We can use the `kubectl config ` subcommand to create contexts for each environment rather than having separate...

Actually @marcoceppi wouldn't it be better if we just distilled these into actual `kubectl config` commands? That way if the data format changes we could be less broken. ``` kubectl...

I would like to point out that you may be able to use the `exclude` and `ignore` keys in your layer.yaml to achieve the desired outcome. Please read https://github.com/juju/charm-tools/blob/master/doc/source/build.md#layeryaml