setup: Windows Setup wrong epoch timestamp (get-date prints epoch + local_tz) about ansible.windows HOT 4 CLOSED

Hi @jborean93,

I give a try to your fix #73, but still get the same error: msg: Invalid value for epoch value (1597253655.92744) when I try to use it with strftime.

I tried by installing the 'ansible.windows' collection via ansible-galaxy but also by 'git cloning' the master branch into my virtualenv and get the same result. (and of course I cleaned the facts cache each time)

Maybe it's due to some version stuff on the remote windows hosts?

from ansible.windows.

So the format of the value has not changed with that PR but rather the timezone the value represents has. If you were having issues trying to filter it with strftime then you will continue to have issues after that change.

from ansible.windows.

Indeed. I misunderstood the original bug report. Sorry for that.

Never the less, I created an issue about strftimenot dealing with float numbers here: ansible/ansible#71257.

In the meantime, I apply the following split filter as workaround: 

{{ '%b %d %Y %H:%M:%S %Z' | strftime(ansible_date_time.epoch.split('.')[0]) }}

from ansible.windows.

I also found the reference of %f in the python strftime doc. I didn't added it because I need that precision in my template.

from ansible.windows.