Bug 1789815
| Summary: | The "start" parameter should be mentioned inside "--compute-attributes:" in hammer_cli for Satellite 6 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Sayan Das <saydas> |
| Component: | Hosts | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED ERRATA | QA Contact: | tstrych |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.6.0 | CC: | ajambhul, apatel, egolov, inecas, kgaikwad, mshira, ofedoren, rabajaj |
| Target Milestone: | 6.8.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-hammer_cli_foreman-0.18.0 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 12:59:59 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
This one was fixed as a part of attached upstream issues. Marking as POST since the upsream issues are resolved. Verified with sat 6.8 snap 2.1, tfm-rubygem-hammer_cli_foreman-2.1.0-2
Need-info why there is Fixed In Version: tfm-rubygem-hammer_cli_foreman-0.18.0 if sat 6.8 snap 2 has at least tfm-rubygem-hammer_cli_foreman-2.x ?
Need info doesn't change that this bz is solved.
hammer host create --help
---------------------omitted ---------------------
Libvirt:
--volume:
pool_name One of available storage pools
capacity String value, e.g. 10G
allocation
Initial allocation, e.g. 0G
format_type Possible values: raw, qcow2
--interface:
compute_type Possible values: bridge, network
compute_bridge Name of interface according to type
compute_model Possible values: virtio, rtl8139, ne2k_pci, pcnet, e1000
compute_network
Libvirt instance network, e.g. default
--compute-attributes:
cpus Number of CPUs
memory String, amount of memory, value in bytes
cpu_mode Possible values: default, host-model, host-passthrough
start Boolean (expressed as 0 or 1), whether to start the machine or not
---------------------omitted ---------------------
oVirt:
--volume:
size_gb Volume size in GB, integer value
storage_domain ID or name of storage domain
bootable Boolean, set 1 for bootable, only one volume can be bootable
preallocate Boolean, set 1 to preallocate
wipe_after_delete Boolean, set 1 to wipe disk after delete
interface Disk interface name, must be ide, virto or virto_scsi
--interface:
compute_name Compute name, e.g. eth0
compute_network Select one of available networks for a cluster, must be an ID or a name
compute_interface Interface type
--compute-attributes:
cluster ID or name of cluster to use
template Hardware profile to use
cores Integer value, number of cores
sockets Integer value, number of sockets
memory Amount of memory, integer value in bytes
display_type Possible values: VNC, SPICE
keyboard_layout Possible values: ar, de-ch, es, fo, fr-ca, hu, ja, mk, no, pt-br, sv, da, en-gb, et, fr, fr-ch, is, lt, nl, pl, ru, th, de, en-us, fi, fr-be, hr, it, lv, nl-be, pt, sl, tr. Not usable if display type is SPICE.
start Boolean, set 1 to start the vm
---------------------omitted ---------------------
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)
start Must be a 1 or 0, whether to start the machine or not
---------------------omitted ---------------------
It's "fixed in" tfm-rubygem-hammer_cli_foreman-0.18.0 because it's fixed in that version, snap 2 has a newer one, so we also have the fix :) 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.8 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-2020:4366 |
Description of problem: If we do "hammer host create --help", we will be able to see that the "start" parameter is mentioned inside "--interface" section. But since we require to pass the argument with "--compute-attributes:", so technically It should be moved under "--compute-attributes:" section to avoid any confusion while forming the "hammer host create" command. Version-Release number of selected component (if applicable): Satellite 6.6 How reproducible: Always Steps to Reproduce: 1. On Satellite 6.6, execute "hammer host create --help" command and observe. Actual results: # hammer host create --help | tail -25 --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 from VMware start Must be a 1 or 0, whether to start the machine or not --compute-attributes: cpus CPU count corespersocket Number of cores per socket (applicable to hardware versions < 10 only) memory_mb Integer number, amount of memory in MB firmware automatic/bios/efi cluster Cluster ID from VMware resource_pool Resource Pool ID from VMware path Path to folder guest_id Guest OS ID form VMware scsi_controller_type ID of the controller from VMware hardware_version Hardware version ID from VMware add_cdrom Must be a 1 or 0, Add a CD-ROM drive to the virtual machine cpuHotAddEnabled Must be a 1 or 0, lets you add memory resources while the machine is on memoryHotAddEnabled Must be a 1 or 0, lets you add CPU resources while the machine is on annotation Annotation Notes Expected results: # hammer host create --help | tail -25 --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 from VMware --compute-attributes: cpus CPU count corespersocket Number of cores per socket (applicable to hardware versions < 10 only) memory_mb Integer number, amount of memory in MB firmware automatic/bios/efi cluster Cluster ID from VMware resource_pool Resource Pool ID from VMware path Path to folder guest_id Guest OS ID form VMware scsi_controller_type ID of the controller from VMware hardware_version Hardware version ID from VMware add_cdrom Must be a 1 or 0, Add a CD-ROM drive to the virtual machine cpuHotAddEnabled Must be a 1 or 0, lets you add memory resources while the machine is on memoryHotAddEnabled Must be a 1 or 0, lets you add CPU resources while the machine is on annotation Annotation Notes start Must be a 1 or 0, whether to start the machine or not Additional info: NA