Nothing happening when using latest version with Splunk 6.5.1 paths about chef-splunk HOT 9 CLOSED

Worked perfectly fine! Thanks!

from chef-splunk.

Anyone? Would really like to move to version 6.5, but this is hindering that...

from chef-splunk.

This is determined by the the underlying resource dpkg_package used by splunk_installer.

I think the default behavior of dpkg --install is to upgrade a package if it's already installed, but you may need to specify an explicit version property or options to be passed for that commend. Look for that resource declaration at the end of splunk_installer definition.

from chef-splunk.

Are you actually running the with node['splunk']['upgrade_enabled'] as mentioned in the readme? If so it should include the upgrade recipe.

from chef-splunk.

@cheeseplus That's a good point. Is it supposed to be set?

I read the docs as if it was only relevant pre 6.0.1:

This recipe can be used to upgrade a splunk installation, for example from an existing 4.2.1 to 4.3.7. The default recipe can be used for 6.0.1 after upgrading earlier versions is completed.

Also, I didn't find any traces of us ever setting that property before, but maybe we've done upgrades some other way (e.g. always on clean machines).

from chef-splunk.

Could it be an issue that the server URL is pointing to 6.3.3 (https://github.com/chef-cookbooks/chef-splunk/blob/master/attributes/default.rb#L88), or is that just something unrelated?

EDIT This doesn't seem to be a problem, afaiu.

from chef-splunk.

So, I tried setting node.override['splunk']['upgrade_enabled'] = true and specifying the paths to the correct .deb version, but it still does nothing... 😒

Recipe: chef-splunk::install_server
  * remote_file[/var/chef/cache/splunk-6.5.1-f74036626f0c-linux-2.6-amd64.deb] action create_if_missing
    - create new file /var/chef/cache/splunk-6.5.1-f74036626f0c-linux-2.6-amd64.deb
    - update content in file /var/chef/cache/splunk-6.5.1-f74036626f0c-linux-2.6-amd64.deb from none to 34bf4d
    (file sizes exceed 10000000 bytes, diff output suppressed)
  * dpkg_package[splunk] action install (up to date)

from chef-splunk.

@sommestad I was able to repro the issue. It appears Chef dpkg resource implementation skips installation simply on package found. I have a workaround in flight to explicitly set version.
Also, to successfully upgrade, you need to do all of the following:

• set upgrade url node['splunk']['upgrade']['server_url']
• set flag node['splunk']['upgrade_enabled']
• add upgrade recipe to run list: recipe[chef-splunk::upgrade]

from chef-splunk.

#91 merged. closing.

from chef-splunk.