From 49422c6a9d6ab30b2e864a88fe0a0c0c134310c6 Mon Sep 17 00:00:00 2001 From: Le Zhang Date: Fri, 11 Oct 2024 10:35:49 -0400 Subject: [PATCH] Issue open-horizon#4156 (part2) - Bug: On restart, agbot doesn't update a node even though a new service was added and a deployment policy update occurred Signed-off-by: Le Zhang --- agreementbot/consumer_protocol_handler.go | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/agreementbot/consumer_protocol_handler.go b/agreementbot/consumer_protocol_handler.go index 00810430e..a6e8ba469 100644 --- a/agreementbot/consumer_protocol_handler.go +++ b/agreementbot/consumer_protocol_handler.go @@ -498,10 +498,12 @@ func (b *BaseConsumerProtocolHandler) HandlePolicyChangeForAgreement(ag persiste t_comp, consumerNamespace, t_reason := compcheck.CheckClusterNamespaceCompatibility(dev.NodeType, dev.ClusterNamespace, dev.IsNamespaceScoped, busPol.ClusterNamespace, wl.ClusterDeployment, ag.Pattern, false, msgPrinter) if !t_comp { glog.V(5).Infof(BCPHlogstring(b.Name(), fmt.Sprintf("cluster namespace %v is not longer compatible for agreement %v. Reason is: %v", consumerNamespace, ag.CurrentAgreementId, t_reason))) - + return true, true, false + } else if consumerNamespace != oldPolicy.ClusterNamespace { + glog.V(5).Infof(BCPHlogstring(b.Name(), fmt.Sprintf("cluster namespace has changed from %v to %v for agreement %v", oldPolicy.ClusterNamespace, consumerNamespace, ag.CurrentAgreementId))) + return true, true, false } - // new cluster namespace is still compatible - return true, true, false + // new cluster namespace is still compatible, namespace still same } }