Bug 1745930

Summary: [UI] Only the First network is being saved for GCE Compute Profile and Host
Product: Red Hat Satellite Reporter: Jitendra Yejare <jyejare>
Component: Compute Resources - GCEAssignee: Kavita <kgaikwad>
Status: CLOSED DUPLICATE QA Contact: Jitendra Yejare <jyejare>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.6.0CC: kgaikwad, zhunting
Target Milestone: 6.6.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-09-12 18:05:17 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:
Bug Depends On:    
Bug Blocks: 1721890    

Description Jitendra Yejare 2019-08-27 09:20:39 UTC 
Description of problem:
The first network in networks list is being saved in GCE Compute Profile if I sele

Version-Release number of selected component (if applicable):
Satellite 6.6 snap 7

How reproducible:
Always

Steps to Reproduce:
1. Create GCE Compute Resource, load data from GCE and test connection successfully.
2. Start creating a new compute profile for GCE.
3. While editing compute profile, select any network in the networks list but not the first network in the list.
4. Save the Compute Profile.
4. Reopen the GCE compute profile and check the network selected is still the same.

Actual results:
1. The first network in the networks list is being saved regardless of what has chosen while saving the Compute Profile.

Expected results:
The chosen network in the networks list should be saved in the Compute Profile.

Additional info:
Comment 3 Jitendra Yejare 2019-08-27 09:38:50 UTC 
The same issue is also observed for GCE Host form, the 'Virtual Machine' tab shows the first network in the network list. But provisioning has done in the selected network only as selected and as expected.
Comment 4 Bryan Kearney 2019-09-01 22:01:58 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27360 has been resolved.
Comment 7 Kavita 2019-09-11 11:30:26 UTC 
Hello Zach,

Can I mark this BZ as duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1731857 as attached PR is same and it will fix both BZs?
Merge request is already created for BZ-1731857
Comment 8 Zach Huntington-Meath 2019-09-12 18:05:17 UTC 

*** This bug has been marked as a duplicate of bug 1731857 ***