# ansible.builtin.setup does not always report the partition UUID

**URL:** <https://forum.ansible.com/t/ansible-builtin-setup-does-not-always-report-the-partition-uuid/33996>\
**Category:** Ansible Developer\
**Created:** [October 9, 2020, 3:08pm UTC](https://forum.ansible.com/t/ansible-builtin-setup-does-not-always-report-the-partition-uuid/33996 "2020-10-09T15:08:58Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Claude\_Robitaille](https://avatars.discourse-cdn.com/v4/letter/c/8edcca/32.png) [@Claude\_Robitaille](https://forum.ansible.com/u/Claude_Robitaille)\
**Post date:** [October 9, 2020, 3:08pm UTC](https://forum.ansible.com/t/ansible-builtin-setup-does-not-always-report-the-partition-uuid/33996/1 "2020-10-09T15:08:58Z")

</div>

Hello,

ansible.builtin.setup is not reliable in reporting the partition UUIDs. It uses /dev/disk/by-uuid (in linux.py: get\_partition\_uuid(partname)), which is not a reliable source of information. I have a situation where 1 of the partitions is missing whereas blkid do report correctly the UUID.

Can linux.py be modified to used blkid instead of /dev/disk/by-uuid?