Bug 2052910 - application creation failed
Summary: application creation failed
Keywords:
Status: CLOSED DUPLICATE of bug 2042210
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Search / Analytics
Version: rhacm-2.4
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: rhacm-2.4.4
Assignee: Jorge Padilla
QA Contact: Atif
Mikela Dockery
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-10 09:31 UTC by Gellert Kis
Modified: 2025-04-04 14:16 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-27 15:27:22 UTC
Target Upstream Version:
Embargoed:
ashafi: qe_test_coverage-
bot-tracker-sync: rhacm-2.4.z+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github stolostron backlog issues 19838 0 None None None 2022-02-10 11:51:07 UTC

Comment 2 bot-tracker-sync 2022-02-10 16:59:23 UTC 
G2Bsync 1035041248 comment 
 fxiang1 Thu, 10 Feb 2022 15:17:09 UTC 
 G2Bsync

Looks like this is an issue with the search component. Before we send it over to the search team can the user confirm it's a search issue by going to the search UI and try searching for the application they created? ie. with the search attributes `kind:application` `name:<APP_NAME>` replace `<APP_NAME>` with the name of their application.
Comment 3 Jorge Padilla 2022-02-24 20:54:33 UTC 
Seems like the root cause is BZ 2042210.  There are various workarounds documented within BZ 2042210 and summarized here https://access.redhat.com/solutions/6671301
Comment 5 Jorge Padilla 2022-04-27 15:27:22 UTC 
@ecai There was no code changes for this bug.

Closing as duplicate of BZ2042210. There are several workarounds documented in BZ2042210. We are working on a permanent solution in a future release.

*** This bug has been marked as a duplicate of bug 2042210 ***
Comment 6 Red Hat Bugzilla 2023-09-18 04:31:49 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.