ChefDK does not install successfully on Mac OS X El Capitan developer seed

[jeremiahsnapp]

This is a heads up from a customer.

The Chef DK does not install successfully on the Mac OS X El Capitan developer seed. I think it might be due to the the Chef DK trying to create symlinks in /usr/bin to various things under /opt/chefdk.

(However, it one ignores the installation failure, the Chef DK appears to function correctly, although one must set up a PATH with chef shell-init when there are no links to /usr/bin).

[jtimberman]

This was reported: #418 - and closed with a note that a support ticket was filed. Is this issue for the same request?

However, there's a low sense of urgency here IMO. El Capitan has been available for less than a week (!!), and it isn't due to be released until the fall. We do want to have that platform supported, but it requires a non-trivial amount of work in our CI environment - builder/tester node(s) need to be built, and at this time it's not known to me if we can manage to do that with virtual machines, or if we need to have physical machines with OS X 10.11 installed.

/cc @schisamo @yzl

[jtimberman]

By "low sense of urgency" I mean: There's a misalignment with the rate of filing two issues and a support request for this, given it's not even a generally available platform.

[jeremiahsnapp]

@jtimberman Sorry, you are correct that this is a duplicate of #418. I wasn't aware of #418 and I'm not sure why @misheska felt the need to open and close #418 and then open a support ticket. I agree that it is very early to "worry" about El Capitan but I opened this issue anyway to let someone else make that call. I'm fine with this issue being closed. I'm sure when it comes time to support El Capitan this basic problem will be resolved.

[fnichol]

Good to see this is coming down the pipe. If I can get my hands on a pre-seed (probably dependant on whether or not a VM can be baked), I can give it a spin for a repro.

[jtimberman]

@jeremiahsnapp @fnichol FWIW, we have tickets in the RELENG queue to address building boxes for El Capitan/OSX 10.11 builders and testers for CI.

[williamsjj]

The issue is many of us have to run El Capitan since we're developing OS X and iOS apps on our workstations that we also deploy to Chef from.

[jtimberman]

@williamsjj Sure, I get that 😄. We also need to have folks internally to build said infrastructure to support it. 🍰

[schisamo]

@williamsjj And just to reiterate, current versions of ChefDK function correctly on El Capitan. You'll just need to manually add /opt/chefdk/bin to your PATH.

[schisamo]

For tracking purposes RELENG-26 is the parent ticket for this work.

[agh]

Just thought I'd chime in and say this is a "straightforward" problem with System Integrity Protection. Anyone who needs to have ChefDK working on El Capitan can sudo nvram boot-args="rootless=0" (and reboot) until @schisamo or whomever is working on RELENG-26 can devise a "proper" fix. HTH.

[thmsobrmlr]

If you're using rbenv, you can also use the rbenv-chefdk plugin. It will allow you to use ChefDK as a version in rbenv. You can then set the ruby version of the project in a .rubyversion file. You still need to run the (seemingly failing) ChefDK installer beforehand.

[mhenrixon]

/~https://github.com/chef/omnibus-chef/issues/456#issuecomment-133671298