Hide Forgot
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:
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.
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.