Bug 1011322

Summary: Sometimes meet "Failed to correctly execute all parallel operations. " error when stopping postgresql or restarting nodejs app
Product: OpenShift Online Reporter: Zhe Wang <zhewang>
Component: ContainersAssignee: Jhon Honce <jhonce>
Status: CLOSED CURRENTRELEASE QA Contact: libra bugs <libra-bugs>
Severity: low Docs Contact:
Priority: low    
Version: 2.xCC: dmcphers, lzhang, xtian, zhewang
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: 2014-03-12 03:05:41 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
the relevant logs of the errors none

Description Zhe Wang 2013-09-24 05:30:15 UTC
Created attachment 802048 [details]
the relevant logs of the errors

Description of problem:
When stopping postgresql, it will sometime report the error:

Unable to complete the requested operation due to: Failed to correctly execute all parallel operations. 

Specifically, there were 5 jobs running against 1 large instance simultaneously. Please refer to the attached development.log for more info of the error.

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

How reproducible:
sometimes (of low frequency, only 2/29 postgresql cases failed due to this error. Have not found other cases failed by this problem yet.)

Steps to Reproduce:
1. create an app with postgresql db added
2. try to stop the postgresql cartridge
3.

Actual results:
Stopping the postgresql cartridge would sometimes fail with the error:

rhc cartridge stop postgresql-9.2 -a oprtj0 -l nimbeutz -p 'redhat' --insecure --server ec2-54-242-42-194.compute-1.amazonaws.com
Stopping postgresql-9.2 ... Unable to complete the requested operation due to: Failed to correctly execute all parallel operations.
Reference ID: 045f4eca49ceb89c04e58c70c82bedd8

Expected results:
Stopping the postgresql cartridge should be successful.

Additional info:

Comment 1 Dan McPherson 2014-02-07 23:57:15 UTC
Is this still a problem?

Comment 2 Zhe Wang 2014-02-18 09:32:09 UTC
Have not met this issue in recent sprints.

Comment 3 Zhe Wang 2014-02-19 01:53:33 UTC
Move the bug to VERIFIED refer to comment#2.