Timeline for Joining domain via Ansible returns error "Already joined to this domain" while via shell is OK
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 3, 2024 at 10:35 | vote | accept | dr_ | ||
| Dec 3, 2024 at 10:34 | answer | added | dr_ | timeline score: 0 | |
| Nov 13, 2024 at 18:24 | comment | added | Sotto Voce | @dr_ that's good, but I asked what happens when you invoke a playbook containing just the two tasks you posted in the question. It's not a thought experiment that can be satisfied by saying "the previous tasks don't matter", but a real experiment that must be performed to see the results. Based on my own experience troubleshooting similar Ansible problems, it's necessary to actually perform the test. | |
| Nov 13, 2024 at 17:18 | comment | added | ctx | Maybe the commands don't run as the same user? You could add the realm list command to a task right before the Realm join into domain task. | |
| Nov 13, 2024 at 13:15 | comment | added | dr_ | Thanks for your questions. I have answered them in the post. | |
| Nov 13, 2024 at 13:14 | history | edited | dr_ | CC BY-SA 4.0 | added 632 characters in body |
| Nov 13, 2024 at 11:45 | comment | added | Sotto Voce | Two questions: (a) what happens when you type the same command being invoked by Ansible? I.e., the full /bin/bash -c ..... and (b) what happens when you run a playbook that has only the two tasks you posted in this question, and nothing else? (i.e., a simulation of what you type manually) | |
| Nov 13, 2024 at 11:28 | history | asked | dr_ | CC BY-SA 4.0 |