Skip to content
New issue

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

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

Already on GitHub? # to your account

Error adding remote execution node with version 1.5.0 #1227

Open
rakesh-p opened this issue Nov 26, 2024 · 3 comments
Open

Error adding remote execution node with version 1.5.0 #1227

rakesh-p opened this issue Nov 26, 2024 · 3 comments

Comments

@rakesh-p
Copy link

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"
},`

@unnecessary-username
Copy link

Confirm this issue also appears on receptor 1.4.11.

@AaronH88
Copy link
Contributor

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

@AaronH88
Copy link
Contributor

AaronH88 commented Dec 4, 2024

receptor 1.5.1 has been released with a fix for this. We tested it to make sure it is backwards compatible with your ee version 1.4.9

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

3 participants