[WIP] Move MiqWorker record creation out of run_single_worker.rb on podified #23110
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.
On a podified environment we cannot pass a unique GUID to a worker due to how the environment is defined by the deployment (all replicas have to have the same environment).
We worked around this by creating the MiqWorker record in the pod once it starts up which allows us to create a record with a unique GUID.
This is an issue however for non-rails/ruby workers which don't use run_single_worker.rb, resulting in a pod running with not MiqWorker record created at all.
The goal here is to move creating the worker record into MiqServer for all platform types (kubernetes, systemd, and process).
TODO:
Depends on:
Fixes ManageIQ/manageiq-providers-embedded_terraform#67