[ovirt-users] HP ILO2 , fence not working, with SSH port specified, a Bug?

[mad Engineer]

:)


On Mon, Jun 30, 2014 at 12:12 PM, combuster <combuster at archlinux.us> wrote:

>  Well if it's a bug then it would be resolved by now :)
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1026662
>
> Had the same doubts as you did. I really don't know why it wouldn't
> connect to iLO if the default port is specified, but I'm glad that you
> found a workaround.
>
> Ivan
>
>
> On 06/30/2014 08:36 AM, mad Engineer wrote:
>
> hi i have an old HP server with ILO2
>
>  on manager i configured power management and configured SSH port to use
> for ILO2
>
>  for checking SSH i manually ssh to ILO and is working fine,
>
>  but power management test always fail with "*Unable to connect/login to
> fencing device*"
>
>
>  log shows its using fence_ilo instead of fence_ilo2
>
>  Thread-18::DEBUG::2014-06-30 08:23:14,106::API::1133::vds::(fenceNode)
> fenceNode(addr=XXXX,port=,*agent=ilo*
> ,user=Administrator,passwd=XXXX,action=status,secure=,options=ipport=22
> ssl=no)
> Thread-18::DEBUG::2014-06-30 08:23:14,741::API::1159::vds::(fenceNode) rc
> 1 in agent=*fence_ilo*
> ipaddr=xxxxxxxxxx
> login=Administrator
> action=status
> passwd=XXXX
>  ipport=22
> ssl=no out  err *Unable to connect/login to fencing device*
>
>
>
>
>  *Manually testing*
>
>  fence_ilo -a xxxxxx  -l Administrator -p xxxxx -o status
>  Status: ON
>
>  but with ssh port specified ie *-u *
>
>  fence_ilo -a xxxxxx  -l Administrator -p xxxxx -o status  -u 22
>  *Unable to connect/login to fencing device*
>
>  So when we specify ssh port it fails and with out ssh port its working
>
>  this is the case with ILO2 also
>
>  for ilo3 and ilo4 since it does not ask for SSH port its working
>
>  Is this a Bug
>
>  Thanks,
>
>
>
> _______________________________________________
> Users mailing listUsers at ovirt.orghttp://lists.ovirt.org/mailman/listinfo/users
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/users/attachments/20140630/3fa3b0ca/attachment-0001.html>