Bug 1808015 - [MIG-UI] Secret not found error when adding a new source cluster
Summary: [MIG-UI] Secret not found error when adding a new source cluster
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Migration Tooling
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: 4.4.0
Assignee: Pranav Gaikwad
QA Contact: Sergio
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-27 16:20 UTC by Sergio
Modified: 2020-05-28 11:10 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-28 11:09:55 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2020:2326 0 None None None 2020-05-28 11:10:37 UTC

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


Note You need to log in before you can comment on or make changes to this bug.