Bug 2060230

Summary: [UI] Delete host modal has incorrect host's name populated
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Thuy Nguyen <thnguyen>
Component: Infrastructure OperatorAssignee: Marek Libra <mlibra>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact: Derek <dcadzow>
Priority: medium    
Version: rhacm-2.5CC: ccrum, dho, dhuynh, huichen, jtomasek, mlibra, ncarboni, smiron, tjelinek, trwest, yfirst
Target Milestone: ---Flags: bot-tracker-sync: rhacm-2.5+
Target Release: rhacm-2.5   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-06-09 02:09:02 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:
Attachments:
Description Flags
Delete host modal none

Description Thuy Nguyen 2022-03-03 02:36:14 UTC
Description of problem: [infraEnv] Delete host modal has incorrect host's name populated


Version-Release number of selected component (if applicable):
- ACM 2.5.0-DOWNSTREAM-2022-03-02-04-59-50
- MCE 2.0.0-DOWNANDBACK-2022-03-02-01-20-35

How reproducible:


Steps to Reproduce:
1. Install ACM + MCH + MCE
2. Create agentserviceconfig
3. Go to UI Infrastructure > Infrastructure environments, add host via BMC 
4. In UI, delete the host added in step 3 

Actual results:
Delete host modal has the BMC address populated as the host's name

Expected results:
The host's name/hostname should be stamped

Additional info:

Comment 1 Thuy Nguyen 2022-03-03 02:39:20 UTC
Created attachment 1863920 [details]
Delete host modal

Comment 2 Michael Filanov 2022-03-06 07:48:06 UTC
@thnguyen can you please attach BMH, infra-env and agent CRs? it will help to see from where this name comes from

Comment 4 Michael Filanov 2022-03-08 08:16:59 UTC
What about the status of the CRs? 
I would like to see the status of the agent, the hostname is there .

Comment 6 Michael Filanov 2022-03-09 08:38:55 UTC
Please get the agent as well (agent-install) it should be in the same namespace as the infra env

Comment 7 Thuy Nguyen 2022-03-21 21:25:19 UTC
As noted in https://bugzilla.redhat.com/show_bug.cgi?id=2060230#c5, the host is not bound to any cluster deployment, and there is no agent-install created.

Comment 8 Nick Carboni 2022-03-22 19:02:02 UTC
(In reply to Thuy Nguyen from comment #7)
> As noted in https://bugzilla.redhat.com/show_bug.cgi?id=2060230#c5, the host
> is not bound to any cluster deployment, and there is no agent-install
> created.

There should be an agent object when the host registers with the service.
Based on the BMH status it looks like there was a provisioning error.

Based on the screenshot it looks like some UI is displaying the BMH provisioning address rather than something more friendly.
In the case that an agent never registers with assisted-service, what do we expect there?

Comment 9 Nick Carboni 2022-03-22 19:04:04 UTC
Also, if the host registers successfully is the modal still displaying the provisioning address or is it getting a better value from some other object?

Comment 10 Michael Filanov 2022-03-23 09:17:30 UTC
@jtomasek @tjelinek FYI

Comment 11 Tomas Jelinek 2022-03-24 09:51:12 UTC
yep, UI should be showing the metadata.name, moving to UI

Comment 12 Shelly Miron 2022-03-31 15:35:05 UTC
verified with (image attached to the bug):

$ oc version

Client Version: 4.10.6
Server Version: 4.10.6
Kubernetes Version: v1.23.5+b0357ed

$ oc get catalogsources.operators.coreos.com -n openshift-marketplace acm-custom-snapshot

NAME                  DISPLAY                                TYPE   PUBLISHER   AGE
acm-custom-snapshot   2.5.0-DOWNSTREAM-2022-03-29-05-04-50   grpc   Red Hat     18h

Comment 18 errata-xmlrpc 2022-06-09 02:09:02 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 (Important: Red Hat Advanced Cluster Management 2.5 security updates, images, and bug fixes), 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/RHSA-2022:4956