After an upgrade, the version specified by node['splunk']['server']['version'] or node['splunk']['forwarder']['version'] can be behind the version specified by node['splunk']['server']['upgrade']['version'] or node['splunk']['forwarder']['upgrade']['version']. respectively. This can cause the installer to downgrade Splunk Server/Forwarder on the next chef run after an upgrade.
REPRO:
enable upgrade and set the version for upgrade to be greater than the version to be installed normally (non-upgrade package resource)
run the chef-splunk::upgrade recipe on a node and see that the node was upgraded
*disable upgrades and re-run the normal run list on the same node
After an upgrade, the version specified by
node['splunk']['server']['version']ornode['splunk']['forwarder']['version']can be behind the version specified bynode['splunk']['server']['upgrade']['version']ornode['splunk']['forwarder']['upgrade']['version']. respectively. This can cause the installer to downgrade Splunk Server/Forwarder on the next chef run after an upgrade.REPRO:
chef-splunk::upgraderecipe on a node and see that the node was upgraded *disable upgrades and re-run the normal run list on the same nodeChef will downgrade Splunk after the last step