Bug 2124287

Summary: Document that yggdrasild must be running at pull-mode job invocation time
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: DocumentationAssignee: Zuzana Lena Ansorgova <zuansorg>
Documentation sub component: default QA Contact:
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: high    
Priority: high CC: aruzicka, bbuckingham, saydas, vferschm
Version: 6.12.0   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2124419 (view as bug list) Environment:
Last Closed: 2022-11-28 11:00: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: 2124419    
Bug Blocks:    

Description Pavel Moravec 2022-09-05 14:11:04 UTC
The problem / reproducer:

1) stop yggdrasild on a client:
systemctl stop yggdrasild

2) invoke a pull-mqtt REX job to the client

3) start the service back:
systemctl start yggdrasild

4) check status of the job - it will be hung forever

(the reason is yggd start drops all incoming notifications)


We *need* to document this *somehow*. Not sure about the most appropriate way, if:
- in install/config guide with pull-mqtt config description, as a warning
- in release notes (where I assume the pull-mqtt feature will be mentioned either way), again as a warning
- as a KCS (that I am happy to write, but I feel it is rather insufficient post-mortem documentation)