Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
Hammer command to create vmware host missing boot_order from compute-attributes.
Version-Release number of selected component (if applicable):
Red Hat Satellite 6.9
How reproducible:
It looks like 'boot_order' attributes is not listed in vmware compute profile section.
# hammer compute-profile values create --help
---snip----
VMware:
--volume:
name
storage_pod Storage Pod ID from VMware
datastore Datastore ID from VMware
mode persistent/independent_persistent/independent_nonpersistent
size_gb Integer number, volume size in GB
thin true/false
eager_zero true/false
controller_key Associated SCSI controller key
--interface:
compute_type Type of the network adapter, for example one of:
VirtualVmxnet3
VirtualE1000
See documentation center for your version of vSphere to find more details about available adapter types:
https://www.vmware.com/support/pubs/
compute_network Network ID or Network Name from VMware
--compute-attributes:
cluster Cluster ID from VMware
corespersocket Number of cores per socket (applicable to hardware versions < 10 only)
cpus CPU count
memory_mb Integer number, amount of memory in MB
path Path to folder
resource_pool Resource Pool ID from VMware
firmware automatic/bios/efi
guest_id Guest OS ID form VMware
hardware_version Hardware version ID from VMware
memoryHotAddEnabled Must be a 1 or 0, lets you add memory resources while the machine is on
cpuHotAddEnabled Must be a 1 or 0, lets you add CPU resources while the machine is on
add_cdrom Must be a 1 or 0, Add a CD-ROM drive to the virtual machine
annotation Annotation Notes
scsi_controllers List with SCSI controllers definitions
type - ID of the controller from VMware
key - Key of the controller (e.g. 1000)
------snip---------
Actual results:
'boot_order' not available with compute-attributes
Expected results:
'boot_order' should be available with compute-attributes
Additional info:
This is listed in section "1.8.1. JSON Formatted Content" from following hammer cli guide
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/pdf/hammer_cli_guide/hammer-cli-guide.pdf
Verified.
Tested on Satellite 6.12.0 Snap 7.0
Steps:
1. # hammer compute-profile values create --help
Observation:
In the help stdout, the boot_order option is included under --compute-attributes for VMware and Libvirt compute-profiles
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.12 Release), 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:8506
Description of problem: Hammer command to create vmware host missing boot_order from compute-attributes. Version-Release number of selected component (if applicable): Red Hat Satellite 6.9 How reproducible: It looks like 'boot_order' attributes is not listed in vmware compute profile section. # hammer compute-profile values create --help ---snip---- VMware: --volume: name storage_pod Storage Pod ID from VMware datastore Datastore ID from VMware mode persistent/independent_persistent/independent_nonpersistent size_gb Integer number, volume size in GB thin true/false eager_zero true/false controller_key Associated SCSI controller key --interface: compute_type Type of the network adapter, for example one of: VirtualVmxnet3 VirtualE1000 See documentation center for your version of vSphere to find more details about available adapter types: https://www.vmware.com/support/pubs/ compute_network Network ID or Network Name from VMware --compute-attributes: cluster Cluster ID from VMware corespersocket Number of cores per socket (applicable to hardware versions < 10 only) cpus CPU count memory_mb Integer number, amount of memory in MB path Path to folder resource_pool Resource Pool ID from VMware firmware automatic/bios/efi guest_id Guest OS ID form VMware hardware_version Hardware version ID from VMware memoryHotAddEnabled Must be a 1 or 0, lets you add memory resources while the machine is on cpuHotAddEnabled Must be a 1 or 0, lets you add CPU resources while the machine is on add_cdrom Must be a 1 or 0, Add a CD-ROM drive to the virtual machine annotation Annotation Notes scsi_controllers List with SCSI controllers definitions type - ID of the controller from VMware key - Key of the controller (e.g. 1000) ------snip--------- Actual results: 'boot_order' not available with compute-attributes Expected results: 'boot_order' should be available with compute-attributes Additional info: This is listed in section "1.8.1. JSON Formatted Content" from following hammer cli guide https://access.redhat.com/documentation/en-us/red_hat_satellite/6.9/pdf/hammer_cli_guide/hammer-cli-guide.pdf