Hi, Brian
 
I don't think we have such limit, I had tried to deploy one node with your osimage and have no error.

And will you pls use the command below to monitor and check what happened during deploy progress?
Pls replace 'c910f05c01bc05k03' with your compute node.
 
root@c910f03c05k10:~# xcatprobe osdeploy -n c910f05c01bc05k03
The install NIC in current server is eth0                                                                         [INFO]
All nodes to be deployed are valid                                                                                [ OK ]
-------------------------------------------------------------
Start capturing every message during OS provision process....
-------------------------------------------------------------
...
[c910f05c01bc05k03] 22:11:37 provision completed.(c910f05c01bc05k03)
[c910f05c01bc05k03] 22:11:37 provision completed                                                                  [ OK ]
[c910f05c01bc05k03] 22:11:37 provision completed.(c910f05c01bc05k03)
[c910f05c01bc05k03] 22:11:37 provision completed                                                                  [ OK ]
All nodes specified to monitor, have finished OS provision process                                                [ OK ]
======================  Summary  =====================
All nodes provisioned successfully                                                                                [ OK ]
root@c910f03c05k10:~#
 
My osimage looks like this:
 
root@c910f03c05k10:~# lsdef -t osimage centos7.4-x86_64-vesta-compute
Object name: centos7.4-x86_64-vesta-compute
    imagetype=linux
    osarch=x86_64
    osdistroname=centos7.4-x86_64
    osname=Linux
    osvers=centos7.4
    otherpkgdir=/install/post/otherpkgs/centos7.4/x86_64
    pkgdir=/install/ospkgdir/centos7.4/x86_64
    pkglist=/install/custom/centos/74/compute.centos7.pkglist   ==> Copied from /opt/xcat/share/xcat/install/centos/compute.centos7.pkglist
    profile="">    provmethod=install
    template=/opt/xcat/share/xcat/install/centos/compute.centos7.tmpl
root@c910f03c05k10:~#
root@c910f03c05k10:~#
root@c910f03c05k10:~# rinstall c910f05c01bc05k03 osimage=centos7.4-x86_64-vesta-compute
Provision node(s): c910f05c01bc05k03
 
 
Thx!
Best Regards,
-----------------------------------
Zhao Er Tao

IBM China System and Technology Laboratory, Beijing
Tel:(86-10)82450485
Email: erta...@cn.ibm.com
Address: 1/F, 28 Building,ZhongGuanCun Software Park,
No.8 DongBeiWang West Road, Haidian District,
Beijing, 100193, P.R.China
 
 
----- Original message -----
From: Brian Joiner <martinitime1...@gmail.com>
To: xcat-user@lists.sourceforge.net
Cc:
Subject: [xcat-user] xCAT 2.14 does not respect custom OS definition attributes
Date: Fri, May 25, 2018 6:39 AM
 
First time poster here.
 
I've installed xcat 2.14 and using the standard centos 7.4 os definitions I can deploy a node.
 
However, cloning that OS definition and changing the pkglist, otherpkglist, otherpkglist attributes to custom entries cause the node to hang during boot.  I don't remember having these issues on other versions.
 
Works:
 
Object name: centos7.4-x86_64-install-compute
    imagetype=linux
    osarch=x86_64
    osdistroname=centos7.4-x86_64
    osname=Linux
    osvers=centos7.4
    otherpkgdir=/install/post/otherpkgs/centos7.4/x86_64
    pkgdir=/install/centos7.4/x86_64
    pkglist=/opt/xcat/share/xcat/install/centos/compute.centos7.pkglist
    profile="">
    provmethod=install
    template=/opt/xcat/share/xcat/install/centos/compute.centos7.tmpl
 
 
FAILS:
 
Object name: centos7.4-x86_64-vesta-compute
    imagetype=linux
    osarch=x86_64
    osdistroname=centos7.4-x86_64
    osname=Linux
    osvers=centos7.4
    otherpkgdir=/install/custom/centos/74/otherpkgs
    pkgdir=/install/centos7.4/x86_64
    pkglist=/install/custom/centos/74/compute.centos7.pkglist
    profile="">
    provmethod=install
    template=/opt/xcat/share/xcat/install/centos/compute.centos7.tmpl
 
UPDATE:  If I change just the custom pkglist to the default one, deployment works.
 
Is xCAT so picky about folder locations and file names that it can't handle a custom 'pkglist' attribute? I often will create multiple OS definitions for various purposes and don't want to modify the default package lists.  We've used custom files and locations with other versions, did 2.14 break something?
 
-- 
Thanks,
Brian Joiner
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user
 

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to