Created attachment 625228 [details]
Services Tab Empty but Services exist

luci.log shows Traces / Callbacks being made

looks like webcluster object not found , but it is there, there is multiple
IP on this host configured for cluster interconnects. 192.168.3.200 is the Web Firefox client Desktop. 


/usr/lib/python2.6/site-packages/sqlalchemy/engine/default.py:230: SAWarning: Unicode type received
 non-unicode bind param value 'ricci'
  param.append(processors[key](compiled_params[key]))
/usr/lib/python2.6/site-packages/sqlalchemy/engine/default.py:230: SAWarning: Unicode type received
 non-unicode bind param value ''
  param.append(processors[key](compiled_params[key]))

00:38:38,678 ERROR [luci.lib.db_helpers] Database object for cluster webcluster not found
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/luci/lib/db_helpers.py", line 37, in get_cluster_db_obj
    db_obj = DBSession.query(Cluster).filter_by(name=unicode(cluster_name)).one()
  File "/usr/lib/python2.6/site-packages/sqlalchemy/orm/query.py", line 1257, in one
    raise orm_exc.NoResultFound("No row was found for one()")
NoResultFound: No row was found for one()
00:38:42,912 ERROR [luci.lib.db_helpers] Database object for cluster webcluster not found
Traceback (most recent call last):
  File "/usr/lib64/python2.6/site-packages/luci/lib/db_helpers.py", line 37, in get_cluster_db_obj
    db_obj = DBSession.query(Cluster).filter_by(name=unicode(cluster_name)).one()
  File "/usr/lib/python2.6/site-packages/sqlalchemy/orm/query.py", line 1257, in one
    raise orm_exc.NoResultFound("No row was found for one()")
NoResultFound: No row was found for one()
00:40:46,033 INFO  [paste.httpserver.ThreadPool] kill_hung_threads status: 10 threads (0 working, 1
0 idle, 0 starting) ave time N/A, max time 0.00sec, killed 0 workers
----------------------------------------
Exception happened during processing of request from ('192.168.3.200', 56293)
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/paste/httpserver.py", line 1068, in process_request_in_thr
ead
    self.finish_request(request, client_address)
  File "/usr/lib64/python2.6/SocketServer.py", line 322, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib64/python2.6/SocketServer.py", line 617, in __init__
    self.handle()
  File "/usr/lib/python2.6/site-packages/paste/httpserver.py", line 442, in handle
    BaseHTTPRequestHandler.handle(self)
  File "/usr/lib64/python2.6/BaseHTTPServer.py", line 329, in handle
    self.handle_one_request()
  File "/usr/lib/python2.6/site-packages/paste/httpserver.py", line 431, in handle_one_request
    self.raw_requestline = self.rfile.readline()
  File "/usr/lib64/python2.6/socket.py", line 450, in readline
    data = self._sock.recv(self._rbufsize)
Error: [('SSL routines', 'SSL23_READ', 'ssl handshake failure')]
----------------------------------------
[root@faust luci]#

This is the expected behavior. I think there is some confusion with the terminology. Traditionally, service groups have been referred to as "services" in this cluster stack. Relatively recently, the terminology was changed to "service group" to more closely match the pacemaker terminology. What you're referring to as services (the things that comprise the service groups, i.e. <apache>,<ip>, etc) are called resources throughout the GUI and docs. The resources tab lists only global resources (those resources that are defined outside of particular services in <rm><resources/></rm>) and have no status associated with them -- they're just bits of configuration that can be referenced inside service groups.

For your config, you could have done:

<rm>
  <resources>
    <apache config_file="/etc/httpd/conf/httpd.conf" name="web" server_root="/etc/httpd" shutdown_wait="0"/>
    <ip address="10.1.3.100" monitor_link="1"/>
  </resources>
  <service autostart="0" name="webserver" recovery="relocate">
    <apache ref="web"/>
    <ip ref="10.1.3.100"/> 
  </service>
</rm>

And "web" and "10.1.3.100" would show up in the resources tab.

Ryan, not sure I agree here. It may not be a bug , but a Useability problem.
I would have expected resources be listed in the Resource tab, as there is no
tab for Global Resources. Incidentally when adding Resources into a Service (Group) - I do see a Global Resource label from the Pull down Menu, furthermore 
I can do something like this :

     <rm>
                <resources>
                        <script file="/etc/init.d/httpd" name="httpd"/>
                </resources>
                <service autostart="0" name="webserver" recovery="relocate">
                        <apache config_file="/etc/httpd/conf/httpd.conf" name="web" server_root="/etc/httpd" sh
utdown_wait="0"/>
                        <ip address="10.1.3.100">
                                <script ref="httpd"/>
                        </ip>
                </service>
        </rm>
        <logging debug="on"/>
</cluster>


Which adds the Global Resource as as Child Resource of a None Global Resource, which just gets a "check mark" in use in the Luci GUI , that does not relate
actually where in use it might be . It's confusing to be honest,
Would we want to fix that up in the GUI a bit and make it consistent to the Admin Guide - emphasize the distinction between Global in use and Service Group specific Resource as does the Admin Guide in the ccs command-line example.

Let me clarify, i mean it's a useability bug.

Christoph,

it looks to me that if anything breaks the terminology (although it
is relative in the context of convergence towards pacemaker) it is ccs
with its "--addsubservice".  E.g., in the usage samples, global resource
"web_fs" is defined using "--addresource" only to be referenced in
"--addsubservice ref=web_fs" sample later on.

> /usr/lib/python2.6/site-packages/sqlalchemy/engine/default.py:230:
> SAWarning: Unicode type received non-unicode bind param value 'ricci'
> param.append(processors[key](compiled_params[key]))
> /usr/lib/python2.6/site-packages/sqlalchemy/engine/default.py:230:
> SAWarning: Unicode type received non-unicode bind param value ''
> param.append(processors[key](compiled_params[key]))

-> [bug 852197]