Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1693195

Summary: Guarantee foreman-tasks / dynflow UP and running when dynflowd looks like ok
Product: Red Hat Satellite 6 Reporter: Waldirio M Pinheiro <wpinheir>
Component: Tasks PluginAssignee: satellite6-bugs <satellite6-bugs>
Status: NEW --- QA Contact: Jan Hutaƙ <jhutar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.2CC: aruzicka, inecas
Target Milestone: UnspecifiedKeywords: EasyFix, Triaged
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Waldirio M Pinheiro 2019-03-27 10:27:31 UTC
Description of problem:
Sometimes dynflowd looks like be ok and running but for any reason, only the process "dynflow_executor_monitor" is up, we are not able to see anymore the "dynflow_executor" process. Another way to check this behavior is via "qpid_stat -q", analyzing the queue "katello_event_queue" the consumer appear as "0". This means Satellite will be impacted until the next dynflowd restart.

Version-Release number of selected component (if applicable):
6.4.z
6.3.z


How reproducible:
100%

Steps to Reproduce:
0. Check all the process related to dynflow (ps -ef | grep dynflow)

1. Kill the process dynflow_executor (kill -9 <dynflow_executor pid>)

2. Check all the process related to dynflow (ps -ef | grep dynflow)
   At this time, you should see only dynflow_executor_monitor

3. Run the command below
qpid-stat -q --ssl-certificate=/etc/pki/katello/qpid_client_striped.crt -b amqps://localhost:5671 | grep katello_event_queue
    At this time, the Cons column will appear as 0

4. Run the commands below
# systemctl status dynflow
# katello-service status

Note. Both will appear correctly and without issues however, no one is consuming  que "katello_event_queue"


Actual results:
dynflow will be stopped and everything tends to fail.

Expected results:
Satellite be reliable and guarantee dynflow_executer UP and running when dynflowd look like be ok.

Additional info: