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 2013611 - Hammer compute-profile create missing 'boot_order' from 'compute-attributes'
Summary: Hammer compute-profile create missing 'boot_order' from 'compute-attributes'
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.9.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 6.12.0
Assignee: aabramov
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-13 11:02 UTC by mithun kalyat
Modified: 2024-12-20 21:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-16 13:32:59 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 33910 0 Normal New Hammer compute-profile create missing 'boot_order' from 'compute-attributes' 2021-11-11 12:55:28 UTC
Red Hat Issue Tracker SAT-12372 0 None None None 2022-08-22 15:40:11 UTC
Red Hat Product Errata RHSA-2022:8506 0 None None None 2022-11-16 13:33:13 UTC

Description mithun kalyat 2021-10-13 11:02:53 UTC 
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
Comment 1 Oleh Fedorenko 2021-11-11 12:55:27 UTC 
Created redmine issue https://projects.theforeman.org/issues/33910 from this bug
Comment 3 Bryan Kearney 2021-12-18 20:05:46 UTC 
Upstream bug assigned to aabramov
Comment 4 Bryan Kearney 2021-12-18 20:05:49 UTC 
Upstream bug assigned to aabramov
Comment 5 Bryan Kearney 2021-12-21 16:04:56 UTC 
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/33910 has been resolved.
Comment 7 Gaurav Talreja 2022-08-22 15:39:30 UTC 
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
Comment 11 errata-xmlrpc 2022-11-16 13:32:59 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.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
Note You need to log in before you can comment on or make changes to this bug.