Bug 807513 - Domain is destroyed successfully even if you specify a wrong namespace
Summary: Domain is destroyed successfully even if you specify a wrong namespace
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OKD
Classification: Red Hat
Component: Pod
Version: 2.x
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: ---
Assignee: Ravi Sankar
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-28 02:47 UTC by jizhao
Modified: 2015-05-15 01:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-13 18:31:11 UTC
Target Upstream Version:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.