2
0
mirror of https://github.com/xcat2/xcat-core.git synced 2026-09-30 23:05:16 +00:00
Files
xcat-core/xCAT-test
Daniel Hilst c406d93bce fix(xcat-core): the genesis lzma case passes when mknb writes no lzma image
nodeset_shell_lzma asserts "output=~genesis" on "ls -l
/tftpboot/xcat/genesis.fs.*.lzma". The path in the command holds the string
the check looks for, so the error "ls: cannot access
'/tftpboot/xcat/genesis.fs.*.lzma'" matches too. The check is green whether
mknb wrote the lzma image or not. Removing the "xz --format=lzma" fallback
from genesis_lzma_command in mknb.pm makes mknb write only the gz image, and
this check still passes.

The same case starts with a "yum install" of xz-lzma-compat from a
rpmfind.net CentOS 8-Stream PowerTools URL. No check follows it. The URL
returns 404 since CentOS 8-Stream went end of life, so the step has done
nothing for a long time.

The check is now "rc==0". ls returns 2 when the glob matches no file, so the
check is red exactly when mknb wrote no lzma image. The dead install and its
paired "yum remove" are deleted rather than gated, because
genesis_lzma_command falls back to "xz --format=lzma" and xz is present on
every EL management node: the lzma image the case tests is produced without
the package.

Verified with the runcmd and check-evaluation code lifted out of
xCAT-test/xcattest. With the lzma image present both checks are green. With
only the gz image present the old check stays green and "rc==0" is red.

Signed-off-by: Daniel Hilst <392820+dhilst@users.noreply.github.com>
(cherry picked from commit 942729abecde9cad7c7ac7adcdbe270d97a79051)
2026-09-05 02:20:10 -03:00
..
2018-04-26 15:15:47 -04:00