"juju help plugins" errors on displaying admin, log and deployer info

[Antonio Rosales]

$ ~/go/bin/juju help plugins --debug
2013-08-07 01:18:33 ERROR juju plugin.go:143 'juju-deployer --description': exit status 2
2013-08-07 01:18:34 ERROR juju plugin.go:143 'juju-log --description': exit status 2
2013-08-07 01:18:34 ERROR juju plugin.go:143 'juju-admin --description': exit status 2
Juju Plugins

Plugins are implemented as stand-alone executable files somewhere in the user's PATH.
The executable command must be of the format juju-<plugin name>.

admin error occurred running 'juju-admin --description'
deployer error occurred running 'juju-deployer --description'
log error occurred running 'juju-log --description'
2013-08-07 01:18:34 INFO juju supercommand.go:276 command finished
$ ~/go/bin/juju --version
1.13.1-quantal-amd64

-thanks,
Antonio

[Dave Cheney (dave-cheney)]

oh dear, this is caused by a recent change to plugins which means _all_ flags are passed down to the plugins, non are consumed by the juju command. What is probably happening is we are calling juju-log --debug --description and the plugin is rejecting the unknown flag.

[Antonio Rosales (arosales)]

Is it possible I am seeing this error because I don't have deployer, log, or admin in my path?

-thanks,
Antonio

[Dave Cheney (dave-cheney)]

I don't think so, the cli should only try to execute plugins _if_ they
exist, there is an infinite number of plugins that don't exist, we
don't try those either.

On Wed, Aug 7, 2013 at 5:47 PM, Antonio Rosales
<email address hidden> wrote:
> Is it possible I am seeing this error because I don't have deployer,
> log, or admin in my path?
>
> -thanks,
> Antonio
>
> --
> You received this bug notification because you are subscribed to juju-
> core.
> Matching subscriptions: MOAR JUJU SPAM!
> https://bugs.launchpad.net/bugs/1209044
>
> Title:
> "juju help plugins" errors on displaying admin, log and deployer info
>
> Status in juju-core:
> Triaged
>
> Bug description:
> $ ~/go/bin/juju help plugins --debug
> 2013-08-07 01:18:33 ERROR juju plugin.go:143 'juju-deployer --description': exit status 2
> 2013-08-07 01:18:34 ERROR juju plugin.go:143 'juju-log --description': exit status 2
> 2013-08-07 01:18:34 ERROR juju plugin.go:143 'juju-admin --description': exit status 2
> Juju Plugins
>
> Plugins are implemented as stand-alone executable files somewhere in the user's PATH.
> The executable command must be of the format juju-<plugin name>.
>
> admin error occurred running 'juju-admin --description'
> deployer error occurred running 'juju-deployer --description'
> log error occurred running 'juju-log --description'
> 2013-08-07 01:18:34 INFO juju supercommand.go:276 command finished
> $ ~/go/bin/juju --version
> 1.13.1-quantal-amd64
>
> -thanks,
> Antonio
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju-core/+bug/1209044/+subscriptions

[Ian Booth (wallyworld)]

Um, the code to pass all flags to plugins hasn't landed yet.

The real cause of the error is as follows: juju considers all executables starting with juju- in the path to be a plugin. When juju help plugins is run, it invokes all juju-* executables with --description. In this case, juju-admin and juju-log belong to pyjuju. They are not juju-core plugins so don't understand the --description argument.

[Dave Cheney (dave-cheney)]

I'm going to make this as retacted, it is an unfortunate interaction with the plugins system and some random binaries in your path. This is a side effect of deciding hat plugins will not live in a magic location like /var/share/....

[Antonio Rosales (arosales)]

I would like to reopen this bug as this still affects the user polish story. If the correct fix is to look for plugins in a certain directory then I think that would help. At a very minimum we should wish list as this is a valid issue that users will run into. On a side note I don't have 'juju-admin' 'juju-log' anywhere on my system. Thus, I don't think this is an issue of my path having a collision with plugins.

My personal opinion is the plugins should live in a defined env path that Juju looks for, perhaps ./juju/plugins by default.

-thanks,
Antonio