Description: ------------------- GCE hammer always selects f1-micro image type regardless of requested image type, How Reproducible: ------------------- Always Steps: ------------------- 1. Provision a GCE host from a hammer with the image anything other than f1-micro type. # hammer host create --architecture-id 1 --build true --compute-attributes 'machine_type=n1-standard-2, network=default, associate_external_ip=true' --compute-resource-id 1 --domain-id 1 --image-id 1 --operatingsystem-id 1 --provision-method image --puppet-ca-proxy-id 1 --puppet-environment-id 1 --puppet-proxy-id 1 --root-password changeme --volume 'size_gb=13, size_gb=11' --location-id 2 --organization-id 1 --name gcePlus1 Actual Behavior: ------------------- 1. The GCE Host is provisioned but the image type in provisioned is f1-micro always. Expected Behavior: -------------------- 1. The GCE host should be provisioned with the requested image type in the hammer command.
Created from redmine issue https://projects.theforeman.org/issues/28130
Upstream bug assigned to None
Upstream bug assigned to kgaikwad
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28130 has been resolved.
Verified! @Satellite 6.7 snap 8 Steps: --------------- 1. Provision a GCE host from a hammer with the image anything other than f1-micro type. # hammer host create --architecture-id 1 --build true --compute-attributes 'machine_type=n1-standard-2, network=default, associate_external_ip=true' --compute-resource-id 1 --domain-id 1 --image-id 1 --operatingsystem-id 1 --provision-method image --puppet-ca-proxy-id 1 --puppet-environment-id 1 --puppet-proxy-id 1 --root-password changeme --volume 'size_gb=13, size_gb=11' --location-id 2 --organization-id 1 --name gcePlus1 Behavior: ------------------- The GCE Host is provisioned with the given machine type.
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, 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:1454