+ Reply to Thread
Results 1 to 7 of 7

Thread: How to get OCS-GUI to work with RedHat HPC solution

  1. #1
    robobold is offline Junior Member
    Join Date
    February 26th, 2009
    Posts
    3
    Downloads
    0
    Uploads
    0

    Default How to get OCS-GUI to work with RedHat HPC solution

    Hi,

    I am trying unsuccessfully to get the nice gui front end working for the RedHat HPC solution

    I believe that I have installed all the relevent kits, I can use cacti, lava and nagios stand-alone.

    However there are install errors when I try to install the ocs-gui using:

    kitops -a -m <path to kit-OCS-GUI-5.1-7.noarch.iso>

    Traceback (most recent call last):
    File "/opt/kusu/bin/kitops", line 655, in ?
    app.run()
    File "/opt/kusu/bin/kitops", line 224, in run
    self.runAdd()
    File "/opt/kusu/bin/kitops", line 305, in runAdd
    self.koinst.addKit(kit)
    File "/opt/kusu/lib/python/kusu/kitops/kitops.py", line 250, in addKit
    _comp = self.__db.Components.select_by(cname=comp['pkgname'])[0]
    IndexError: list index out of range

    The rpms do however appear in /depot/kits/OCS-GUI/5.1/noarch/

    other relevent info:

    sqlrunner -q "select * from kits"
    1|rhel5.3|OS kit for rhel5.3 5 x86_64|5|True|True|x86_64
    2|base|Base Kit|5.2|False|False|noarch
    3|lava|Lava Kit|1.0|False|True|noarch
    4|cacti|kit-cacti package|0.1|False|True|noarch
    5|nagios|Nagios(R) Kit|2.12|False|True|noarch
    7|ntop|Ntop Kit|3.3|False|True|noarch
    13|OCS-GUI|OCS GUI Kit|5.1|False|True|noarch

    sqlrunner -q "select * from components";
    1|1|rhel5.3-5-x86_64|rhel5.3-5-x86_64 mock component|None
    2|2|component-base-installer|Component for Kusu Installer Base|
    3|2|component-base-node|Component for Kusu Node Base|
    4|2|component-gnome-desktop|GNOME Desktop Environment|
    5|2|component-icr-facilitator|Component for Intel(R) Cluster Ready Facilitator|
    8|3|component-lava-master-v1_0|Lava Master Candidate|rhel-5-x86_64
    9|3|component-lava-master-v1_0|Lava Master Candidate|centos-5-x86_64
    10|3|component-lava-master-v1_0|Lava Master Candidate|rhel-5-i386
    11|3|component-lava-master-v1_0|Lava Master Candidate|centos-5-i386
    12|3|component-lava-compute-v1_0|Lava Compute Node|rhel-5-x86_64
    13|3|component-lava-compute-v1_0|Lava Compute Node|rhel-5-i386
    14|3|component-lava-compute-v1_0|Lava Compute Node|centos-5-x86_64
    15|3|component-lava-compute-v1_0|Lava Compute Node|centos-5-i386
    18|4|component-cacti|Cacti master node|centos-5-x86_64
    19|4|component-cacti|Cacti master node|rhel-5-x86_64
    20|4|component-cacti|Cacti master node|centos-5-i386
    21|4|component-cacti|Cacti master node|rhel-5-i386
    22|4|component-cacti-monitored-node|Cacti monitored node|centos-5-x86_64
    23|4|component-cacti-monitored-node|Cacti monitored node|rhel-5-x86_64
    24|4|component-cacti-monitored-node|Cacti monitored node|centos-5-i386
    25|4|component-cacti-monitored-node|Cacti monitored node|rhel-5-i386
    28|5|component-nagios-installer-v2_12|Nagios Installer|rhel-5-x86_64
    29|5|component-nagios-installer-v2_12|Nagios Installer|centos-5-x86_64
    30|5|component-nagios-installer-v2_12|Nagios Installer|rhel-5-i386
    31|5|component-nagios-installer-v2_12|Nagios Installer|centos-5-i386
    32|5|component-nagios-compute-v2_12|Nagios Compute Node|rhel-5-x86_64
    33|5|component-nagios-compute-v2_12|Nagios Compute Node|centos-5-x86_64
    34|5|component-nagios-compute-v2_12|Nagios Compute Node|rhel-5-i386
    35|5|component-nagios-compute-v2_12|Nagios Compute Node|centos-5-i386
    38|7|component-ntop-v3_3|Ntop Monitoring|rhel-5-x86_64
    39|7|component-ntop-v3_3|Ntop Monitoring|centos-5-x86_64
    40|7|component-ntop-v3_3|Ntop Monitoring|rhel-5-i386
    41|7|component-ntop-v3_3|Ntop Monitoring|centos-5-i386

    ---

    There seems to be a problem updating the above table. Does anyone know what I am doing wrong here!

    I have tried manually populating the component table with no avail

    sqlrunner -q "insert into components values (42,13,'component-OCS-GUI','OCS GUI installer','rhel-5-x86_64')";

    I've run out of ideas

  2. #2
    ltsai is offline Project Moderator
    Join Date
    March 4th, 2008
    Posts
    61
    Blog Entries
    3
    Downloads
    3
    Uploads
    0

    Default

    Hi

    Which version of kusu are you using? Can you provide us with the output of /etc/kusu-release?

    -Liming

  3. #3
    robobold is offline Junior Member
    Join Date
    February 26th, 2009
    Posts
    3
    Downloads
    0
    Uploads
    0

    Default

    Kusu "Platform OCS" 5 (build 1991)

  4. #4
    ltsai is offline Project Moderator
    Join Date
    March 4th, 2008
    Posts
    61
    Blog Entries
    3
    Downloads
    3
    Uploads
    0

    Default

    Hi,

    Did the GUI came together with the Platform OCS media?

  5. #5
    robobold is offline Junior Member
    Join Date
    February 26th, 2009
    Posts
    3
    Downloads
    0
    Uploads
    0

    Default

    the ocs gui came in the package kit-OCS-GUI-5.1-7.tar

  6. #6
    George Goh is offline Project Moderator
    Join Date
    February 29th, 2008
    Location
    Singapore
    Posts
    26
    Blog Entries
    5
    Downloads
    16
    Uploads
    11

    Default

    Hi,

    I'm suspecting that the OCS GUI component may not be associated with the installer nodegroup.

    Can you run the following query:

    # sqlrunner -q "select ngname,cname from components,ng_has_comp,nodegroups where cname='component-OCS-GUI' and components.cid=ng_has_comp.cid and ng_has_comp.ngid=nodegroups.ngid;"
    If no results show, you have to manually update your ng_has_comp with the following:
    # sqlrunner -q "insert into ng_has_comp values(1, <component cid>);"

  7. #7
    _fmms_ is offline Member
    Join Date
    September 16th, 2008
    Location
    Germany
    Posts
    42
    Downloads
    7
    Uploads
    0

    Default

    I just hit the same bug.

    I am using:
    Code:
    [root@master ~]# cat /etc/kusu-release
    Kusu "Gong Gong" 1.1 (build 3737)
    
    And I have
    Code:
    kit-OCS-GUI-5.1-7.noarch.iso
    
    .

    The components variable in line 248 of kitops is
    Code:
    [{'pkgname': 'component-OCS-GUI', 'description': 'component for installing the OCS GUI', 'compversion': '5.1', 'driverpacks': [], 'ngtypes': [], 'comprelease': '4', 'ostype': '', 'osversion': '', 'arch': 'x86_64', 'name': 'OCS-GUI'}]
    Added kit: OCS-GUI-5.1-noarch
    

+ Reply to Thread

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts