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:
If you run "service foreman-tasks start", this will kick off foreman-tasks. However, "hammer ping" will return "fail" for foreman-tasks for a few dozen seconds after the systemctl script has returned. This makes it appear as if startup has failed.
After 10-30 seconds, "hammer ping" will show success for foreman-tasks, and things will operate normally. While this is a minor issue, the delay can be enough time for the user to think something is wrong and start checking log files, only to retry the hammer ping and get a success message.
Version-Release number of selected component (if applicable): 6.2.7
Steps to Reproduce:
1. service foreman-tasks stop
2. service foreman-tasks start
3. hammer ping
Actual results:
candlepin:
Status: ok
Server Response: Duration: 19ms
candlepin_auth:
Status: ok
Server Response: Duration: 19ms
pulp:
Status: ok
Server Response: Duration: 26ms
foreman_tasks:
Status: FAIL
Server Response:
Expected results:
foreman_tasks should be successful immediately, or the service script should wait
I think there was a misunderstanding of this bug and the fix. I think the correct BZ the attached issues is meant to solve is this in https://bugzilla.redhat.com/show_bug.cgi?id=1538688.
@adam: can you recall a reason why this BZ was linked to corresponding patch? It doesn't look like it could fix this particular problem.
Comment 8Satellite Program
2018-12-11 13:04:34 UTC
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.
Description of problem: If you run "service foreman-tasks start", this will kick off foreman-tasks. However, "hammer ping" will return "fail" for foreman-tasks for a few dozen seconds after the systemctl script has returned. This makes it appear as if startup has failed. After 10-30 seconds, "hammer ping" will show success for foreman-tasks, and things will operate normally. While this is a minor issue, the delay can be enough time for the user to think something is wrong and start checking log files, only to retry the hammer ping and get a success message. Version-Release number of selected component (if applicable): 6.2.7 Steps to Reproduce: 1. service foreman-tasks stop 2. service foreman-tasks start 3. hammer ping Actual results: candlepin: Status: ok Server Response: Duration: 19ms candlepin_auth: Status: ok Server Response: Duration: 19ms pulp: Status: ok Server Response: Duration: 26ms foreman_tasks: Status: FAIL Server Response: Expected results: foreman_tasks should be successful immediately, or the service script should wait