Platform `centos` not found (Mixlib::Install::Backend::ArtifactsNotFound) about chef_client_updater HOT 9 CLOSED

Update

Test whether changing platform string from centos to el resolves the issue. Forked cookbook and hard-coded platform to el, resulting in success (chef-client was properly downgraded to v12.19.36 and then subsequently upgraded to latest v13.1.31 by adjusting node['chef_client_updater']['version']).

diff --git a/providers/default.rb b/providers/default.rb
index 7d0a2c9..2169b11 100644
--- a/providers/default.rb
+++ b/providers/default.rb
@@ -73,7 +73,7 @@ def mixlib_install
   options = {
     product_name: 'chef',
     platform_version_compatibility_mode: true,
-    platform: node['platform'],
+    platform: 'el',
     platform_version: node['platform_version'],
     architecture: node['kernel']['machine'],
     channel: new_resource.channel.to_sym,

from chef_client_updater.

IMO that should get fixed over in mixlib-install and we should normalize all the platforms over there with ohai platform names (which at one point i thought i tried to do back when it was all just omnitruck)

from chef_client_updater.

mixlib install will accept any override value for platform. The correct thing to do here is remove platform, platform_version and architecture options and let mixlib install auto detect the appropriate values.

from chef_client_updater.

we had to put that here for windows.

from chef_client_updater.

Ok I see. I'm not used to seeing this since most scenarios like this use chef-ingredient (which I understand why we're not). May I suggest doing similar to how this is handled in chef-ingredient?

https://github.com/chef-cookbooks/chef-ingredient/blob/master/libraries/helpers.rb#L299-L310

Essentially, call Mixlib::Install.detect_platform and go from there.

from chef_client_updater.

I've also see this Windows logic in omnibus: https://github.com/chef-cookbooks/omnibus/blob/master/recipes/_omnibus_toolchain.rb#L20

from chef_client_updater.

@lamont-granquist I'm happy to pinch the referenced code from the chef-ingredient cookbook. Would you entertain a PR with that change? I'm not sure how this would affect the windows support.

from chef_client_updater.

yeah it looks like we should copy that logic and probably the windows logic out of the omnibus cookbook

from chef_client_updater.

This is fixed with the 2.0.3 release

from chef_client_updater.