Bug 1977358

Summary:	[4.8.0] KUBE-API: Support move agent to different cluster in the same namespace
Product:	Red Hat Advanced Cluster Management for Kubernetes	Reporter:	Michael Filanov <mfilanov>
Component:	Infrastructure Operator	Assignee:	Fred Rolland <frolland>
Status:	CLOSED CURRENTRELEASE	QA Contact:	bjacot
Severity:	medium	Docs Contact:	Christopher Dawson <cdawson>
Priority:	medium
Version:	rhacm-2.3	CC:	aos-bugs, ccrum, frolland, juhsu, trwest, yfirst
Target Milestone:	---	Keywords:	Triaged
Target Release:	rhacm-2.3.1	Flags:	ming: rhacm-2.3.z+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	AI-Team-Hive KNI-EDGE-4.8
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:	1977354	Environment:
Last Closed:	2021-10-13 21:08:28 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1977354
Bug Blocks:

Comment 12 ximhan 2021-08-20 07:26:57 UTC

OpenShift engineering has decided to NOT ship 4.8.6 on 8/23 due to the following issue.
https://bugzilla.redhat.com/show_bug.cgi?id=1995785
All the fixes part will be now included in 4.8.7 on 8/30.

Comment 16 Mike Ng 2021-09-03 13:52:31 UTC

G2Bsync 912085739 comment 
 CrystalChun Thu, 02 Sep 2021 21:54:56 UTC 
 G2Bsync Fix was merged as part of ACM 2.3 GA
Picked up in #14081

Comment 17 Yona First 2021-09-30 10:37:20 UTC

Hi @frolland, some questions about this bug:

1. What is the use case of this bug? Before\during\after installation?
2. In order to reproduce & verify the bug, should booting and rebooting the host be done manually, or done via ZTP and bmh? 

Thanks!

Comment 18 Fred Rolland 2021-09-30 12:38:30 UTC

1. Before installation
2. Should work with both methods

Comment 19 Yona First 2021-10-12 09:33:46 UTC

Verified with:
Hub Cluster OCP version: 4.8.0
RHACM version: 2.3.3-DOWNSTREAM-2021-09-30-13-28-42

Using both manual & ZTP methods to reboot the host with the new infraenv, output with old Infraenv:

oc get agent -o jsonpath='{.items[0].spec.clusterDeploymentName.name}{"\n"}'
spoke-0

With new Infraenv:

oc get agent -o jsonpath='{.items[0].spec.clusterDeploymentName.name}{"\n"}'
spoke-0-2

From Agent events log, with Infraenv1:

{"cluster_id":"06202dc3-1ce0-4661-a3f1-5ac682ccbe09","event_time":"2021-10-11T14:49:06.585Z","host_id":"67de17b9-ce08-45ce-98e2-a027c46f80b0","message":"Host 67de17b9-ce08-45ce-98e2-a027c46f80b0: registered to cluster","severity":"info"}

After changing to Infraenv2:

"cluster_id":"04af3f0a-6af0-4048-ba83-88ad08f6a220","event_time":"2021-10-11T15:00:10.060Z","host_id":"67de17b9-ce08-45ce-98e2-a027c46f80b0","message":"Host 67de17b9-ce08-45ce-98e2-a027c46f80b0: registered to cluster","severity":"info"}