Bug 1687086

Summary: cloudforms registration process with satellite (+1 org) must require the selection of the sat6 org before allowing to save
Product: Red Hat CloudForms Management Engine Reporter: Reartes Guillermo <greartes>
Component: UI - OPSAssignee: Dávid Halász <dhalasz>
Status: CLOSED ERRATA QA Contact: Tasos Papaioannou <tpapaioa>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: 5.10.0CC: bmidwood, dmetzger, hkataria, lavenel, mpovolny, mshriver, obarenbo, simaishi, tpapaioa
Target Milestone: GA   
Target Release: 5.11.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 5.11.0.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-12 13:36:02 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:

Description Reartes Guillermo 2019-03-09 16:51:53 UTC 
Description of problem:

There is an issue with the registration process to Red Hat Satellite when there are more than 1 organizations in the Satellite.
One MUST select an organization, but it is possible to save without having selected one (!)

No appliance should be built with pre-enabled non redhat repositories.

Version-Release number of selected component (if applicable):
CFME: 5.10.0.33-1 (i think this is present in CF versions)
CF: 4.7
SAT: 6.4.x

How reproducible:
always

Steps to Reproduce:
1. deploy new CF 4.7 appliance
2. start the registration process -> select satellite
3. fill all the user/pw data and check validate
4. FAIL to notice that a new field appears (the field request an organization)
4. click save
5. even if the validation succeeds, the registration process will fail (CF will show red notification)

Actual results:
it is possible to validate the sat6 credentials, miss a required field and fail to register the appliances

Expected results:
the field to select the organization MUST be Required.
change the process in a way that the user is unable to save unless they selected the organization.

Additional info:
N/A
Comment 11 CFME Bot 2019-05-07 08:22:45 UTC 
https://github.com/ManageIQ/manageiq-ui-classic/pull/5540
Comment 12 CFME Bot 2019-05-09 20:41:43 UTC 
New commit detected on ManageIQ/manageiq-ui-classic/master:

https://github.com/ManageIQ/manageiq-ui-classic/commit/757a835197b671fdf1ea517e1201d1eb0b02981d
commit 757a835197b671fdf1ea517e1201d1eb0b02981d
Author:     Dávid Halász <dhalasz>
AuthorDate: Tue May  7 04:06:35 2019 -0400
Commit:     Dávid Halász <dhalasz>
CommitDate: Tue May  7 04:06:35 2019 -0400

    Make Organization required on RHN updates upon 1+ available orgs

    Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1687086

 app/controllers/ops_controller/settings/rhn.rb | 2 +
 spec/controllers/ops_controller/settings/common_spec.rb | 20 +-
 2 files changed, 19 insertions(+), 3 deletions(-)
Comment 13 Tasos Papaioannou 2019-05-15 19:39:35 UTC 
Verified on 5.11.0.4.
Comment 15 errata-xmlrpc 2019-12-12 13:36:02 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/RHBA-2019:4199