topic Re: Why is the checksum for active_bundle not matching last_validated_bundle after application? in Splunk Enterprise

Why is the checksum for active_bundle not matching last_validated_bundle after application?

fatsug — Fri, 13 Dec 2024 13:36:11 GMT

This is not a particulary crucial question but it has been nagging me for a while.

When applying changes to indexes.conf on the manager node I usually do a calidate -> show -> apply round. But I am somewhout confused about a detail.

When you validate a bundle after making modifications you get an updated "last_validated_bundle" checksum. In my mind, when you then apply this bundle the now "last_validated_bundle" checksum should become the new "latest_bundle" and "active_bundle". But this is not the case.

$ splunk apply cluster-bundle Creating new bundle with checksum=<does_not_match_last_validated_bundle> Applying new bundle. The peers may restart depending on the configurations in applied bundle. Please run 'splunk show cluster-bundle-status' for checking the status of the applied bundle. OK

After the new bundle has been applied active_bundle, latest_bundle and last_validated_bundle checksums all match again. But why is the checksum produced after bundle validation not matching the checksum for the applied bundle?

Have a great weekend!

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

sainag_splunk — Wed, 18 Dec 2024 02:04:33 GMT

@fatsug Hello! The last_validated_bundle differs from the active_bundlewhich identifies the bundle that was most recently applied and is currently active across the peer nodes.

Refer: https://docs.splunk.com/Documentation/Splunk/9.3.2/Indexer/Updatepeerconfigurations#Use_the_CLI_to_validate_the_bundle_and_check_restart

if this Helps, Please Upvote.

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

fatsug — Wed, 18 Dec 2024 07:44:16 GMT

Thank you @sainag_splunk

I do understand the "how" so to speak, but I do not understand the "why". If I validate a bundle and then push that bundle I would assume that the checksum for the validated bundle after a push should be the same as the new and current one. Otherwise I cannot validate that the last validated bundle is exactly what has been pushed and applied.

But maybe I'm missing the point? If the checksums are not there to validate changes but rather just to track the presence of unapplied changes, then its fine.

I suspect that at this point the logical follow-up question is, how are bundles modified after validation but before being applied? Or are the checksums only for the changed files/settings and the final cheksum is for the entire bundle?

All the best

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

isoutamo — Wed, 18 Dec 2024 19:48:08 GMT

Here https://conf.splunk.com/files/2017/slides/pushing-configuration-bundles-in-an-indexer-cluster.pdf is an old conf presentation about pushing cluster bundle. It contains quite much information and starting page 41 is troubleshooting section. There are e.g. places where those bundles are stored on CM and peers. Basically you could look their content to see are those different which explains the difference of hash.
r. Ismo

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

sainag_splunk — Wed, 18 Dec 2024 20:33:47 GMT

@fatsug Hi! ASFAIK, the last_validated_bundle is different from the active_bundle because they have different purposes within the bundle lifecycle. The validation process creates a temporary bundle to verify the configuration changes, while the apply process would create a new bundle including additional metadata and runtime information needed for the actual deploy across the cluster. When you run splunk apply cluster-bundle, it creates a new bundle from the master-apps directory and that's why you're seeing a different checksum than your validation step. After successful application, all checksums align since they're now referring to the same deployed bundle.

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

fatsug — Wed, 18 Dec 2024 21:33:53 GMT

While I still find this "counter intuitive" speaking of checksums, I understand that this is by design.

The validated bundle is modified upon application and hence the checksum changes. This is not to prevent pushing bundles that have been modified after validation but rather to keep track of states of changes/bundles.

Thank you for the explanation

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

fatsug — Wed, 18 Dec 2024 21:36:47 GMT

I feel content accepting that bundle checksums are by design present to visualise the different states and not to detect modifications between validation and application. Thank you for the link though, I will definetly have a look at the presentation. With a little luck it might even be available online somewhere.

All the best

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

isoutamo — Wed, 18 Dec 2024 22:15:23 GMT

This is excellent app for finding old presentations and video sessions https://splunkbase.splunk.com/app/3330

Re: Why is the checksum for active_bundle not matching last_validated_bundle after application?

fatsug — Thu, 19 Dec 2024 09:10:36 GMT

"There's an app for that" 😄

Thank you!