8000 Give receptor subprocess a nodeID by fosterseth · Pull Request #501 · ansible/receptor · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Give receptor subprocess a nodeID #501

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

fosterseth
Copy link
Member
@fosterseth fosterseth commented Nov 19, 2021

related issue #470

When work units are started, a separate receptor process is started to run the command (that way if the main receptor process goes down, we can still monitor whatever command is running, i.e. ansible-runner)

If this receptor process does not have a node ID, receptor will try to use os.hostname. If hostname begins with "localhost", receptor will error out, as "localhost" is a reserved keyword in receptor to mean "this node".

To avoid this scenario, we should just give the receptor a nodeID. Since this receptor process is not joining a mesh, the name really doesn't matter, so I just chose worker. We could also give it the same name as the parent receptor node.

@fosterseth fosterseth force-pushed the start_receptor_subprocess_with_a_nodeid branch from 0fc7915 to 4c3c12f Compare November 19, 2021 16:30
When work units are started, a separate receptor process is ran
If this receptor process does not have a node ID, receptor will try to
use os.hostname. If hostname begins with "localhost", receptor will
error out. To avoid this scenario, we should just give the receptor a
nodeID. Since this receptor process is not joining a mesh, the name
really doesn't matter.
@fosterseth fosterseth force-pushed the start_receptor_subprocess_with_a_nodeid branch from 4c3c12f to 687c96e Compare January 10, 2022 23:13
@fosterseth fosterseth merged commit 8429fb9 into ansible:devel Jan 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0