Bug 1413966
| Summary: | Upgrade w/ customer db raises "No executor available (Dynflow::Error)" at db:seed step | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sachin Ghai <sghai> | ||||||
| Component: | Tasks Plugin | Assignee: | Martin Bacovsky <mbacovsk> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Roman Plevka <rplevka> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.2.7 | CC: | bbuckingham, chrobert, egolov, hmore, inecas, mbacovsk, mmccune, oshtaier, pmoravec, rplevka | ||||||
| Target Milestone: | Unspecified | Keywords: | Triaged | ||||||
| Target Release: | Unused | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | rubygem-dynflow-0.8.13.5-1 | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1446733 (view as bug list) | Environment: | |||||||
| Last Closed: | 2017-06-20 17:53:40 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1410795 | ||||||||
| Attachments: |
|
||||||||
|
Description
Sachin Ghai
2017-01-17 13:04:40 UTC
Created attachment 1241771 [details]
upgrade error dusing db:seed step
Created attachment 1241773 [details]
foreman-debug
I was able to reproduce with the cust DB dump and rake db:migrate. I'll update once I have more details. The customer's DB contains Dynflow tasks that are in running state. We may assume the DB dump was done while foreman-tasks was running and the tasks were not finished properly. During db:seed the Dynflow that is being initiated is trying to recover and is trying to restart the tasks. When no executor is running the error is risen. It is not harmful because the task will be resumed on next executor start, but the error should not be displayed. Changing the componnent to the Tasks plugin. Created redmine issue http://projects.theforeman.org/issues/18206 from this bug Minimal reproducer for this issue: 1/ Have Foreman/Satellite with at least one Dynflow task running. (Actions::Candlepin::ListenOnCandlepinEvents in Katello/Satellite is a good candidate) 2/ kill dynflow executor while the task is running: pkill -9 -f dynflow_executor 3/ foreman-rake db:migrate You should see errors in the output E, [2017-01-24T03:00:53.032499 #9544] ERROR -- /client-dispatcher: No executor available (Dynflow::Error) Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18206 has been resolved. *** Bug 1413575 has been marked as a duplicate of this bug. *** VERIFIED on 6.2.10-2 using the reproducer in Comment #7, I was able to reproduce the issue on 6.2.9 and can confirm, that it no longer occurs on 6.2.10-2 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, 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/RHBA-2017:1553 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |