When adding a new Bootable Volume that references a VMP, the UI shows it referencing a VMCP despite having properly labels to reference the VMP. 

This creates confusion when viewing the Bootable Volume from the DataSources or Catalog pages as they do not properly display it referencing the VMP or details such as the Operating System name or logo.

4.17, 4.18.9

100%

1. Create a VirtualMachinePreference (VMP). 
  - During my test, I used details from the windows.2k19 VMCP and just customized the VMP configuration for my use case, but the specific configuration of the VMP isn't as important. The VMP should however still include relevant annotations such as display-name and iconClass so that's visible on the Catalog page. 
2. Create a new Bootable Volume. 
  - This can be done in many ways, but I used the "Add volume" button from the Catalog page and referenced an existing volume and user preference (VMP). 
3. If the VMP labels were not added to the Bootable Volume Datasource resource when it was created, ensure the correct labels are added.
4. View the Bootable Volume / DataSource resource page.
5. View the Catalog page

The Bootable Volume / DataSource UI shows it referencing a VMCP rather than the VMP defined in the label.

The Catalog page does not display the Bootable Volumes OS name or logo icon that's referenced in the VMP.

Bootable Volumes should be able to display details from the VMP and not be restricted to only VMCPs.

As a note, there are no issues actually creating the VM from a Bootable Volume that references a VMP, this appears to be just a UI bug with how we display details on the different pages. These were two pages I noticed the issue, but not sure if there are others.