Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

CLA signed

CLAs look good, thanks!

Had the same problem on my cluster, this fix worked.

Any chance of getting this approved soon? This somehow blocks our deployment atm.

Thanks for the patch and feedback folks. You can (and should) copy the initialization action to your own GCS bucket for your production pipelines: https://github.com/GoogleCloudPlatform/dataproc-initialization-actions#how-initialization-actions-are-used. 1) That protects your automation in case we make a breaking change, and 2) you don't need to wait on us merging PRs.

As described in #279 the path changed because the incorrect (and problematic) Debian 8 zookeeper package was installed instead. This affects all image versions (until next week's unreleased versions) and should be fixed by installing the correct package.

As a very quick work around I would simply delete the apt-get install zookeeper line, because it is already installed.