In xCAT 2.8, we added a new osdistro table and a new osdistroname attribute
for the osimage def (where osdistroname matches an entry in the osdistro
table).  I think the addkitcomp is looking for this osimage attribute and
corresponding osdistro table entry to verify the OS distro.

e.g. I have:

# lsdef -t osdistro -l rhels6.4-x86_64
Object name: rhels6.4-x86_64
    arch=x86_64
    basename=rhels
    dirpaths=/install/rhels6.4/x86_64
    majorversion=6
    minorversion=4
    type=Linux

[root@x3550n01 ~]# lsdef -t osimage -l linda -i osdistroname
Object name: linda
    osdistroname=rhels6.4-x86_64

It looks like you are missing at least the osdistroname attribute in your
osimage def.  I'm guessing your osimage def was created by copying a def
from a previous xCAT release.  For the osdistro object, the should be
created by copycds, so you most likely have a RH 6.4 entry there.

Linda




From:   Christopher Samuel <[email protected]>
To:     xCAT Users Mailing list <[email protected]>,
Date:   07/30/2013 02:07 AM
Subject:        [xcat-user] Xeon Phi addkitcomp fails when adding to osimage



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

Using kit kindly sent to the list by Wang Xiaopeng I've successfully
gone through the wiki page and built the kit and added the kit to xCAT,
but when I try and add it to our osimage for our Xeon Phi nodes I get:

[root@barcoo-m kits]# addkitcomp -a -i rhel64phi_updates
mpss_compute-2.1.6720-15-rhels-6-x86_64
Error: osimage rhel64phi_updates doesn't fit to kit component
mpss_compute-2.1.6720-15-rhels-6-x86_64 with attribute OS

[root@barcoo-m kits]# lsdef -t kitcomponent
mpss_compute-2.1.6720-15-rhels-6-x86_64
Object name: mpss_compute-2.1.6720-15-rhels-6-x86_64
    basename=mpss_compute
    description=description for component mpss_compute
    kitname=mpss-2.1.6720-15
    release=15
    serverroles=compute
    version=2.1.6720

[root@barcoo-m kits]# lsdef -t osimage rhel64phi_updates
Object name: rhel64phi_updates
    exlist=/install/custom/netboot/rh/compute.exlist
    imagetype=linux
    osarch=x86_64
    osname=linux
    osvers=rhels6
    otherpkgdir=/install/post/otherpkgs/rhels6/x86_64
    permission=755

pkgdir=/install/rhels6.4/x86_64,/install/rhels6/x86_64/updates/rhel-x86_64-server-6/getPackage/,/install/post/postinstall.netboot/rh64/x86_64/

    pkglist=/install/custom/netboot/rh/phi64.pkglist

postinstall=/install/postinstall/02-VLSCIsyncfiles.post,/install/postinstall/add-usr-local.post,/install/postinstall/munge.post,/install/postinstall/ldap.post,/install/postinstall/gpfs.post,/install/postinstall/slurm.post,/install/postinstall/mic.post,/install/postinstall/tmpfs.post

    postscripts=confignics
    profile=compute
    provmethod=statelite
    rootfstype=ramdisk
    rootimgdir=/install/netboot/rhels6/x86_64/phi64_u


Any ideas?

cheers,
Chris
- --
 Christopher Samuel        Senior Systems Administrator
 VLSCI - Victorian Life Sciences Computation Initiative
 Email: [email protected] Phone: +61 (0)3 903 55545
 http://www.vlsci.org.au/      http://twitter.com/vlsci

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlH3V5oACgkQO2KABBYQAh+m/wCdG18w/R5flWeaHho4ClflnnB1
fLUAoJYeXuFSh6VelshwAOZtJi2vEkCm
=EuNP
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------

Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

<<inline: graycol.gif>>

------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent 
caught up. So what steps can you take to put your SQL databases under 
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
xCAT-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to