[EnMasse] Errors in address-controller (0.13.0-rc3 on kubernetes)

[Lohmann Carsten (INST/ECS4)]

Hi,

we have deployed the 0.13.0-rc3 version in a minikube environment (using the "deploy-kubernetes.sh" script, params
" -k pw -n enmasse -m https://192.168.99.100:8443").
In the address-controller log, there are frequent exceptions like this:
--------
2017-09-22 08:36:35 INFO  AddressController:242 - Error requesting router status. Ignoring
java.util.concurrent.ExecutionException: java.lang.SecurityException: Could not find a suitable SASL mechanism for the remote peer using the available credentials.
            at java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
            at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1915)
            at io.enmasse.amqp.SyncRequestClient.request(SyncRequestClient.java:94)
            at io.enmasse.controller.standard.AddressController.checkRouter(AddressController.java:236)
            at io.enmasse.controller.standard.AddressController.checkRouterStatus(AddressController.java:196)
            at io.enmasse.controller.standard.AddressController.checkStatuses(AddressController.java:177)
            at io.enmasse.controller.standard.AddressController.resourcesUpdated(AddressController.java:113)
            at io.enmasse.k8s.api.ResourceController.run(ResourceController.java:72)
            at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.SecurityException: Could not find a suitable SASL mechanism for the remote peer using the available credentials.
            at io.vertx.proton.impl.ProtonSaslClientAuthenticatorImpl.handleSaslInit(ProtonSaslClientAuthenticatorImpl.java:140)
            at io.vertx.proton.impl.ProtonSaslClientAuthenticatorImpl.process(ProtonSaslClientAuthenticatorImpl.java:89)
            at io.vertx.proton.impl.ProtonTransport.processSaslAuthentication(ProtonTransport.java:201)
            at io.vertx.proton.impl.ProtonTransport.handleSocketBuffer(ProtonTransport.java:184)
            at io.vertx.core.net.impl.NetSocketImpl.handleDataReceived(NetSocketImpl.java:321)
            at io.vertx.core.net.impl.NetClientImpl$1.handleMsgReceived(NetClientImpl.java:197)
            at io.vertx.core.net.impl.VertxNetHandler.lambda$channelRead$0(VertxNetHandler.java:64)
            at io.vertx.core.impl.ContextImpl.lambda$wrapTask$2(ContextImpl.java:335)
            at io.vertx.core.impl.ContextImpl.executeFromIO(ContextImpl.java:193)
            at io.vertx.core.net.impl.VertxNetHandler.channelRead(VertxNetHandler.java:64)
            at io.vertx.core.net.impl.VertxHandler.channelRead(VertxHandler.java:122)
            at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:363)
--------
A subsequent address registration attempt does not result in addresses getting ready:
Message in JSON output:
Address x is missing linkRoutes on qdrouterd-760403140-kznkm
Address y not found on qdrouterd-760403140-kznkm


Is it a bug or is there some configuration missing here?

TIA

Best regards

Carsten Lohmann

(INST/ECS4)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY | www.bosch-si.com<http://www.bosch-si.com>
Tel. +49 30 726112-130 | Fax +49 30 726112-100 | carsten.lohmann at bosch-si.com<mailto:carsten.lohmann at bosch-si.com>

Sitz: Berlin, Registergericht: Amtsgericht Charlottenburg; HRB 148411 B
Aufsichtsratsvorsitzender: Dr.-Ing. Thorsten Lücke; Geschäftsführung: Dr.-Ing. Rainer Kallenbach, Michael Hahn



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20170922/745b6222/attachment.htm>