Template.pm silently continued rendering kickstart templates when
getipaddr() failed to resolve the master hostname, producing
kickstarts with an empty MASTER_IP. Nodes would install successfully
but fail on first reboot when post.xcat and xcatinstallpost tried
to contact the master, timing out after 90 retries with:
the network between the node and is not ready
Postage.pm (mypostscript generation) already checks for this and
returns a clear error. Apply the same pattern in Template.pm so
nodeset fails immediately with a descriptive message instead of
producing a broken kickstart.
Fixes#7544
When a pkgdir has no valid repodata, Yum.pm creates an empty
local-repository.tmpl file. Template.pm then reads it and generates
an empty yum repo config block in the kickstart. Adding a -s check
skips empty template files instead of silently including them.
Revives the fix from PR #4769 which was closed without merging.
Fixes#3572
Fixes the following error with perl-Crypt-CBC >= 3.0+ (default on EL9+)
'blocksize' is not a recognized argument at /usr/share/perl5/vendor_perl/Crypt/CBC.pm line 312.
at /opt/xcat/lib/perl/xCAT/IPMI.pm line 724.
This configures automated installation using the subiquity installer, as
documented at
https://ubuntu.com/server/docs/install/autoinstall-quickstart and other
locations on the Internet.
Installation uses the NFS export of /install, and configures the
installer to use the nocloud-net datasource, creating a per-node
directory containing the processed template file as the user-data file,
and an empty meta-data file.
Kernel and initrd files are pulled from the casper/ directory under the
package dir.
Unnecessary elements of the kernel command line have been removed in the
subiquity installer path.
Support has been added for selecting a subiquity specific default
template, as well as an updated pre-install script and some minor POSIX
shell compliance fixes for the getinstdisk script.
This will be compatible with some current implementations
that do not have SHA-1. HMAC-SHA1 may be still secure, but
SHA1 in any context *looks* bad even if it isn't.
The maximum socket receive buffer size (SO_RCVBUF) is set from the value
in /proc/sys/net/core/rmem_max. When this value is close to INT_MAX,
the select() system call used by IO::Select->can_read() never returns
true. This causes packets to never be read. Therefore, reduce the
maximum socket receive buffer size to a value which works.
* rpower for redfish support
* rsetboot for redfish support
* recover
* modify depending on discussion and comments
* refine test case xcatd_start (#5932)
* Update small text in the diskful support example for cuda_power9_setup
Fix small issue mentioned in 5852
* rsetboot for redfish support
* Fix issue 5933: xCAT-openbmc-py build failed
* Fix remoteshell compatibility with custom Match (#5936)
If a user has a custom Match directive, remoteshell would
create an invalid configuration. Fix by ensuring we are
outside of a match context by doing Match all explicitly.
* fix issue PR #5936 resulted in remoteshell failed in rhels6.10 #5944
* refine xcat-inventory backend testcase (#5946)
* add test case for issue 3602: confignetwork cannot work when regular expression is used in nics table
* add lsdef to get more debug info
* Revert "fix issue PR #5936 resulted in remoteshell failed in rhels6.10 #5944"
* revert PR Fix remoteshell compatibility with custom Match #5936
* add sle dir for copycds
* remove HPC packages from sle15 template
* copycds support ppc64le sle15
* support packages products for sle15
* create repos for all products in sle15 Package ISO
* fix deployment status postbooting in sle15
* support sle15
* add copycds example for sle15
* generate add_on product
* polished
* adjust product_dir