Bug 1790863 - Should not create secret if idp is not created successfully
Summary: Should not create secret if idp is not created successfully
Keywords:
Status: CLOSED DUPLICATE of bug 1790757
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.3.z
Assignee: Jakub Hadvig
QA Contact: Yadan Pei
URL:
Whiteboard:
Depends On: 1790757
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-01-14 12:16 UTC by Jakub Hadvig
Modified: 2020-01-23 12:07 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1790757
Environment:
Last Closed: 2020-01-23 12:07:25 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jakub Hadvig 2020-01-14 12:16:32 UTC 
+++ This bug was initially created as a clone of Bug #1790757 +++

Description of problem:
When do negative test for idp, the idp is not created successfully but secret is already created.

Version-Release number of selected component (if applicable):
4.3.0-0.nightly-2020-01-11-070223

How reproducible:
Always

Steps to Reproduce:
1.Create gitlab idp from console, set name, client id, client secret, and input "testurl" in field "URL", click "Add".
2.Check secret in openshift-config project.
3.

Actual results:
1. It will prompt error: "must contain a scheme (e.g. https://)" for field "spec.identityProviders[1].gitlab.url"."
2. New secret prefix with "gitlab-client-secret" is listed in openshift-config project.

Expected results:
2. Should not create secret if idp is not created successfully.


Additional info:
Comment 1 Jakub Hadvig 2020-01-23 12:07:25 UTC 

*** This bug has been marked as a duplicate of bug 1790757 ***
Note You need to log in before you can comment on or make changes to this bug.