Bug 1384214
Summary: | Remote Execution jobs do not get successful task creation when using 'schedule future execution' | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Craig Donnelly <cdonnell> |
Component: | Remote Execution | Assignee: | satellite6-bugs <satellite6-bugs> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 6.2.2 | CC: | aruzicka, bbuckingham, chrobert, gpayelka, inecas, jcallaha, jentrena |
Target Milestone: | Unspecified | Keywords: | Triaged |
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: | 2016-11-21 11:15:27 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: |
Description
Craig Donnelly
2016-10-12 20:28:54 UTC
the first thing to check would be if there is a "delayed_executor" running. It is the thing that handles running scheduled tasks in Dynflow. One way to do that would be opening the Dynflow console, in the "Status" tab[1], clicking "check status" and checking if any of the entries has "delayed_executor" => true in the meta column and is marked as valid. The CLI equivalent would be running: cat <<-END | foreman-rake console states = ForemanTasks.dynflow.world.worlds_validity_check(false) ForemanTasks.dynflow.world.coordinator.find_worlds.map do |world| world.meta.merge(:valid => states.fetch(world.id, :invalid)) end END This should print the same information as in the Dynflow console, so the same check should be done here. If there is no entry with delayed_executor or the world with it is invalid, restarting foreman-tasks service should fix it. Hope this helps or at least helps us get some more information about what's going on. [1] https://fqdn.of.the.satellite.server/foreman_tasks/dynflow/worlds It looks like the cause of this BZ is directly tied to the issue in BZ 1390931. Once I applied the workaround: https://bugzilla.redhat.com/show_bug.cgi?id=1390931#c2 Everything was able to proceed at planned scheduled times completely without issue. Thanks for the help, Ivan. Closing since this is merely a symptom of another issue which is being handled in BZ#1390931 |