|Summary:||[UI] Hide image field from compute profile form|
|Product:||Red Hat Satellite||Reporter:||Kavita <kgaikwad>|
|Component:||Compute Resources - GCE||Assignee:||Kavita <kgaikwad>|
|Status:||CLOSED ERRATA||QA Contact:||Jitendra Yejare <jyejare>|
|Fixed In Version:||foreman-220.127.116.11-1||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2020-04-14 13:28:54 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Kavita 2020-02-26 15:11:52 UTC
Description of problem: To make behaviour for image field consistent across all compute-resources, hiding image selection from compute-profile form Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Select compute-profile > GCE CR 2. On form, user can see image selection list 3. Actual results: Expected results: remove image selection from compute-profile form Additional info:
Comment 3 Bryan Kearney 2020-03-02 15:01:28 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/29183 has been resolved.
Comment 5 Jitendra Yejare 2020-03-09 14:06:34 UTC
I observed image fields in Libvirt and VMWare Compute Resources compute profile. @Kavita, Is this an expected behavior? Is this change only for GCE?
Comment 6 Jitendra Yejare 2020-03-11 08:04:08 UTC
Verified ! @ Satellite 6.7 snp 15 Steps: ------------ 1. Select compute-profile > GCE CR 2. On form, see if the image field is displayed Observation: ------------- The image field is no more available for GCE CR in Compute Profile which equals to the behavior from CLI. Note: ------ As per discussion with Assignee over email and her reply says: ``` This change is specific to GCE only. Eventually, it will get removed from all other remaining CRs as well. ``` So considering this change is only for GCE and assignees reply, moving this bug to Verified.
Comment 9 errata-xmlrpc 2020-04-14 13:28:54 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, 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