Description of problem:
Hammer, UI and probably API also showing every machine_type but multiple times to provision the GCE Host.
Version-Release number of selected component (if applicable):
Satellite 6.7 snap 9
Steps to Reproduce:
1. Create a GCE Compute Resource.
2. From UI:
1. While host provisioning, attempt to search any machine_type while choosing machine type.
3. From API/CLI:
1. List the machine types/flavors in Compute Resource.
Every machine_type is displayed/fetched multiple times to provision the GCE Host.
Every machine_type/flavor should be fetched once.
Same also applies with the count of Available images in GCE CR. The count of available images in GCE CR under satellite is different(more) than whats available in Google Compute Engine under images section.
Created redmine issue https://projects.theforeman.org/issues/28898 from this bug
Upstream bug assigned to email@example.com
From comment 3, could you please raise a separate issue for images?
Because showing duplicate records for machine_types/flavors is different than having different images list than google compute engine.
I will add my observations related to images accordingly.
Raised new bug - https://bugzilla.redhat.com/show_bug.cgi?id=1801622
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/28898 has been resolved.
Created attachment 1666150 [details]
[Verified Screenshot] Unique flavors and not repeated
@Satellite 6.7 snap 13
1. Fetch GCE machite_type/flavors from UI/CLI/API.
1. Every machine_type/flavor is being fetched once and unique.
# hammer compute-resource flavors --id 1 | grep n1-highmem
5016 | n1-highmem-16
5002 | n1-highmem-2
5032 | n1-highmem-32
5004 | n1-highmem-4
5064 | n1-highmem-64
5008 | n1-highmem-8
5096 | n1-highmem-9
Screenshot Attached of STDOUT and grep.
Created attachment 1666151 [details]
[Verified Screenshot] UI Unique flavors and not repeated
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.