Bug 807513

Summary: Domain is destroyed successfully even if you specify a wrong namespace
Product: OKD Reporter: jizhao
Component: PodAssignee: Ravi Sankar <rpenta>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: high    
Version: 2.xCC: bmeng, dmcphers, mmcgrath, mpatel, rpenta, szhou
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-13 18:31:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description jizhao 2012-03-28 02:47:20 UTC 
Description of problem:
Domain is successfully destroyed with a wrong namespace parameter.

Version-Release number of selected component (if applicable):
rhc-0.89.7-1.el6_2.noarch

How reproducible:
Always

Steps to Reproduce:
1.Create domain
$ rhc domain create -n <domain_name> -l <user_email>
2.Destroy domain with a wrong namespace parameter
$ rhc domain destroy -n <invalid_domain_name> -l <user_email>
3.
  
Actual results:
Domain is destroyed successfully.
<------------output-------------->
[root@guest ~]# rhc domain destroy -l jizhao+2 -d -n jizhao
Password: 
Submitting form:
namespace: jizhao
delete: true
rhlogin: jizhao+2
Contacting https://ec2-23-20-152-133.compute-1.amazonaws.com
Response from server:
DEBUG:


Exit Code: 0
api_c: placeholder
broker_c: namespacerhloginsshapp_uuiddebugaltercartridgecart_typeactionapp_nameapi
API version:    1.1.3
Success
<-------------------------------->

Expected results:
Domain shouldn't be destroyed. The client should prompt something like "invalid domain name" or so.

Additional info:
Comment 1 Ravi Sankar 2012-04-09 22:27:38 UTC 
Fixed in git rev ebd4f2a721286
Comment 2 Meng Bo 2012-04-10 08:03:44 UTC 
verified with devenv_1704,
issue has been fixed.
Comment 3 Mike McGrath 2012-04-10 14:47:00 UTC 
Re opening, this commit has been reverted as it broke the automated testing.
Comment 4 Ravi Sankar 2012-04-10 21:57:00 UTC 
Fixed in git rev a4f2e631e67a6
Comment 5 jizhao 2012-04-11 05:07:05 UTC 
Verified on devenv_1713.