Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1808015

Summary:	[MIG-UI] Secret not found error when adding a new source cluster
Product:	OpenShift Container Platform	Reporter:	Sergio <sregidor>
Component:	Migration Tooling	Assignee:	Pranav Gaikwad <pgaikwad>
Status:	CLOSED ERRATA	QA Contact:	Sergio <sregidor>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.3.0	CC:	chezhang, dymurray, pgaikwad, rpattath, whu, xjiang
Target Milestone:	---
Target Release:	4.4.0
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:	2020-05-28 11:09:55 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:

Description Sergio 2020-02-27 16:20:17 UTC

Description of problem:
When we add a new cluster, sometimes, we get an error saying that the secret does not exist.

Version-Release number of selected component (if applicable):
CAM 1.1.1

How reproducible:
Intermittent

Steps to Reproduce:
1. Click on "Add" in the cluster row in the UI
2. Fill in the source cluster information
3. Click on "Add cluster"

Actual results:
Sometimes, not very often, the form displays an error saying that the secret does not exist. When we click "Close", it happens that the cluster was correctly added and everything is working fine, even if the error said otherwise.

Expected results:
The cluster should not show any error, since it was added correctly.


Additional info:

Comment 6 Xin jiang 2020-05-07 10:34:20 UTC

verified.

Controller image:
 image: quay-enterprise-quay-enterprise.apps.qe-appmig-tgt-3190.qe.azure.devcluster.openshift.com/admin/openshift-migration-controller-rhel8@sha256:383991bd3e7eda398958980a00abb9c2fda5602e864f978e1eab2312bc248689
    imagePullPolicy: Always

Comment 8 errata-xmlrpc 2020-05-28 11:09:55 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/RHEA-2020:2326