Thanks for the hard work getting katello 3 released. There are some
fantastic improvements!
I have a question about the remote execution plugin:
Is there a restriction on Solaris clients? All my RHEL clients work fine,
but with Solaris (specifically Solaris 10), the job fails. The Solaris
Client logs at /var/adm/messages look like it was successful:
Accepted publickey for root from <IPADDRESS> port <PORT> ssh2
The job logs in Katello say:
No Output
Exit Status 1
I won't be using puppet or (obviously) subscription manager for Solaris
clients, but I'd like to be able to distribute commands using the Remote
Execution Plugin if possible.
Hello,
could you provide us with some more info about this? The production.log
with log level set to debug and output of the
Proxy::RemoteExecution::Ssh::CommandAction action from the smart proxy's
Dynflow console could help to shed some light on this. What version of
Solaris are you running?
Thanks
– Adam
···
On Fri, Jun 24, 2016 at 9:27 PM, GD wrote:
All,
Thanks for the hard work getting katello 3 released. There are some
fantastic improvements!
I have a question about the remote execution plugin:
Is there a restriction on Solaris clients? All my RHEL clients work fine,
but with Solaris (specifically Solaris 10), the job fails. The Solaris
Client logs at /var/adm/messages look like it was successful:
Accepted publickey for root from port ssh2
The job logs in Katello say:
No Output
Exit Status 1
I won’t be using puppet or (obviously) subscription manager for Solaris
clients, but I’d like to be able to distribute commands using the Remote
Execution Plugin if possible.