From f3e18130e38e4c141df77f7b2e90d2b5f97c3f2b Mon Sep 17 00:00:00 2001 From: Le Zhang Date: Mon, 14 Oct 2024 08:59:31 -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 | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/agreementbot/consumer_protocol_handler.go b/agreementbot/consumer_protocol_handler.go index 00810430e..985b455dc 100644 --- a/agreementbot/consumer_protocol_handler.go +++ b/agreementbot/consumer_protocol_handler.go @@ -498,10 +498,9 @@ 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 } // new cluster namespace is still compatible - return true, true, false } }