[EnMasse] 0.13.0 release candidate
Lohmann Carsten (INST/ECS4)
Carsten.Lohmann at bosch-si.com
Fri Sep 22 15:47:52 UTC 2017
below message was supposed to go to the "Errors in address-controller (0.13.0-rc3 on kubernetes)" thread.
Mails arriving in strange order here :)
-----Ursprüngliche Nachricht-----
Von: enmasse-bounces at redhat.com [mailto:enmasse-bounces at redhat.com] Im Auftrag von Lohmann Carsten (INST/ECS4)
Gesendet: Freitag, 22. September 2017 15:56
An: Ulf Lilleengen <ulilleen at redhat.com>; enmasse at redhat.com
Betreff: Re: [EnMasse] 0.13.0 release candidate
Hi Ulf,
we have repeated the test with rc4. Deployment has been done with the "standard" (ie keycloak) auth service:
deploy-kubernetes.sh -a standard -m https://192.168.99.100:8443 -n enmasse
The exception mentioned below is still there:
--------
2017-09-22 13:34:16 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)
-------------
Upon address registration (one multicast address "telemetry/DEFAULT_TENANT" and one topic address "event/DEFAULT_TENANT"), there is this exception in the address-controller log:
---------
2017-09-22 13:40:11 INFO AddressController:87 - Check address in address space controller: [{address=event/DEFAULT_TENANT,name=event/DEFAULT_TENANT,uuid=96ea5893-7503-362d-ac96-048dbe8e183d,type=TOPIC,plan={name=inmemory,uuid=824e119c-615a-11e7-a25e-507b9def37d9},status=false}, {address=telemetry/DEFAULT_TENANT,name=telemetry/DEFAULT_TENANT,uuid=1faaf778-ab53-308e-85e2-034f310f9197,type=MULTICAST,plan={name=standard,uuid=e840275c-6163-11e7-9fe6-507b9def37d9},status=false}]
2017-09-22 13:40:11 INFO AddressController:108 - Current set of clusters: []
2017-09-22 13:40:11 WARN ResourceController:75 - Exception doing resource update
java.lang.IllegalArgumentException: No value available for parameter name: COLOCATED_ROUTER_SECRET
at io.fabric8.openshift.client.dsl.internal.TemplateOperationsImpl.processLocally(TemplateOperationsImpl.java:203)
at io.fabric8.openshift.client.dsl.internal.TemplateOperationsImpl.processLocally(TemplateOperationsImpl.java:157)
at io.fabric8.openshift.client.dsl.internal.TemplateOperationsImpl.processLocally(TemplateOperationsImpl.java:59)
at io.enmasse.controller.common.KubernetesHelper.processTemplate(KubernetesHelper.java:146)
at io.enmasse.controller.common.TemplateAddressClusterGenerator.processTemplate(TemplateAddressClusterGenerator.java:104)
at io.enmasse.controller.common.TemplateAddressClusterGenerator.lambda$generateCluster$0(TemplateAddressClusterGenerator.java:64)
at java.util.Optional.map(Optional.java:215)
at io.enmasse.controller.common.TemplateAddressClusterGenerator.generateCluster(TemplateAddressClusterGenerator.java:64)
at io.enmasse.controller.standard.AddressController.lambda$createBrokers$5(AddressController.java:140)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at java.util.Iterator.forEachRemaining(Iterator.java:116)
at java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1801)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at io.enmasse.controller.standard.AddressController.createBrokers(AddressController.java:141)
at io.enmasse.controller.standard.AddressController.resourcesUpdated(AddressController.java:110)
at io.enmasse.k8s.api.ResourceController.run(ResourceController.java:72)
at java.lang.Thread.run(Thread.java:748)
---------
Both addresses are not ready afterwards (message: " Address telemetry/DEFAULT_TENANT not found on qdrouterd-192504702-892d5").
Best regards
Carsten Lohmann
(INST/ECS4)
Bosch Software Innovations GmbH | Ullsteinstr. 128 | 12109 Berlin | GERMANY | www.bosch-si.com Tel. +49 30 726112-130 | Fax +49 30 726112-100 | 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
-----Ursprüngliche Nachricht-----
Von: enmasse-bounces at redhat.com [mailto:enmasse-bounces at redhat.com] Im Auftrag von Ulf Lilleengen
Gesendet: Freitag, 22. September 2017 13:25
An: enmasse at redhat.com
Betreff: [EnMasse] 0.13.0 release candidate
Hi all,
I've tagged a release candidate for 0.13.0 which is available here:
https://github.com/EnMasseProject/enmasse/releases/download/0.13.0-rc4/enmasse-0.13.0-rc4.tgz
Please give it a test if you can. I'll be doing some final verification on features that are not covered by automatic tests. If things look good, I will create the final release from this tag.
--
Ulf
_______________________________________________
enmasse mailing list
enmasse at redhat.com
https://www.redhat.com/mailman/listinfo/enmasse
_______________________________________________
enmasse mailing list
enmasse at redhat.com
https://www.redhat.com/mailman/listinfo/enmasse
More information about the enmasse
mailing list