Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 21 Jul 2014 16:50:38 +0000 (UTC)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12407744.1225754232558.9882.1405961438774@arcas>
In-Reply-To: <JIRA.12407744.1225754232558@arcas>
References: <JIRA.12407744.1225754232558@arcas>
Subject: [jira] [Resolved] (HADOOP-4582) create-hadoop-image doesn't fail
 with expired Java binary URL
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HADOOP-4582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HADOOP-4582.
--------------------------------------

    Resolution: Won't Fix

We removed this stuff a long time ago. Closing.

> create-hadoop-image doesn't fail with expired Java binary URL
> -------------------------------------------------------------
>
>                 Key: HADOOP-4582
>                 URL: https://issues.apache.org/jira/browse/HADOOP-4582
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: contrib/cloud
>    Affects Versions: 0.18.1
>            Reporter: Karl Anderson
>            Priority: Minor
>
> Part of creating a Hadoop EC2 image involves putting the URL for the Java binary into hadoop-ec2-env.sh.  Ths URL is time-sensitive; a working URL will eventually redirect to a HTML warning page.  create-hadoop-image-remote does not notice this, and will create, bundle, and register a non-working image, which launch-cluster will launch, but on which the hadoop commands will not work.
> To fix, check the output status of the "sh java.bin" command in create-hadoop-image-remote, die with that status, and check for that status when create-hadoop-image-remote is run.


--
This message was sent by Atlassian JIRA
(v6.2#6252)