[
https://issues.apache.org/jira/browse/KAFKA-6672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403118#comment-16403118
]
ASF GitHub Bot commented on KAFKA-6672:
---------------------------------------
hachikuji opened a new pull request #4727: KAFKA-6672; ConfigCommand should
create config change parent path if needed
URL: https://github.com/apache/kafka/pull/4727
Change `KafkaZkClient.createConfigChangeNotification` to ensure creation of
the change directory. This fixes failing system tests which depend on setting
SCRAM credentials prior to broker startup. Existing test case has been modified
for new expected usage.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> ConfigCommand failing to alter configs
> --------------------------------------
>
> Key: KAFKA-6672
> URL: https://issues.apache.org/jira/browse/KAFKA-6672
> Project: Kafka
> Issue Type: Bug
> Reporter: Jason Gustafson
> Assignee: Jason Gustafson
> Priority: Major
>
> Seen a few system test failures with the following error:
> {code:java}
> RemoteCommandError: ubuntu@worker7: Command
> '/opt/kafka-dev/bin/kafka-configs.sh --zookeeper worker6:2181 --entity-name
> kafka-broker --entity-type users --alter --add-config
> SCRAM-SHA-256=[password=broker-secret]' returned non-zero exit status 1.
> Remote error message:
> Error while executing config command with args [Ljava.lang.String;@52363f8d
> org.apache.zookeeper.KeeperException$NoNodeException: KeeperErrorCode =
> NoNode for /config/changes/config_change_
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:111)
> at org.apache.zookeeper.KeeperException.create(KeeperException.java:51)
> at kafka.zookeeper.AsyncResponse.maybeThrow(ZooKeeperClient.scala:472)
> at
> kafka.zk.KafkaZkClient.createConfigChangeNotification(KafkaZkClient.scala:292)
> at
> kafka.zk.AdminZkClient.kafka$zk$AdminZkClient$$changeEntityConfig(AdminZkClient.scala:393)
> at
> kafka.zk.AdminZkClient.changeUserOrUserClientIdConfig(AdminZkClient.scala:323)
> at kafka.zk.AdminZkClient.changeConfigs(AdminZkClient.scala:287)
> at kafka.admin.ConfigCommand$.alterConfig(ConfigCommand.scala:133)
> at kafka.admin.ConfigCommand$.processCommandWithZk(ConfigCommand.scala:100)
> at kafka.admin.ConfigCommand$.main(ConfigCommand.scala:77)
> at kafka.admin.ConfigCommand.main(ConfigCommand.scala){code}
> This may have been failing for a while and was only exposed after KAFKA-6656.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
