Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionStephen Wadeley
2021-12-01 07:31:56 UTC
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:
- https://<test_host>.redhat.com/foreman_tasks/tasks/b75e5863-55f3-49b7-9c88-d27d459aef0e
this is understandable, its a side effect of recent changes in task info [1] , 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
satellite-6.10.1-2.el7sat.noarch
How reproducible:
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.
Actual results:
ISE
Expected results:
no ISE
Additional info:
[1]
Bug 2017533 - API call to generate applicability does not return task info
(In reply to Justin Sherrill from comment #2)
> Stephen, to be clear, you'd expect a 400 Bad Request?
Hi Justin
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.
Thank you
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.
https://access.redhat.com/errata/RHSA-2022:5498