Skip to content
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.

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

CRAYSAT-1919: Update to cfs-config-util version 5.1.1 #3705

Merged
merged 1 commit into from
Oct 14, 2024

Conversation

haasken-hpe
Copy link
Contributor

Summary and Scope

The cfs-config-util image is used by the update-mgmt-ncn-cfs-config.sh script, which is used during patch installs. This script updates the CFS configuration assigned to management nodes so that it uses the latest version of the Ansible content from the csm-config-management repo in VCS.

This new version of cfs-config-util adds support for CFS v3, and it fixes a couple bugs that resulted in data being lost from configurations that were modified with this tool (additional_inventory and special_parameters). It also better handles unknown fields in CFS configurations, so if, in the future, additional fields are added to CFS configurations, they won't be lost.

Issues and Related PRs

Testing

Tested on:

  • drax

Test description:

Built a CSM release distribution that contained the shell script and the latest version of the cfs-config-util image and copied it to drax. Mocked out a new CSM release and associated branch in the csm-config-management repo in VCS. Then executed the script to update the configuration currently assigned to management nodes. The script successfully updated 3 configurations assigned to those nodes and then waited for the nodes to reach a configured status.

Risks and Mitigations

This is pretty low risk, especially for CSM 1.6.0. I do not think this script currently gets used in the normal installation of CSM 1.6.0. As far as I'm aware it has only been used in the installation of CSM 1.4 and 1.5 patch versions (e.g. 1.5.2). It is good to get this fixed well before we have to release CSM 1.6.z patches though.

I will also backport to CSM 1.5 so that the fix will be in place for the next CSM 1.5 patch release, if any.

Pull Request Checklist

  • Version number(s) incremented, if applicable
  • Copyrights updated
  • License file intact
  • Target branch correct
  • Testing is appropriate and complete, if applicable
  • HPC Product Announcement prepared, if applicable

The cfs-config-util image is used by the `update-mgmt-ncn-cfs-config.sh`
script, which is used during patch installs. This script updates the CFS
configuration assigned to management nodes so that it uses the latest
version of the Ansible content from the csm-config-management repo in
VCS.

This new version of cfs-config-util adds support for CFS v3, and it
fixes a couple bugs that resulted in data being lost from configurations
that were modified with this tool (`additional_inventory` and
`special_parameters`). It also better handles unknown fields in CFS
configurations, so if, in the future, additional fields are added to CFS
configurations, they won't be lost.

Test Description:
Built a CSM release distribution that contained the shell script and the
latest version of the cfs-config-util image and copied it to drax.
Mocked out a new CSM release and associated branch in the
csm-config-management repo in VCS. Then executed the script to update
the configuration currently assigned to management nodes. The script
successfully updated 3 configurations assigned to those nodes and then
waited for the nodes to reach a configured status.
@haasken-hpe
Copy link
Contributor Author

/backport release/1.5

Copy link

Backporting into branch release/1.5 was successful. New PR: #3706

@mtupitsyn mtupitsyn merged commit 4fdb9e9 into release/1.6 Oct 14, 2024
2 checks passed
@mtupitsyn mtupitsyn deleted the CRAYSAT-1919-update-cfs-config-util-version branch October 14, 2024 18:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants