-
Notifications
You must be signed in to change notification settings - Fork 33
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
Failure on TASK [fubarhouse.golang : Go-Lang | Moving to installation directory] #66
Comments
@markdorison first of all thanks for submitting a ticket! Second, as you're getting the following: You can use the following
This will rule out any obvious errors. I am intending on going back through this role again for a new release - much like what I've just completed for my curl role. |
@fubarhouse: Thanks! (I work with @markdorison and it was me who ran into this issue). The machine the Ansible playbook was running from does have a passphrase-protected ssh-key to the remote machine, but we know it was But reading through the code, it looks like it's the I'll run the playbook again at a quiet time with a value for |
@ctorgalson that actually describes something I can diagnose much better, so I'll look into this for you and respond. Under no circumstance should Are you able to provide any given reason the following two tasks would be skipped?
|
@fubarhouse Thanks. I think I can explain what's failing. Background
Analysis
I think (4) is the core issue, though I'm not sure what an appropriate solution might be--installing in individual users' home directories is not a viable solution for us :) PS: according to Ansible's documentation, the Synchronize module "...is run and originates on the local host where Ansible is being run". Which sounds like the generated |
@ctorgalson I've actually been doing a bit of work on similar things, but I've rolled some more changes to the dev branch in and kicked off some tests, here's a summary.
You can test this out on the dev-2.5.x branch, but I'll get a release out in the next day for you. I would be appreciative if you could tell me if the above changes solve your problem! Link to tests: |
2.5.0 is officially released, available via the galaxy. As previously stated, I'd like to know if the changes have resolved your problems. |
@fubarhouse I updated the role to 2.5.0. When attempting a run it fails, but in a different place:
|
The cause of this failure seems to be further upstream in the playbook as a bunch of tasks are being skipped and |
I have just identified the problem, so I'll get a fix under way asap. Edit: see See 0231ee8 I'm just waiting for some tests (now running) to complete and I'll release it. Edit: 2.6.1 is released, which includes the above commit. Changelog will be added tonight, but it's available via the galaxy. Edit (again): If the distribution tasks are skipping, the removal of the old Go install will also fail. It's my recommendation to delete your GOROOT in the event this fails again. |
This role has worked for me in the past but I am now encountering the following error on the "Moving to installation directory" task. I redacted the information about the box it is running on.
fatal: [FQDN_REDACTED -> IP_REDACTED]: FAILED! => {"changed": false, "cmd": "/usr/bin/rsync --delay-updates -F --compress --delete-after --archive --rsh 'ssh -S none -o StrictHostKeyChecking=no' --rsync-path=\"sudo rsync\" --out-format='<<CHANGED>>%i %n%L' \"/tmp/go/\" \"IP_REDACTED:/root/go\"", "failed": true, "msg": "Warning: Permanently added 'IP_REDACTED' (ECDSA) to the list of known hosts.\r\nPermission denied (publickey).\r\nrsync: connection unexpectedly closed (0 bytes received so far) [sender]\nrsync error: unexplained error (code 255) at io.c(226) [sender=3.1.0]\n", "rc": 255}
The text was updated successfully, but these errors were encountered: