Bug 893365

Summary:

[fork][model refactor]Delete app failed when deleting two app together

Product:

OKD

Reporter:

Ziqian SUN (Zamir) <zsun>

Component:

Pod

Assignee:

Abhishek Gupta <abhgupta>

Status:

CLOSED CURRENTRELEASE

QA Contact:

libra bugs <libra-bugs>

Severity:

medium

Docs Contact:

Priority:

medium

Version:

2.x

CC:

abhgupta, dmcphers, szhou, xtian

Target Milestone:

---

Target Release:

---

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

Fixed In Version:

fork_ami_refctr1_396+

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2013-02-14 00:44:53 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:

Attachments:

Description	Flags
Some line of development.log from the broker.	none

Description Ziqian SUN (Zamir) 2013-01-09 08:38:53 UTC

Description of problem:
If I delete two app at the same time, one of them may fail

Version-Release number of selected component (if applicable):
fork_refctr1_392

How reproducible:
always

Steps to Reproduce:
1.adding two app
rhc app create tmp1 php-5.3 -p a
rhc app create tmp2 php-5.3 -p a
2.type rhc app delete tmp1 -p a --confirm --timeout 600 in one terminal window,do not exec it.
Type rhc app delete tmp2 -p a --confirm --timeout 600 in another terminal window, do not exec it either.

3.Exec the two commands together, I mean ,run the two commands in less than 2 senconds.
  
Actual results:
One of them will return with error like the following message, and another deleted successfully

Deleting application 'tmp1' ... The server did not respond correctly. This may be an issue with the server configuration or with your connection to the server (such as a Web proxy or firewall).Please verify that you can access the OpenShift server https://ec2-107-21-171-219.compute-1.amazonaws.com/broker/rest/domains/del2bug/applications/tmp1


Expected results:
The two app should be deleted successfully.

Additional info:
1.Some of the development.log attached.
2.If I run rhc domain show after the step 3, I will get an error.
$ rhc domain show
Password: *
Applications in del2bug domain
==============================

  tmp1 @ http://tmp1-del2bug.dev.rhcloud.com/ (uuid: 50ecf524c12584a4080000a5)
  ============================================================================
/usr/lib/ruby/1.8/uri/common.rb:406:in `split': bad URI(absolute but no path): ssh:// (URI::InvalidURIError)
	from /usr/lib/ruby/1.8/uri/common.rb:485:in `parse'
	from /usr/lib/ruby/1.8/uri/common.rb:608:in `URI'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/rest/application.rb:146:in `ssh_string'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:162:in `send'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:162:in `get_properties'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:160:in `map'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:160:in `get_properties'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:57:in `display_app_properties'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:42:in `display_app'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:337:in `call'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:337:in `section'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:40:in `display_app'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:294:in `indent'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:286:in `header'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:39:in `display_app'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:337:in `call'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:337:in `section'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:351:in `paragraph'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/output_helpers.rb:38:in `display_app'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/commands/domain.rb:55:in `show'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/commands/domain.rb:54:in `each'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/commands/domain.rb:54:in `show'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:294:in `indent'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/helpers.rb:286:in `header'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/commands/domain.rb:53:in `show'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/commands.rb:137:in `send'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/commands.rb:137:in `to_commander'
	from /usr/lib/ruby/gems/1.8/gems/commander-4.1.3/lib/commander/command.rb:180:in `call'
	from /usr/lib/ruby/gems/1.8/gems/commander-4.1.3/lib/commander/command.rb:180:in `call'
	from /usr/lib/ruby/gems/1.8/gems/commander-4.1.3/lib/commander/command.rb:155:in `run'
	from /usr/lib/ruby/gems/1.8/gems/commander-4.1.3/lib/commander/runner.rb:402:in `run_active_command'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/command_runner.rb:61:in `run!'
	from /usr/lib/ruby/gems/1.8/gems/commander-4.1.3/lib/commander/delegates.rb:7:in `run!'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/lib/rhc/cli.rb:41:in `start'
	from /usr/lib/ruby/gems/1.8/gems/rhc-1.3.2/bin/rhc:18
	from /usr/bin/rhc:19:in `load'
	from /usr/bin/rhc:19

Comment 1 Ziqian SUN (Zamir) 2013-01-09 08:40:34 UTC

Created attachment 675315 [details]
Some line of development.log from the broker.

Comment 2 Abhishek Gupta 2013-01-10 05:23:37 UTC

This is now fixed and should be available in the next fork ami -- fork_ami_refctr1_396+

Comment 3 Ziqian SUN (Zamir) 2013-01-14 02:31:59 UTC

I have checked this with fork_ami_refctrl_404 ,and the bug has been fixed. Move the bug to VERIFIED.