Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure local directory hierarchy (suspect there is a better way). #81

Merged
merged 1 commit into from
Dec 18, 2013
Merged

Conversation

sw1nn
Copy link

@sw1nn sw1nn commented Sep 23, 2013

The java recipe consistently fails for me when run the first time. A subsequent vagrant provision succeeds.

I tracked the problem down to the failure of the curl of the jdk .tar.gz with error 23 - a write error. In turns out that the destination directory, /var/chef/cache, doesn't exist at that time.

Not sure what, if anything, is supposed to create that directory, but getting using curl --create-dirs seems fairly innocuous.

I'm using a standard precise64.box and these attributes.

:java => {
  :install_flavor => "oracle",
  :oracle => {
     "accept_oracle_download_terms" => true
  },
:jdk_version => "7"

@jesseadams
Copy link

Hey @sw1nn! Thank you for supporting the Opscode Cookbooks! Opscode's process has a couple prerequisites before they will merge your contribution. We need to ensure you've completed a Contributor License Agreement (CLA) and a ticket on their ticket tracker for the release workflow. Pull requests are optional, but should always include the ticket number that they're related to for cross-referencing. Please take a moment to review the below wiki page for the appropriate steps:

If you have already done all of that, please consider linking to the ticket in this pull request.

carmstrong added a commit that referenced this pull request Dec 18, 2013
Ensure local directory hierarchy (suspect there is a better way).
@carmstrong carmstrong merged commit 616999d into sous-chefs:master Dec 18, 2013
@lock
Copy link

lock bot commented May 3, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators May 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants