Can somebody explain what is supposed to disable the external OS package 
repositories during a statefull install.?
I have a cluster where it looks like this was happening, but I just rebuilt a 
compute node and it didn’t happen causing that node to pull in a newer kernel 
package that I wasn’t ready for. I was testing this process because I have 
another cluster where I’m moving from stateless builds to statefull and this 
isn’t happening at all there.
Here are some details. In both cases the statefull nodes being built are CentOS 
7.9 and the file I expect to change during the build is 
/etc/yum.repos.d/CentOS-Base.repo. On the nodes that were built in the past 
this file has enabled=0 added to each of 4 repositories that are listed in the 
file. On new builds that line is missing.
I’ve looked through some of the xcat code and I found a postscript called 
addsiteyum that looks like it should take care of this, but I can’t find any 
evidence that I’ve ever had it listed in my node definitions. Does it get 
called automatically at some stage or did I manage to remove this without 
realizing it?
Further, even if I run it manually I’ve found that it depends on finding a 
template repo file in repos/$OSVER/$ARCH inside of the postscripts directory. 
I’ve got those, but for some reason mine are in repos/install/$OSVER/$ARCH. So, 
what process creates or manages those files and how could I have gotten them 
created in the wrong subdirectory?
_______________________________________________
xCAT-user mailing list
xCAT-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xcat-user

Reply via email to