Thank you Rick. You pointed me to the right direction.
Whichever node that was created via Juju will have the SSH credential
from Juju's machine, not Maas'. One can use the plain $ ssh
ubuntu@node-ip to access.
Btw, there is no need to remove the SSH key in MAAS, which is still
useful when
What would happen if the update-status hook hangs here? I know it only is
supposed to be for short-duration status messages (but charm bugs are known
to happen).
In addition, it will also block other hooks/actions from happening until
completed and it will remain in a stuck state with the status
What would happen if the update-status hook hangs here? I know it only is
supposed to be for short-duration status messages (but charm bugs are known
to happen).
In addition, it will also block other hooks/actions from happening until
completed and it will remain in a stuck state with the status
Hi Feng, what method were you using to ssh to the Juju node?
When you bootstrap with juju it will grab local ssh keys to setup for the
ubuntu user on the juju managed nodes. For example, I temporarily removed
my ssh key from my MAAS user profile and bootstrapped from my laptop a new
controller
Hi Juju,
I ran into an issue which I couldn't figure out. I setup a MAAS
controller, can manually provision node directly using MAAS and was able
to ssh to it, so I suppose MAAS is all working well.
Then if I use $ juju deploy to start a node, I could not ssh to this
node. What is the right
All agents start up in DEBUG until they can talk to the controller and read
what the current logging config is set to. Otherwise you wouldn't be able
to debug startup issues.
That said, I think there was a request to cache the last-known value in
agent.conf which would let restarts be less noisy.
All agents start up in DEBUG until they can talk to the controller and read
what the current logging config is set to. Otherwise you wouldn't be able
to debug startup issues.
That said, I think there was a request to cache the last-known value in
agent.conf which would let restarts be less noisy.
+1
On Fri, May 19, 2017 at 4:13 AM, Tim Penhey
wrote:
> Hi folks,
>
> Currently juju will update the status of any hook execution for any unit
> to show that it is busy doing things. This was all well and good until we
> do things based on time.
>
> Every five minutes
+1
On Fri, May 19, 2017 at 4:13 AM, Tim Penhey
wrote:
> Hi folks,
>
> Currently juju will update the status of any hook execution for any unit
> to show that it is busy doing things. This was all well and good until we
> do things based on time.
>
> Every five minutes
On Fri, 19 May 2017 at 03:14 Tim Penhey wrote:
> Hi folks,
>
> Currently juju will update the status of any hook execution for any unit
> to show that it is busy doing things. This was all well and good until
> we do things based on time.
>
> Every five minutes (or so)
Hi folks
That time of the week again - almost beer o'clock for those of us in Aus/NZ
timezones - and also time to recap on the happenings in the land of Juju
development over the past 7 days.
We're working hard to get a Juju 2.2 out the door. The week saw a release of 2.2
beta4 which included
On 19 May 2017 at 03:13, Tim Penhey wrote:
> Hi folks,
>
> Currently juju will update the status of any hook execution for any unit to
> show that it is busy doing things. This was all well and good until we do
> things based on time.
>
> Every five minutes (or so) each
On 19 May 2017 at 03:13, Tim Penhey wrote:
> Hi folks,
>
> Currently juju will update the status of any hook execution for any unit to
> show that it is busy doing things. This was all well and good until we do
> things based on time.
>
> Every five minutes (or so) each
+1
On Fri, May 19, 2017 at 6:10 AM David Britton
wrote:
> +1 from me: https://bugs.launchpad.net/juju/+bug/1530840
>
> :)
>
> On Thu, May 18, 2017 at 8:13 PM, Tim Penhey
> wrote:
>
>> Hi folks,
>>
>> Currently juju will update the status
14 matches
Mail list logo