Closed strong-code closed 4 years ago
Thanks for sharing that, @strong-code. We’ll leave this open for a while so others might spot it!
And as a temporary workaround, we self-hosted our own archive.
zookeeper-3.5.3-beta.tar.gz
from one of the official mirrors, but remove the .gz
ending for the archive.gzip zookeeper-3.5.3-beta.tar
locally to create a properly compressed archivezookeeper-3.5.3-beta
inside of it, then upload your properly gzipped archive to the folder. Make sure the archive is publicly accessible. The path should now look like https://s3.amazonaws.com/<your bucket name>/zookeeper-3.5.3-beta/zookeeper-3.5.3-beta.tar.gz
install
resource to use your AWS S3 mirror like so:zookeeper '3.5.3-beta' do
mirror 'https://s3.amazonaws.com/<your bucket name>'
end
Hope this helps!
Solved with v13.0.0
This is more of a "heads up" than an issue with this cookbook, per se. The latest release of ZK
zookeeper-3.5.3-beta
was improperly released to distribution channels. The artifact is labeled aszookeeper-3.5.3-beta.tar.gz
but it is not actually a gzipped archive:This causes the
ark
resource to fail when attempting to gunzip/unpack since it always expects a properly gzipped archive here: https://github.com/evertrue/zookeeper-cookbook/blob/master/resources/default.rb#L70Which can be replicated as such:
The Apache team is aware of this but they don't seem to be prioritizing fixing the existing beta release: https://issues.apache.org/jira/browse/ZOOKEEPER-2885
I hope this issue prevents others from banging their head against a wall in the future like I did!