CASMPET-6860 deploy node-exporter via cephadm shell in ansible #217
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary and Scope
Deploy node-exporter via cephadm shell in ansible that deploys smartmon on storage nodes.
We believe this change is necessary because when applying the CSM 1.4.2 patch on Alvarez, the smartmon enablement on storage nodes script failed. This was likely caused by the ceph-common version on the system. To be able to apply the node-exporter.yml file which enables smartmon, node-exported was deployed via cephadm shell. Applying node exporter via the cephadm shell should work every time and doesn't depend on the ceph-common version installed on the node.
This has been tested on Beau.
Issues and Related PRs
List and characterize relationship to Jira/Github issues and other pull requests. Be sure to list dependencies.
Testing
List the environments in which these changes were tested.
Tested on:
admin.keyring
to see that both cases worked.Testing was not done on a metal system. This will be tested on every storage node upgrade.
Test description:
Tested configuring storage nodes with these CFS changes. There were no errors.
Pull Request Checklist