As stated before we gather facts as root user, so we have access to
/sys/devices/virtual/dmi/id/{product_name,sys_vendor}.
Also dmidecode is installed, but is not used because before mentioned paths
are accessible.
Also this happens only from time to time on one or two of our hosts (we
have 1300 hosts).
On each ansible-playbook run, different 1 to 2 hosts appear with a
undefined ansible_system_vendor fact,
sometimes also ansible_product_name is undefined.
Sometimes a ansible-playbook run finishes with no undefined Ansible facts.
And as also stated before, this happened after updating our Ansible from
2.3.3 to 2.10.8.
We never ever saw this problem with Ansible 2.3.3, which was running fine
for years.
Brian Coca schrieb am Dienstag, 11. Mai 2021 um 15:27:07 UTC+2:
> from the code, you don't have access to stat
> /sys/devices/virtual/dmi/id/product_name (or if you do, you cannot
> access /sys/devices/virtual/dmi/id/sys_vendor)
> and executing dmidecode it does not provide this info (not installed,
> lack of permissions, etc).
>
> --
> ----------
> Brian Coca
>
>
--
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/f4966e9a-32b0-4f5c-903f-ee3fc5c43ddcn%40googlegroups.com.
