The pvcreate(8) manpage lists the perferred MBR partition type (0x8E) for LVM.
Please add the same for GPT partitions, where it is (according to https://en.wikipedia.org/wiki/GUID_Partition_Table#Partition_type_GUIDs):
OK, let's add this one...
GPT partition type added to pvcreate(8) manpage.
[root@virt-010 ~]# man pvcreate | grep -A 5 -B 5 GPT
pvcreate initializes PhysicalVolume for later use by the Logical Volume
Manager (LVM). Each PhysicalVolume can be a disk partition, whole
disk, meta device, or loopback file. For DOS disk partitions, the par-
tition id should be set to 0x8e using fdisk(8), cfdisk(8), or a equiva-
lent. For GUID Partition Table (GPT), the id is
E6D6D379-F507-44C2-A23C-238F2A3DF928. For whole disk devices only the
partition table must be erased, which will effectively destroy all data
on that disk. This can be done by zeroing the first sector with:
dd if=/dev/zero of=PhysicalVolume bs=512 count=1
lvm2-2.02.141-2.el6 BUILT: Wed Feb 10 14:49:03 CET 2016
lvm2-libs-2.02.141-2.el6 BUILT: Wed Feb 10 14:49:03 CET 2016
lvm2-cluster-2.02.141-2.el6 BUILT: Wed Feb 10 14:49:03 CET 2016
udev-147-2.71.el6 BUILT: Wed Feb 10 14:07:17 CET 2016
device-mapper-1.02.115-2.el6 BUILT: Wed Feb 10 14:49:03 CET 2016
device-mapper-libs-1.02.115-2.el6 BUILT: Wed Feb 10 14:49:03 CET 2016
device-mapper-event-1.02.115-2.el6 BUILT: Wed Feb 10 14:49:03 CET 2016
device-mapper-event-libs-1.02.115-2.el6 BUILT: Wed Feb 10 14:49:03 CET 2016
device-mapper-persistent-data-0.6.2-0.1.rc1.el6 BUILT: Wed Feb 10 16:52:15 CET 2016
The GUID code might be a confusing information as some tools don't require this specific code as input. Like in fdisk user can list the partition IDs and select them by typing the code provided on the screen (8e for LVM partition) and do the same in gdisk (8e00 for LVM partition) alternatively user can use hex code in fdisk to select partition type (0x8e) and GUID in gdisk (E6D6D379-F507-44C2-A23C-238F2A3DF928). Both methods work in the same way.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.