#4711 [FVT]:rcons NODE with confluent returns Connection failure on SLES

[ting ting li]

c910f02c01p25:~ # rpm -qa |grep -i xcat
xCAT-server-2.10-snap201505190324
xCAT-client-2.10-snap201505190324
ipmitool-xcat-1.8.11-3
xCAT-genesis-base-ppc64-2.10-snap201505172314
perl-xCAT-2.10-snap201505190324
yaboot-xcat-1.3.17-rc1
grub2-xcat-2.02-0.16.el7.snap201505140423
xCAT-genesis-scripts-ppc64-2.10-snap201505122308
xCAT-2.10-snap201505190324
conserver-xcat-8.1.16-10
xCAT-confluent-2.10-snap201505122308
xCAT-buildkit-2.10-snap201505122308
c910f02c01p25:~ # ps -ef |grep -i confluent
root 13134 12686 0 05:38 pts/5 00:00:00 grep -i confluent
root 26530 1 2 05:02 ? 00:01:05 /usr/bin/python /opt/confluent/bin/confluent
root 26531 26530 0 05:02 ? 00:00:00 /usr/bin/python /opt/confluent/bin/confluent
c910f02c01p25:~ # tabdump site |grep -i consoleservice
"consoleservice","confluent",,
c910f02c01p25:~ # rcons c910f02c01p26
ocket connection to xcatd daemon on localhost:3001.
Verify that the xcatd daemon is running and that your SSL setup is correct.
Connection failure: SSL connect attempt failed with unknown errorerror:00000000:lib(0):func(0):reason(0) at /opt/xcat/lib/perl/xCAT/Client.pm line 265.
Unable to open socket connection to xcatd daemon on localhost:3001.
Verify that the xcatd daemon is running and that your SSL setup is correct.
Connection failure: SSL connect attempt failed with unknown errorerror:00000000:lib(0):func(0):reason(0) at /opt/xcat/lib/perl/xCAT/Client.pm line 265.
Unable to open socket connection to xcatd daemon on localhost:3001.
Verify that the xcatd daemon is running and that your SSL setup is correct.
Connection failure: SSL connect attempt failed with unknown errorerror:00000000:lib(0):func(0):reason(0) at /opt/xcat/lib/perl/xCAT/Client.pm line 265.
Unable to open socket connection to xcatd daemon on localhost:3001.

[Victor Hu]

Ting Ting,

I think your test machine has changed a bit, I don't see confluent installed there. Casandra was able to reproduce this by setting nodehm.conserver to the xcathost IP address.

This means that rcons is starting up using /opt/confluent/bin/confetty -s <server> <node> .... </node></server>

# /opt/confluent/bin/confetty --help
Usage: confetty [options]

Options:
  -h, --help            show this help message and exit
  -s SERVER:PORT, --server=SERVER:PORT
                        Confluent instance to connect to
  -c PATH, --control=PATH
                        Path to offer terminal control

I think the issue here is similar to http://sourceforge.net/p/xcat/bugs/4709/
Let's discuss today in the mtg with Xiao Peng.

[Victor Hu]

The SSL issue is caused by SLES11 exports XCATSSLVER=TLSv1 into the environment. For confluent hmc console support, we are exec a script under the /opt/confluent/lib/python/plugin/console/xcathmc.sh. In there, need to also export the environment when on SLES11 systems.

Another issues going to fix in this commit is rcons. If nodehm.conserver is set to an IP address, rcons will try to start confetty with -s option. For now, check the IP and if we are on the same node running confluent server, omit the -s option.

commit id: 60bcc9e8840dd197c194ba439e34a170068fdd2f

[ting ting li]

Verified with 20150703 build

c910f02c01p25:/etc/zypp/repos.d # service conserver status
consever is not running
c910f02c01p25:/etc/zypp/repos.d # tabdump site |grep -i confluent
"consoleservice","confluent",,
c910f02c01p25:/etc/zypp/repos.d # rcons c910f02c01p26 -f

Acquiring startup lock...done

Welcome to SUSE Linux Enterprise Server 11 SP4 (ppc64) - Kernel 3.0.101-63-ppc64 (console).

c910f02c01p26 login:

Welcome to SUSE Linux Enterprise Server 11 SP4 (ppc64) - Kernel 3.0.101-63-ppc64 (console).

c910f02c01p26 login:

Welcome to SUSE Linux Enterprise Server 11 SP4 (ppc64) - Kernel 3.0.101-63-ppc64 (console).

c910f02c01p26 login: