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=compute
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=compute
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
