Hi NAZ,
Like Andrew already pointed out, you can issue `juju deploy your-charm
--to 9` to run your charms.
Then on the juju CLI side, use `juju debug-log` to get a running debug
log. Whatever the charm error is, you should see it flashing across the
screen. Also, hooks and states will be
Hi NAZ,
Like Andrew already pointed out, you can issue `juju deploy your-char
--to 9` to run your charms.
Then on the juju CLI side, use `juju debug-log` to get a running debug
log. Whatever the charm error is, you should see it flashing across the
screen. Also, hooks and states will be run
On Fri, Jun 30, 2017 at 7:39 AM N. S. wrote:
> Hi,
>
> Excuse me if this seems a strange scenario.
>
> My scenario is as follows:
>
> I have a charm that has lots of problems in its install script, needs
> massive change (NOT SURE how to fix it)
>
> So,
>
> I added an empty
Hi,
Excuse me if this seems a strange scenario.
My scenario is as follows:
I have a charm that has lots of problems in its install script, needs massive
change (NOT SURE how to fix it)
So,
I added an empty machine by
Juju add-machine --series Xenial
And then I logged into it by
Juju SSH 9