We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I have described the issue when adding a remote machine as execution node to AWX https://www.reddit.com/r/ansible/comments/1gvq6q7/adding_a_remote_node_as_an_instance_to_awx/
The solution is downgrading to v1.4.9
In v1.5.0, it looks like the first octet of remote VM ip address (136) is interpreted as remote work unit number.
`# receptorctl --socket /var/run/receptor/receptor.sock work list
"136.156.x.xruxrZvwN": { "Detail": "exit status 0", "ExtraData": null, "State": 2, "StateName": "Succeeded", "StdoutSize": 121, "WorkType": "ansible-runner" },`
The text was updated successfully, but these errors were encountered:
Confirm this issue also appears on receptor 1.4.11.
Sorry, something went wrong.
we have root caused this issue to be a receptor version miss match between the installer and the EE, Latest vs 1.4.9.
We are working with the teams now to bring ee up to the latest
No branches or pull requests
I have described the issue when adding a remote machine as execution node to AWX
https://www.reddit.com/r/ansible/comments/1gvq6q7/adding_a_remote_node_as_an_instance_to_awx/
The solution is downgrading to v1.4.9
In v1.5.0, it looks like the first octet of remote VM ip address (136) is interpreted as remote work unit number.
`# receptorctl --socket /var/run/receptor/receptor.sock work list
"136.156.x.xruxrZvwN": {
"Detail": "exit status 0",
"ExtraData": null,
"State": 2,
"StateName": "Succeeded",
"StdoutSize": 121,
"WorkType": "ansible-runner"
},`
The text was updated successfully, but these errors were encountered: