Bug 1420651
| Summary: | foreman-tasks startup returns quickly, but "hammer ping" shows failed state until startup is complete | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Chris Duryee <cduryee> |
| Component: | Tasks Plugin | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED WONTFIX | QA Contact: | Jan Hutař <jhutar> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2.7 | CC: | aruzicka, daniele, gkonda, inecas, jcallaha, jhutar, pcreech |
| Target Milestone: | Unspecified | Keywords: | Triaged, UserExperience |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-04-01 12:07:06 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Created redmine issue http://projects.theforeman.org/issues/21294 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/21294 has been resolved. 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. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/21294 has been resolved. Nothing sensible comes to my mind, probably just human error. Ok, updated the upstream issue accordingly 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. Wrond closure reason. |
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