CSM 1.7 contains many changes spanning bug fixes, new feature development, and documentation improvements. This page lists some of the highlights.
cray
CLI, see console for more information.cray
).
See Managing many components for more information.
Support is added for v2
and v3
API versions.hpe-signing-key
secret, which allows for the verification of the recipe build artifacts.csm.ssh_config
Ansible role to automatically restore the root user’s SSH configuration file during
Management Node Personalization.
For more details, see SSH configuration files.adjust k8s_nodes_ready_check.sh
to not fail when a node is in Ready,SchedulingDisabled
statevelero_backups_check.sh
to not fail if a newer, successful backup existsrun_hms_ct_tests.sh
to handle concurrency bettercheck_key_id_in_jwks.sh
goss-postgresql-syncfailed.yaml
to prevent intermittent false positivespostgres_clusters_running.sh to prevent
intermittent false positivessession-setup
operator now ignores invalid
xnames referenced by session templates,
fixing a bug that caused BOS sessions to be stuck in pending
state.OOMKilled
.boot_sets
in the update data (this fixes a regression bug present in CSM 1.6).hmcollector
, and FAS
services. This reduced instances of pods being restarted due to
OOMKilled
and failed liveness and/or readiness probes. These
changes also improved the responsiveness and scalability of these
services.
hmcollector-poll
service so that event subscriptions are no longer lost after updating Paradise BMC firmware. The service no longer needs to be restarted after performing firmware updates.x86_64
, regardless of the architecture of the recipe that was deleted.require_dkms=true
, regardless of the value of the recipe that was deleted.cfs-debugger
crashed when cfs-state-reporter
service status did not include a since
timestamp.cms-ipxe
would fail if a previously failed cms-ipxe
upgrade job entry existed.error
when the zypper
repositories were not available.For more details and a list of all deprecated CSM features, see Deprecations.
ncn-master.yaml
, ncn-storage.yaml
, and ncn-worker.yaml
in csm-config-management
repository in the
Version Control Service (VCS).
ncn_nodes.yaml
top-level playbook.disable_components_on_completion
Boot Orchestration Service (BOS)
option.For more details and a list of all features with an announced removal target, see Removals.
For a full list of known issues, see Known issues.