Bug 1882417 - [OCP 4.6 BM IPI / ACM 2.1.0] - Bare metal assets displaying "Asset sync failed" when allocated to spoke cluster
Summary: [OCP 4.6 BM IPI / ACM 2.1.0] - Bare metal assets displaying "Asset sync faile...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Cluster Lifecycle
Version: rhacm-2.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: rhacm-2.1
Assignee: Hao Liu
QA Contact: magchen@redthat.com
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-24 14:00 UTC by Chad Crum
Modified: 2021-04-09 16:40 UTC (History)
3 users (show)

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


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github open-cluster-management backlog issues 5664 0 None None None 2020-10-08 15:44:45 UTC
Red Hat Product Errata RHEA-2020:4954 0 None None None 2020-11-05 11:55:25 UTC

Description Chad Crum 2020-09-24 14:00:03 UTC
Description of problem:
Bare metal assets displaying "Asset sync failed" when allocated (Although spoke create is successful)

Version-Release number of selected component (if applicable):
- OCP 4.6 - registry.svc.ci.openshift.org/ocp/release:4.6.0-0.nightly-2020-09-20-184226 (Both hub + spoke)
- ACM 2.1.0 - 2.1.0-DOWNSTREAM-2020-09-21-02-55-22
- IPv4 Provision + Baremetal networks

How reproducible:
100%

Steps to Reproduce:
1. Deploy OCP 4.6 and ACM 2.1.0 BM 
2. Create bare metal assets
3. Create spoke cluster and include bare metal assets (Via UI)

Actual results:
Bare metal asset page shows "Asset sync failed" next to each asset, although create is successful

Expected results:
The correct message to display

Additional info:

Comment 1 Chad Crum 2020-09-24 14:13:14 UTC
@haoli - This is what we were discussing yesterday. I duplicated it again today as well.

Comment 2 Chad Crum 2020-10-26 13:20:52 UTC
As stated in the GH issue, I retested and the issue is fixed in 2.1.0-DOWNSTREAM-2020-10-22-14-50-3.

Comment 5 errata-xmlrpc 2020-11-05 11:55:19 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 (Red Hat Advanced Cluster Management for Kubernetes version 2.1 images), 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:4954


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