hammer cannot use the cluster name or id as valid input when clusters are residing inside folders and fails with error Fog::Vsphere::Compute::NotFound error
Comment 3Lukáš Hellebrandt
2022-10-24 09:05:06 UTC
Verified with Sat 6.11.4 snap 1.0.
For vSphere versions 6 and 7, followed the instructions from OP + succesfully created hosts using the compute profiles. No related traceback.
$ hammer compute-profile values create --compute-profile-id 2 --compute-resource-id 5 '--compute-attributes={"cpus":4,"corespersocket":2,"memory_mb":4096,"firmware":"efi","resource_pool":"Resources","cluster":"lhellebr-clusterfolder-willdelsoon/Satellite-Engineering","guest_id":"rhel8_64Guest","path":"/Datacenters/RH_Engineering/vm/","hardware_version":"Default","memoryHotAddEnabled":0,"cpuHotAddEnabled":0,"add_cdrom":0,"boot_order":["disk","network"],"scsi_controllers":[{"type":"ParaVirtualSCSIController","key":1000},{"type":"ParaVirtualSCSIController","key":1001}]}'
Compute profile attributes are set.
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 (Important: Satellite 6.11.4 Async Security Update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2022:7242