Bug 2225402 - Associating a host with an VM with added "Precision Clock Device" on Satellite fails with error unknown VMODL type VirtualPrecisionClock
Summary: Associating a host with an VM with added "Precision Clock Device" on Satellit...
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-25 08:53 UTC by Jayant Bhatia
Modified: 2023-07-27 14:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-19134 0 None None None 2023-07-25 11:18:02 UTC

Description Jayant Bhatia 2023-07-25 08:53:31 UTC
Description of problem:

Compute resource VMware

While trying to associate a host with an VM with added "Precision Clock Device" the following error occurred: unknown VMODL type VirtualPrecisionClock


Version-Release number of selected component (if applicable): All Satellite versions


This could be observed because of some missing "Data Types" in the vmodl.db in the Satellite ruby interface for vSphere API (rubygem-rbvmomi). The problem is reported for vSphere Version 7.0.3 Build: 20990077. 

VMWare documentation: https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-4E6AE904-75C6-475F-8732-07E4542D7798.html

Similar issue with missing data types: https://github.com/vmware-archive/rbvmomi/issues/208

Comment 4 Sayan Das 2023-07-27 07:41:45 UTC
Reproducer steps shared by the end-user :

New virtual machine:
 1. Create New Virtual Maschine (From vSphere Web-Client)
	Guest OS Family:  	Linux
	Guest OS Version:	Red Hat Enterprise Linux 8 (64-bit)
	Compatibility: 		ESXi 7.0 U2 and later
	
	Customize hardware -> Add new device -> Precision CLock (Host System Time NTP)
	-> Build VM


2. Create Host (From RH Satellite)
3. Compute Resources -> Virtual Maschines -> Associate VM 

---> Results in error: "Oops, we're sorry but something went wrong unknown VMODL type VirtualPrecisionClock"


Existing virtual machine:

Modify hardware ((From vSphere Web-Client))
1. Add new device -> Precision CLock (Host System Time NTP)

2. All hosts -> VM Hostname -> Edit 

---> Results in error: "Oops, we're sorry but something went wrong unknown VMODL type VirtualPrecisionClock"


Note You need to log in before you can comment on or make changes to this bug.