Bugfix: Startup states on minions are not being written to mysql returner #34773
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…urn jid into the jid list table.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Allows salt-run jobs.list_jobs etc. to work correctly with a minion triggered mysql returner.
Sets a proper jid for minion based mysql returner, similar to local_cache returner.
What issues does this PR fix or reference?
If a startup state is specified and 'ext_job_cache' is set to 'mysql' on a minion. The mysql returner does not correctly write the state run to Mysql.
New Behavior
Minion will write the startup state to mysql.
Master runners have visibility of the startup state run.
Tests written?
No