Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2131761 - 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
Summary: hammer cannot use the cluster name or id as valid input when clusters are re...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - VMWare
Version: 6.9.0
Hardware: All
OS: Linux
high
high
Target Milestone: 6.11.4
Assignee: Chris Roberts
QA Contact: Lukáš Hellebrandt
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-10-03 15:22 UTC by Odilon Sousa
Modified: 2024-12-20 21:42 UTC (History)
10 users (show)

Fixed In Version: foreman-3.1.1.24-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1994945
Environment:
Last Closed: 2022-10-27 13:08:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 35438 0 Normal Closed hammer cannot use the cluster name or id as valid input when clusters are residing inside folders and fails with error f... 2022-10-03 15:22:38 UTC
Github theforeman foreman pull 9383 0 None Merged Fixes #35438 - Unescape cluster on compute resource controller 2022-10-03 15:22:38 UTC
Github theforeman hammer-cli-foreman pull 604 0 None Merged Refs #35438 - Enhance VMware listing commands and switch to cluster_name param 2022-10-03 15:22:38 UTC
Red Hat Issue Tracker SAT-12371 0 None None None 2022-10-03 15:22:38 UTC
Red Hat Product Errata RHSA-2022:7242 0 None None None 2022-10-27 13:08:55 UTC

Comment 3 Lukáš 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.
Comment 8 errata-xmlrpc 2022-10-27 13:08:46 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.