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.
Description of problem:
Running satellite-change-hostname forgets to update one old hostname reference.
When a task fails to be executed due to an acquired lock, an error like:
Could not synchronize the repository:
Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.
Conflicts with tasks:
- https://old.hostname.com/foreman_tasks/tasks/bc2cb786-21d5-4c24-b7f6-33048ea1032a
is raised, pointing to the *old* FQDN.
Replacing the FQDN to a current one shows proper task (that acquired the lock), so it is just somewhere in foreman-tasks that still points to the old FQDN.
Version-Release number of selected component (if applicable):
Sat 7.0 snap 9
How reproducible:
100%
Steps to Reproduce:
1. satellite-change-hostname new-satellite.redhat.com
2. For a (bigger) repo with a feed URL, invoke its sync twice concurrently:
hammer repository synchronize --organization-id 1 --async --id 4
hammer repository synchronize --organization-id 1 --async --id 4
3. Check hostname in the error raised.
Actual results:
3. shows old FQDN
Expected results:
3. to show new FQDN
Additional info:
(In reply to Brad Buckingham from comment #1)
> Is this a regression from Satellite 6.10?
Yes it is a regression.
Renaming my Sat6.10 to pmoravec-sat610-renamed.brq2.redhat.com :
hammer> repository synchronize --organization-id 1 --id 3 --async
Repository is being synchronized in task 5b16c769-26b8-469f-be4d-8474688e22d2.
hammer> repository synchronize --organization-id 1 --id 3 --async
Could not synchronize the repository:
Required lock is already taken by other running tasks.
Please inspect their state, fix their errors and resume them.
Conflicts with tasks:
- https://pmoravec-sat610-renamed.brq2.redhat.com/foreman_tasks/tasks/5b16c769-26b8-469f-be4d-8474688e22d2
hammer>
That is correct URL - on 6.10 .
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