Get all the bugs which were fixed in 2.9.1 release from 2.9.1 defects.
To avoid this problem, you could specify the kernel parameter "netwait" to have the kernel wait the network adapters initialization. On a node with 12 network adapters, the netwait=60 did the trick.
chdef <nodename> -p addkcmdline="netwait=60"
The xCAT postscripts may not be able to run when provisioning SLES 12 on x86_64 platform, the symptom is that after the os provisioning is done, the node status is still "booting", and the node could not be logged in through ssh. The workaround is to login the node through console and run "service sshd start", and then run xdsh <nodename> -K", and then "updatenode <nodename> -P". See bug 4463 for more details.</nodename></nodename>
On Ubuntu 14.x, the command 'lsdef <node> -i status' sometimes can NOT return the correct value for the status attribute. This issue also impacts the attributes which are stored in the nodelist table. Refer to the bug 4468 for more details.</node>
The Postscripts otherpkgs didn't support on sles12. Refer to the bug 4482 for more details.
This page documents all of the changes and notes for
xCAT 2.8.4
Released on
May 23, 2014
A combined summary of all recent xCAT release notes can be viewed at XCAT Release Notes
**Notice: We repackaged xCAT 2.8.4 on May 29, 2014 for defect 4145. The code is the same. We only added a file /etc/httpd/conf.d/xcat.conf into xCAT-server package. **
The following list summarizes the specific details of the test environments used for this release of xCAT. Although not specifically tested, xCAT will continue to be supported and work correctly for other environments. We just do not have the resources to test all possible operating systems and hardware for each release.
For a combined summary of all test environments for recent releases of xCAT, see: XCAT Test environment Summary
When updating xCAT from 2.7 to 2.8 on a SLES x86_64 MN, using the command zypper update -t package 'xCAT' , zypper will ask the following question:
Problem: xCAT-2.8-snap201302071009.x86_64 requires xCAT-genesis-scripts-x86_64, but this requirement cannot be provided
uninstallable providers: xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch[xcat28]
Solution 1: replacement of xCAT-genesis-x86_64-1:2.7.7-snap201301100842.noarch with xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch
Solution 2: do not install xCAT-2.8-snap201302071009.x86_64
Solution 3: break xCAT by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c] (c):
Choose solution # 1. The new xCAT-genesis-scripts-x86_64 rpm replaces the xCAT-genesis-x86_64 rpm. It gets combined with the xCAT-genesis-base-x86_64 rpm from xcat-dep when mknb is run and forms the new genesis boot kernel.
If you have a hierarchical SLES x86_64 cluster, you will hit this same problem when upgrading the services nodes. Since the choice needs to be responded to interactively, you must upgrade xCAT on the SNs manually, instead of having xCAT's otherpkgs support do it for you.
sles11.2 nfs_based statelite on x86 deployment fails. See SF bug 3038 for workaround.
When updating xCAT from 2.7 to 2.8 on a SLES x86_64 MN, using the command zypper update -t package 'xCAT' , zypper will ask the following question:
Problem: xCAT-2.8-snap201302071009.x86_64 requires xCAT-genesis-scripts-x86_64, but this requirement cannot be provided
uninstallable providers: xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch[xcat28]
Solution 1: replacement of xCAT-genesis-x86_64-1:2.7.7-snap201301100842.noarch with xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch
Solution 2: do not install xCAT-2.8-snap201302071009.x86_64
Solution 3: break xCAT by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c] (c):
Choose solution # 1. The new xCAT-genesis-scripts-x86_64 rpm replaces the xCAT-genesis-x86_64 rpm. It gets combined with the xCAT-genesis-base-x86_64 rpm from xcat-dep when mknb is run and forms the new genesis boot kernel.
If you have a hierarchical SLES x86_64 cluster, you will hit this same problem when upgrading the services nodes. Since the choice needs to be responded to interactively, you must upgrade xCAT on the SNs manually, instead of having xCAT's otherpkgs support do it for you.
sles11.2 nfs_based statelite on x86 deployment fails. See SF bug 3038 for workaround.
rmdsklsnode can not remove the NIM machine definition with AIX 7.1.2.0 Update image on xCAT management node or service node. This is actually caused by AIX APAR IV32670. You can get more info from bug 3527
the workaround is to force reinstall the bos.sysmgt.nim.master 7.1.2.0 fileset using AIX 7.1 TL02 media.
Uninstalling PE 1.3 PTF1 man page ppe_rte_man-1.3.0.1-.rpm either directly or indirectly by upgrading to PE 1.3 PTF2 fails during the rpm %preun script processing. This has been fixed in PE 1.3 PTF2 ppe_rte_man-1.3.0.2-.rpm.
To work around this problem, you may need to directly remove the rpm using "rpm -e ". If you are working with a diskless image, the genimage command may fail the first time you try to remove PE 1.3.0.1 or try to upgrade to 1.3.0.2. Simply run your genimage command again, and it should work correctly the second time.
makedhcp -a does not always update the DHCP leases correctly. Workaround is to run makedhcp -n and makedhcp -a. bug 3535
When updating xCAT from 2.7 to 2.8 on a SLES x86_64 MN, using the command zypper update -t package 'xCAT' , zypper will ask the following question:
Problem: xCAT-2.8-snap201302071009.x86_64 requires xCAT-genesis-scripts-x86_64, but this requirement cannot be provided
uninstallable providers: xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch[xcat28]
Solution 1: replacement of xCAT-genesis-x86_64-1:2.7.7-snap201301100842.noarch with xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch
Solution 2: do not install xCAT-2.8-snap201302071009.x86_64
Solution 3: break xCAT by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c] (c):
Choose solution # 1. The new xCAT-genesis-scripts-x86_64 rpm replaces the xCAT-genesis-x86_64 rpm. It gets combined with the xCAT-genesis-base-x86_64 rpm from xcat-dep when mknb is run and forms the new genesis boot kernel.
If you have a hierarchical SLES x86_64 cluster, you will hit this same problem when upgrading the services nodes. Since the choice needs to be responded to interactively, you must upgrade xCAT on the SNs manually, instead of having xCAT's otherpkgs support do it for you.
sles11.2 nfs_based statelite on x86 deployment fails. See SF bug 3038 for workaround.
Uninstalling PE 1.3 PTF1 man page ppe_rte_man-1.3.0.1-.rpm either directly or indirectly by upgrading to PE 1.3 PTF2 fails during the rpm %preun script processing. This has been fixed in PE 1.3 PTF2 ppe_rte_man-1.3.0.2-.rpm.
To work around this problem, you may need to directly remove the rpm using "rpm -e ". If you are working with a diskless image, the genimage command may fail the first time you try to remove PE 1.3.0.1 or try to upgrade to 1.3.0.2. Simply run your genimage command again, and it should work correctly the second time.
makedhcp -a does not always update the DHCP leases correctly. Workaround is to run makedhcp -n and makedhcp -a. bug 3535
When updating xCAT from 2.7 to 2.8 on a SLES x86_64 MN, using the command zypper update -t package 'xCAT' , zypper will ask the following question:
Problem: xCAT-2.8-snap201302071009.x86_64 requires xCAT-genesis-scripts-x86_64, but this requirement cannot be provided
uninstallable providers: xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch[xcat28]
Solution 1: replacement of xCAT-genesis-x86_64-1:2.7.7-snap201301100842.noarch with xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch
Solution 2: do not install xCAT-2.8-snap201302071009.x86_64
Solution 3: break xCAT by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c] (c):
Choose solution # 1. The new xCAT-genesis-scripts-x86_64 rpm replaces the xCAT-genesis-x86_64 rpm. It gets combined with the xCAT-genesis-base-x86_64 rpm from xcat-dep when mknb is run and forms the new genesis boot kernel.
If you have a hierarchical SLES x86_64 cluster, you will hit this same problem when upgrading the services nodes. Since the choice needs to be responded to interactively, you must upgrade xCAT on the SNs manually, instead of having xCAT's otherpkgs support do it for you.
sles11.2 nfs_based statelite on x86 deployment fails. See SF bug 3038 for workaround.
On Linux, after the upgrade to 2.8, you may find the xcatd daemon did not stop and restart successfully. A command like xdsh <node> date will return an error like the following:
Can't locate object method "determinehostname" via package "xCAT::NetworkUtils" at /opt/xcat/lib/perl/xCAT_plugin/xdsh.pm line 121.
If this occurs, run service xcatd stop and check to make sure all xcatd processes are gone. If not kill them and then run service xcatd start. This issue has been fixed in 2.8, so updates after this should not have the error.
Use of kits to package software so it can easily be installed in a cluster. See [Using_Software_Kits_in_OS_Images] and [IBM_HPC_Software_Kits]. Kits for IBM HPC software will be available starting in March.
Most of these bugs will be fixed in 2.8.1.
When updating xCAT from 2.7 to 2.8 on a SLES x86_64 MN, using the command zypper update -t package 'xCAT' , zypper will ask the following question:
Problem: xCAT-2.8-snap201302071009.x86_64 requires xCAT-genesis-scripts-x86_64, but this requirement cannot be provided
uninstallable providers: xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch[xcat28]
Solution 1: replacement of xCAT-genesis-x86_64-1:2.7.7-snap201301100842.noarch with xCAT-genesis-scripts-x86_64-1:2.8-snap201302071009.noarch
Solution 2: do not install xCAT-2.8-snap201302071009.x86_64
Solution 3: break xCAT by ignoring some of its dependencies
Choose from above solutions by number or cancel [1/2/3/c] (c):
Choose solution # 1. The new xCAT-genesis-scripts-x86_64 rpm replaces the xCAT-genesis-x86_64 rpm. It gets combined with the xCAT-genesis-base-x86_64 rpm from xcat-dep when mknb is run and forms the new genesis boot kernel.
If you have a hierarchical SLES x86_64 cluster, you will hit this same problem when upgrading the services nodes. Since the choice needs to be responded to interactively, you must upgrade xCAT on the SNs manually, instead of having xCAT's otherpkgs support do it for you.
sles11.2 nfs_based statelite on x86 deployment fails. See SF bug 3038 for workaround.
AIX: 7.3.1.0 and 7.3.1.1) ( 71L and 71L sp1) and AIX 6.1.9.1
LInux: Rhel5,6 SLES 10,11
RH6.3, RH6.4 and AIX71H
rmdsklsnode can not remove the NIM machine definition with AIX 7.1.2.0 Update image on xCAT management node or service node. This is actually caused by AIX APAR IV32670. You can get more info from bug 3527
the workaround is to force reinstall the bos.sysmgt.nim.master 7.1.2.0 fileset using AIX 7.1 TL02 media.
updatenode -k does not work to compute nodes in a hierarchical environment; that is when the compute node is accessed via a service code. Running this command to the compute node results in an infinite loop which consumes memory. For a work around to exchange ssh keys use xdsh -K to the compute node. 3652
A couple IPMI bugs existed in 2.7.5:
Both of the problems are fixed in this release, see bug 3156.
A couple IPMI bugs exist in 2.7.5:
Both of the problems are fixed in the file IPMI.pm that is attached to bug 3156.
For xCAT 2.7.5 with Linux, you should use the xcat-dep tarball from 6/12/2012. The is the xcat-dep tarball that has been tested with xCAT 2.7.5. (The most recent xcat-dep tarball should also work with xCAT 2.7.5, but it hasn't been tested yet.)
For sles11.2 nfs-based statelite deployment on x86, initrd might fail to mount the rootimg and complain the messages below:
...
Setting up Statelite
mount.nfs: Protocol not supported
Couldn't mount dx360m3n04:/install/netboot/sles11.2/x86_64/compute on /sysroot
Trying again in 1 seconds
...
the work around can be found in bug 3038
When running mkdsklsnode you may, in certain cases, see the following error:
Error: there is already one directory named "", but the entry in litefile table is set to one file, please check it
Error: Could not complete the statelite setup.
Error: Could not update the SPOT
If you see this error simply re-run the command.
In an AIX HASN environment, if you have more than 8 service nodes, the mkdsklsnode command may create an /etc/exports file entry that is not supported by AIX.
The mkdsklsnode command updates the /etc/exports file on the service nodes with an entry that contains a list of replicas that are used by the the AIX NFSv4 support. Due to an NFS limitation the list of replicas may not exceed 8. If you have existing /etc/exports files that already contain the replication entry then it will not be modified and you DO NOT need to take any further actions. However, if you have removed the /etc/exports file or need to set up a new service node, you must manually check the /etc/xports file to make sure there are no more than 8 replicas listed.
The format of the file is as follows:
/install -vers=4,replicas=/install@20.10.12.1:/install@20.10.12.2:/install@20.10.12.3:/install@20.10.12.4:/install@20.10.12.5:/install@20.10.12.6,noauto,rw,root=*
Simply remove one or more replicas from the list.( ex. :/install@20.10.12.6)
For the rvitals command on system p with option "lcds", if there is any LPAR in the noderange which is defined in the xCAT DB, but doesn't exist on its CEC, the rvitals will not return correct info. You can get more info from bug 3133 and you also can get the e-fix to fix this issue from the attached in the bug 3133 page.
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
See the xCAT 2.7.2 SourceForge bugs.
genimage problem in HPC integration. There are two known problems about HPC integration. Bug: https://sourceforge.net/tracker/?func=detail&atid=1006945&aid=3529659&group_id=208749
1) loadl-5103.otherpkgs.pkglist is not putting Loadleveler rpms in a subdirectory. Fix: putting the package names in loadl-5103.otherpkgs.pkglist to loadl subdirectory as:
loadl/LoadL-full-license*
loadl/LoadL-scheduler-full*
loadl/LoadL-resmgr-full*
2) GPFS otherpkgs list includes a comma in comment which is not allowed. Fix: remove the comma in GPFS otherpkgs list. For example:
-# List additinal package names in comments to reduce image size, uncomment them if they are necessary for you.
+# List additinal package names in comments to reduce image size
+# uncomment them if they are necessary for you
mknb problem on system x during xCAT install, workaround provided on defect. https://sourceforge.net/tracker/?func=detail&aid=3532045&group_id=208749&atid=1006945
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
See the xCAT 2.7.1 SourceForge bugs.
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
See the xCAT 2.7 SourceForge bugs.
When upgrading xCAT to 2.7, you may see the following error when the xCAT-server RPM is installed:
Reloading xCATd Can't locate xCAT/Enabletrace.pm in @INC...
This is caused by xCAT-server being installed before perl-xCAT, and xcatd is being restarted before the new version of perl-xCAT is installed. The error message can be ignored, because xcatd will be restarted again when perl-xCAT is installed and then it will pick up the correct files. See SourceForge bug about this. This will be fixed in 2.7.1.
Booting lots of lpars, some hang on c31 (Power 775) - Will be fixed 2.6.12 and 2.7.1. Efix available. See bug for details https://sourceforge.net/tracker/index.php?func=detail&aid=3485032&group_id=208749&atid=1006945#
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
None.
For additional bugs fixed, see Tracker Bugs
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
For additional bugs fixed, see Tracker Bugs
For AIX diskless nodes, if you define /var/adm/ras/errlog as a statelite persistent file in the litefile table, default entries in crontab like the following may cause significant slow downs on the service nodes for a few minutes when those entries run (due to high disk usage on the SNs):
0 11 * * * /usr/bin/errclear -d S,O 30
0 12 * * * /usr/bin/errclear -d H 90
You may want to reduce the frequency that these commands are run.
When powering on multiple p775 CECs or powering on LPARs of multiple p775 CECs via rpower, set site.powerinterval to 30 before running rpower. See https://sourceforge.net/tracker/?func=detail&aid=3426911&group_id=208749&atid=1006945 for details.
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
For additional bugs fixed, see Tracker Bugs
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
These are the changes since the xCAT 2.6.7 release.
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
These are the changes since the xCAT 2.6.2 release. Note: for reasons too difficult to explain here, the xCAT version number went straight from 2.6.2 to 2.6.6. There were no releases named 2.6.3, 2.6.4, or 2.6.5.
DNS fowarders can not work on AIX - bug 3391271
The workaround is to dig the forwarder's dns records into /var/named/db.cache file and restart named service.
For example:
If your forwarder is 9.114.1.1, then run commands below on your xcat management node:
dig @9.114.1.1 . ns >>/var/named/db.cache
stopsrc -s named
startsrc -s named
Power 775 support - On AIX after reboot of the EMS, the ISNM software will not automatically start and LoadLeveler will fail to start. In fact any 32 bit application that uses the DB2 database will have problems connecting to the database. This is a DB2 APAR, it is referenced in the defect and the problem will be fixed when V9.7.5 fix pack is available and applied.
See the following for instructions to restart the HPC stack:
[Setting_Up_DB2_as_the_xCAT_DB#Power_775_Special_instructions_for_Reboot_of_EMS_on_AIX]
See the following defect for details: bug 3391193
This is the summary of what's new in this release. Or you can go straight to [Download_xCAT].
For additional issues, see Tracker Bugs