You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
INFO Successfully logged in. (org.apache.kafka.common.security.authenticator.AbstractLogin)
INFO Kafka version: 2.8.1 (org.apache.kafka.common.utils.AppInfoParser)
INFO Kafka commitId: 839b886f9b732b15 (org.apache.kafka.common.utils.AppInfoParser)
INFO Kafka startTimeMs: 1690488835909 (org.apache.kafka.common.utils.AppInfoParser)
INFO Single run mode: ACL will be synchornized once. (io.conduktor.ksm.KafkaSecurityManager$)
ERROR unexpected exception (io.conduktor.ksm.KafkaSecurityManager$)
java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidRequestException: The only valid name for the CLUSTER resource is kafka-cluster
at org.apache.kafka.common.internals.KafkaFutureImpl.wrapAndThrow(KafkaFutureImpl.java:45)
at org.apache.kafka.common.internals.KafkaFutureImpl.access$000(KafkaFutureImpl.java:32)
at org.apache.kafka.common.internals.KafkaFutureImpl$SingleWaiter.await(KafkaFutureImpl.java:89)
at org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:260)
at io.conduktor.ksm.compat.AdminClientAuthorizerBase.addAcls(AdminClientAuthorizer.scala:44)
at io.conduktor.ksm.compat.AdminClientAuthorizerBase.addAcls$(AdminClientAuthorizer.scala:41)
at io.conduktor.ksm.compat.AdminClientAuthorizer.addAcls(AdminClientAuthorizer.scala:90)
at io.conduktor.ksm.AclSynchronizer$.$anonfun$applySourceAcls$1(AclSynchronizer.scala:48)
at io.conduktor.ksm.AclSynchronizer$.$anonfun$applySourceAcls$1$adapted(AclSynchronizer.scala:47)
at scala.collection.MapLike$MappedValues.$anonfun$foreach$3(MapLike.scala:257)
at scala.collection.TraversableLike$WithFilter.$anonfun$foreach$1(TraversableLike.scala:985)
at scala.collection.immutable.Map$Map2.foreach(Map.scala:273)
at scala.collection.TraversableLike$WithFilter.foreach(TraversableLike.scala:984)
at scala.collection.MapLike$MappedValues.foreach(MapLike.scala:257)
at io.conduktor.ksm.AclSynchronizer$.applySourceAcls(AclSynchronizer.scala:47)
at io.conduktor.ksm.AclSynchronizer.run(AclSynchronizer.scala:111)
at io.conduktor.ksm.KafkaSecurityManager$.delayedEndpoint$io$conduktor$ksm$KafkaSecurityManager$1(KafkaSecurityManager.scala:52)
at io.conduktor.ksm.KafkaSecurityManager$delayedInit$body.apply(KafkaSecurityManager.scala:10)
at scala.Function0.apply$mcV$sp(Function0.scala:39)
at scala.Function0.apply$mcV$sp$(Function0.scala:39)
at scala.runtime.AbstractFunction0.apply$mcV$sp(AbstractFunction0.scala:17)
at scala.App.$anonfun$main$1$adapted(App.scala:80)
at scala.collection.immutable.List.foreach(List.scala:431)
at scala.App.main(App.scala:80)
at scala.App.main$(App.scala:78)
at io.conduktor.ksm.KafkaSecurityManager$.main(KafkaSecurityManager.scala:10)
at io.conduktor.ksm.KafkaSecurityManager.main(KafkaSecurityManager.scala)
Caused by: org.apache.kafka.common.errors.InvalidRequestException: The only valid name for the CLUSTER resource is kafka-cluster
Our ACL file as related to Cluster has nothing special. I even tried deleeting the entire Cluster section but it still fails.
Is there some invalid Cluster rule that it is pulling from MSK? Is there something special that AWS MSK is adding that is causing this to barf? I tried using kafka-acls --list and I only get valid Cluster level ACLs
Someuser:
groups:
"*":
- All
topics:
"*":
- All
- DescribeConfigs
- AlterConfigs
clusters:
kafka-cluster:
- Alter
- AlterConfigs
- ClusterAction
- Create
- Describe
- DescribeConfigs
Because of this mid-sync barfing, the sync does not complete and we are getting a partial sync. Some ACLs are not applied and many are not removed from the cluster.
The text was updated successfully, but these errors were encountered:
Getting the following error when syncing
Our ACL file as related to Cluster has nothing special. I even tried deleeting the entire Cluster section but it still fails.
Is there some invalid Cluster rule that it is pulling from MSK? Is there something special that AWS MSK is adding that is causing this to barf? I tried using
kafka-acls --list
and I only get valid Cluster level ACLsBecause of this mid-sync barfing, the sync does not complete and we are getting a partial sync. Some ACLs are not applied and many are not removed from the cluster.
The text was updated successfully, but these errors were encountered: