[#1448] container/ape: Ignore an error when getting a role

When getting a role in the APE checker for the container services,
an error may be returned if network maps of the previous two epochs
don't have enough nodes to fulfil a container placement policy.
It's a logical error, so we should ignore it.

Signed-off-by: Aleksey Savchuk <a.savchuk@yadro.com>

pkg/services/container/ape.go

@@ -550,10 +550,9 @@ func (ac *apeChecker) isContainerKey(pk []byte, cnrID cid.ID, cont *containercor
 }
 
 func isContainerNode(nm *netmapSDK.NetMap, pk, binCnrID []byte, cont *containercore.Container) bool {
-	// An error may be returned if network maps of the previous two epochs
-	// don't have enough nodes to fulfil a container placement policy.
-	// It's a logical error, so we should ignore it.
-	// See https://git.frostfs.info/TrueCloudLab/frostfs-node/issues/1448.
+	// It could an error only if the network map doesn't have enough nodes to
+	// fulfil the policy. It's a logical error that doesn't affect an actor role
+	// determining, so we ignore it
 	cnrVectors, _ := nm.ContainerNodes(cont.Value.PlacementPolicy(), binCnrID)
 
 	for i := range cnrVectors {