Thanks For pointing the direction Jordan!
I was able to solve the problem by installing libc6_2.31 on my WSL Ubuntu.
The steps are as following:
Download libc6_2.31-0ubuntu9_amd64.deb.zip
<https://github.com/microsoft/WSL/files/4603734/libc6_2.31-0ubuntu9_amd64.deb.zip>
mv libc6_2.31-0ubuntu9_amd64.deb.zip libc6_2.31-0ubuntu9_amd64.deb
sudo dpkg -i libc6_2.31-0ubuntu9_amd64.deb
When I ran "ansible localhost -m ping" again, I was able to get the
following:
localhost | SUCCESS => {
"ansible_facts": {
"discovered_interpreter_python": "/usr/bin/python3"
},
"changed": false,
"ping": "pong"
}
As Jordan mentioned, this is a problem on the WSL side rather than Ansible
itself. Hope the above helps whoever encountered the same problem.
On Monday, June 1, 2020 at 8:25:29 PM UTC-4, Jordan Borean wrote:
>
> With the further details exposed by -vvv we can see the error message when
> it tried to create the temp folder
>
> sleep: cannot read realtime clock
>>
>
> A quick google search brings up an issue on the WSL repo about this
> problem https://github.com/microsoft/WSL/issues/4898. Looks like there
> are some workarounds in that post that indicate it's due to a recent
> package update that isn't handled by WSL. Ansible has no guarantees that it
> will work properly on WSL, while most things are fine you've encountered
> one of those edge cases which stop us from officially supporting/testing
> Ansible on this platform. There is nothing we can do here but rely on WSL
> implementing the POSIX syscalls that Ansible relies on.
>
> Thanks
>
> Jordan
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/e7a6dfc9-ecf6-40b5-bc23-a0ac737e1571%40googlegroups.com.
