Description of problem:
While running a test, setting up tools repo failed because setup procedure did not wait for CV to be published before attempting to promote it:
ForemanTasks::Lock::LockConflict: Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.
Conflicts with tasks:
this is understandable, its a side effect of recent changes in task info  , setup procedure no longer has a task ID to poll for completion,
but then this error was also seen:
500 Server Error: Internal Server Error for url <redacted>/katello/api/v2/repositories/177/sync
Version-Release number of selected component (if applicable):
~]# rpm -q satellite
Test fails every time but not sure about the ISE, I run again on new install to get cleaner logs if required.
Steps to Reproduce:
1. Run a test that use API to set up tools repo, but does not wait for Foreman Task completion between steps.
Bug 2017533 - API call to generate applicability does not return task info
Stephen, to be clear, you'd expect a 400 Bad Request?
(In reply to Justin Sherrill from comment #2)
> Stephen, to be clear, you'd expect a 400 Bad Request?
that would be better than an ISE
Would it be possible to give some clue that the request is just invalid at that time rather than bad?
503 Service Unavailable ?
Most of the HTTP error codes seem to have very precise meanings.
For this bug 400 Bad Request is OK, 503 Service Unavailable with some clue as to the reason is RFE.
Created redmine issue https://projects.theforeman.org/issues/34680 from this bug
Upstream bug assigned to firstname.lastname@example.org
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/34680 has been resolved.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.