Bug 790216

Summary:	Promoting when already a promotion happening elsewhere- queue, don't error out
Product:	Red Hat Satellite	Reporter:	Jeff Weiss <jweiss>
Component:	API	Assignee:	Marek Hulan <mhulan>
Status:	CLOSED UPSTREAM	QA Contact:	Katello QA List <katello-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	dajohnso, mhulan, mmccune
Target Milestone:	Unspecified	Keywords:	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:	2013-09-19 18:16:02 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 Jeff Weiss 2012-02-13 22:59:09 UTC

Description of problem:
I don't know why we're still erroring out when we submit a promotion and there's already one in progress.  Promotions are now delayed jobs, right?  So if there's already one in progress, so what?  Just queue it.

It's really annoying to get this error.  You just stare at the screen, no idea how to find out when the other promotion is done, you just have to keep submitting.  Unless you're an admin, you might not even have permission to find out anything about the other promotion.

The other problem with this is if several users want to do a promotion, instead of processing them in the order they were requested, it's whoever buzzes in quickest after the previous promotion finishes.  The other users have to sit there twiddling their thumbs until they get win the reaction-time contest.

Version-Release number of selected component (if applicable):
katello-0.1.231-1.git.1.4ca672f.el6.noarch

How reproducible:


Steps to Reproduce:
1. 
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 2 Marek Hulan 2012-12-12 13:49:36 UTC

Currently both API and UI use asynchronous method so it should be possible. However we'll have to make sure that there are no conflicting jobs (in case more than one worker is running). I'll discuss this with someone first but the basic idea is that we disallow synchronous promoting and add a prerequisite for delayed jobs to start only when no conflicting is in progress. This way user will be able to register his promotions and he will just have to wait until some worker will be able to finish his job.

Comment 3 Mike McCune 2013-09-19 18:16:02 UTC

These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.