Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1229815

Summary: [RFE] rhc app create <app name> <cartridge> -s -enable-ha # should throw error
Product: OpenShift Container Platform Reporter: Ryan Howe <rhowe>
Component: RFEAssignee: Mike Barrett <mbarrett>
Status: CLOSED DUPLICATE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 2.2.0CC: jokerman, libra-onpremise-devel, mmccomas, nicholas_schuetz, tiwillia
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-17 15:19:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ryan Howe 2015-06-09 17:09:51 UTC 
[RFE] rhc app create <app name> <cartridge> -s -enable-ha     # should throw error

The proper work flow is 
  $ rhc app-create example ruby-1.9 -s
  $ rhc enable-ha example

This works in creating and app but not enabling ha:
  $rhc app create <app name> <cartridge> -s -enable-ha

It can throw a user off when they are trying to enable-ha, this is a request to get the following  to throw and error. 

rhc app create <app name> <cartridge> -s -enable-ha
Comment 3 Timothy Williams 2015-06-17 20:00:24 UTC 
It looks like this fails not because rhc explicitly allows the enable-ha option with app-create, but because the '-e' option is valid. For example, If you pass in the option '-lololol', rhc will try to use the login 'ololol' as it treats this option the same as '--login ololol' or '-l ololol'.

You can pass in anything as an option, as long as it starts with a valid option letter, and it won't complain:

# rhc app-create breaktest ruby-1.9 -e12345
Application Options
-------------------
Domain:     admin
Cartridges: ruby-1.9
Gear Size:  default
Scaling:    no

Creating application 'breaktest' ... done

The real problem appears to be that there is no failure when the '-e' option is not able to parse the provided environment variable(s).
Comment 5 Timothy Williams 2015-07-17 15:19:13 UTC 
Closing duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1232921

*** This bug has been marked as a duplicate of bug 1232921 ***