Bug 734526

Summary: Promotion failure when trying to simultaneously trying to promote 2 changesets should be less ambiguous
Product: Red Hat Satellite Reporter: Corey Welton <cwelton>
Component: WebUIAssignee: Justin Sherrill <jsherril>
Status: CLOSED CURRENTRELEASE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-22 17:54:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 747354    

Description Corey Welton 2011-08-30 17:08:40 UTC
Description of problem:
"Failed to promote: Cannot promote a changeset while another is being promoted."  This message doesn't tell the user which one failed and which is currently in process.

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


How reproducible:


Steps to Reproduce:
1.  Configure multiple products and multiple associate change sets.
2.  Attempt to promote both (near) simultaneously
3.  Wait for failure message
  
Actual results:
Failed to promote: Cannot promote a changeset while another is being promoted.

Expected results:
Something more like
Failed to promote (My Failed Changeset): Cannot promote a changeset while another (My Changeset In Process) is being promoted.

Additional info:

Comment 1 Justin Sherrill 2011-09-19 16:58:22 UTC
should be fixed here:  

5bf345b792923605f6174792c027191cc7effc3d



Also fixed a few other issues i noticed with that page (changeset would not show it is being promoted if you refreshed the page).

Comment 2 Corey Welton 2011-09-23 18:41:05 UTC
QA verified.

Comment 5 Mike McCune 2013-08-16 18:14:14 UTC
getting rid of 6.0.0 version since that doesn't exist