Skip to content

[3.14.1] Update changelog #3073

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
himani2411 merged 1 commit into from
Dec 19, 2025
Merged

[3.14.1] Update changelog #3073

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 3 additions & 5 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,8 @@ This file is used to list changes made in each version of the AWS ParallelCluste
3.14.1
------

**ENHANCEMENTS**
- Ensure clustermgtd runs after cluster update. On success, start it unconditionally. On failure, start it if the queue reconfiguration succeeded.

**CHANGES**
- Improve cluster update resiliency by ensuring clustermgtd is started after updates complete successfully, or after failed updates where queue reconfiguration succeeded.
- Add chef attribute `cluster/in_place_update_on_fleet_enabled` to disable in-place updates on compute and login nodes
and mitigate performance impact at scale.
- Upgrade Slurm to version 24.11.7 (from 24.11.6).
Expand All @@ -29,9 +27,9 @@ This file is used to list changes made in each version of the AWS ParallelCluste
- Open MPI: openmpi40-aws-4.1.7-2 and openmpi50-aws-5.0.8-11

**BUG FIXES**
- Fix incorrect timestamp parsing for chef-client.log in CloudWatch Agent configuration.
- Prevent cluster readiness check failures due to instances launched while the check is in progress.
- Fix race condition where compute nodes could deploy the wrong cluster config version after an update failure.
- Prevent cluster readiness check failures due to instances launched while the check is in progress.
- Fix incorrect timestamp parsing for chef-client.log in CloudWatch Agent configuration.

3.14.0
------
Expand Down
Loading