Hello,
I'm running juju 1.20.1 on a test maas cluster. Every now and then when I run
juju add-machine the machine gets stuck at pending state (permanently). Maas
shows status as Failed deployment.
Is there a way to force machine state to error so I can retry-provisioning on
it? I don't want to
juju-core 1.21-beta2
A new development release of Juju, juju-core 1.21-beta2, is now available.
This release replaces 1.21-beta1.
Getting Juju
juju-core 1.21-beta2 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
Hello, good people!
How hard would it be to implement 'showing running relations in juju
status'?
Currently there is no easy (if any) way of knowing the state of the
deployment. When one does 'juju add-relation' the relation hooks are
run, but there is no feedback on weather the hooks are still
juju-core 1.21-beta2
A new development release of Juju, juju-core 1.21-beta2, is now available.
This release replaces 1.21-beta1.
Getting Juju
juju-core 1.21-beta2 is available for utopic and backported to earlier
series in the following PPA:
https://launchpad.net/~juju/+archive/devel
FYI, I was able to solve 3 reviewboard-github integration issues today:
1. pull requests for branches other than master now work (e.g. 1.21 backports)
2. no more hitting rate limits (5000 requests/hour limit instead of 60)
3. pull request bodies now get updated with a link to the new review
On 14 November 2014 22:31, Mario Splivalo mario.spliv...@canonical.com wrote:
Hello, good people!
How hard would it be to implement 'showing running relations in juju
status'?
Currently there is no easy (if any) way of knowing the state of the
deployment. When one does 'juju add-relation'
