[HADOOP-4582] create-hadoop-image doesn't fail with expired Java binary URL

• Type: Bug
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 0.18.1
• Component/s: contrib/cloud
• Assignee: Unassigned
• Reporter: Karl Lehenbauer
• Created: 03/Nov/08 23:17
• Updated: 21/Jul/14 16:49
• Resolved: 21/Jul/14 16:49

Description

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.