The tool Andrew has is: https://github.com/axw/juju-tools

I don't know a lot about the parameters, etc of how to use it, but I
believe you would build it, and put the 'juju-tools' binary into your PATH
and then run "juju tools --help".



On Tue, Dec 5, 2017 at 6:24 PM, Matt Dirba <email address hidden> wrote:

> After I bootstrap or upgrade my controller with --build-agent it changes
> the agent-version from 2.2.6 to 2.2.6.1 (I backported the patch), and I am
> able to add machines with the same architecture from my MaaS server, but
> when I attempt to add a machine with a different architecture wild things
> happen.  Every machine matching the constraints is added and then almost
> immediately released once juju realizes that the architecture is different
> and it does not have an agent already built.  Is there a way to hard code
> the build version such that when I bootstrap with build-agent it shows as
> 2.2.6?
>
>
> Regards,
> Matt Dirba
> 512-779-4696
>
> On Mon, Dec 4, 2017 at 9:38 PM, John A Meinel <email address hidden>
> wrote:
>
> > If you can't use the published builds, I believe Andrew Wilkins has a
> tool
> > that lets you cross compile and then upload them to the controller.
> >
> > We should probably look to move that into the official Juju repo under
> > scripts/ so people know where to find it.
> >
> > John
> > =:->
> >
> > On Dec 4, 2017 21:41, "Matt Dirba" <email address hidden> wrote:
> >
> > > How would I build a model agent for a different architectures?  Some of
> > > my test machines are aarch64 and others are amd64.
> > >
> > > --
> > > You received this bug notification because you are subscribed to juju.
> > > Matching subscriptions: juju bugs
> > > https://bugs.launchpad.net/bugs/1729880
> > >
> > > Title:
> > >   juju 2.2.4 and 2.2.6 actions dissappear when state is changed from
> > >   running to complete
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/juju/+bug/1729880/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1729880
> >
> > Title:
> >   juju 2.2.4 and 2.2.6 actions dissappear when state is changed from
> >   running to complete
> >
> > Status in juju:
> >   Fix Committed
> >
> > Bug description:
> >   Description: After 20ish hours of calling actions in a while loop that
> >   take either a minute, 30 minutes, an hour, or 4 hours to run.  The
> >   result of an action disappears and juju loop.run gets stuck in an
> >   infinite loop.
> >
> >   Code:
> >       def run_action(self, unit, action, params):
> >           from juju import loop
> >           app = self.model.units[unit].application
> >           action = loop.run(self.model.applications[app].units[0].
> run_action(action,
> > **params))
> >           logger.info("Running action %s on %s UUID %s with Params %s",
> > action.data['name'],
> >                       action.data['receiver'], action.data['id'], params)
> >           loop.run(action.wait())
> >           self.update_status()
> >           return action
> >
> >       while True:
> >           datetime.now()
> >           self.run_action('sshdefault/0', 'benchmark', params={'time':
> > 1800})
> >
> >   Log from above code with timestamp of the start of the action:
> >       jujubench2.jujubench - 2017-11-02 17:16:00,747 Running action
> > benchmark on sshdefault/0 UUID  b57d6c41-6cf6-4f92-81f1-558887cd2062
> with
> > Params {'time': 1800}
> >
> >
> >   $ juju debug-log -m sshdefault
> >   unit-sshdefault-0: 17:46:47 ERROR juju.worker.uniter resolver loop
> > error: executing operation "run action b57d6c41-6cf6-4f92-81f1-
> 558887cd2062":
> > running action "benchmark": action "b57d6c41-6cf6-4f92-81f1-
> 558887cd2062"
> > not found
> >   unit-sshdefault-0: 17:46:47 ERROR juju.worker.dependency "uniter"
> > manifold worker returned unexpected error: executing operation "run
> action
> > b57d6c41-6cf6-4f92-81f1-558887cd2062": running action "benchmark":
> action
> > "b57d6c41-6cf6-4f92-81f1-558887cd2062" not found
> >
> >   $ juju show-action-status -m sshdefault b57d6c41-6cf6-4f92-81f1-
> > 558887cd2062
> >   ERROR no actions found matching prefix "b57d6c41-6cf6-4f92-81f1-
> > 558887cd2062"
> >
> >   Note: The errors show up in the juju debug-log after the action
> >   completes, but I can not find the action using juju show-action-
> >   status.  This indicates to me that when the action is moved from the
> >   running to completed state it gets lost.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/juju/+bug/1729880/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1729880
>
> Title:
>   juju 2.2.4 and 2.2.6 actions dissappear when state is changed from
>   running to complete
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1729880/+subscriptions
>