[EnMasse] 0.27.0-rc7 available

[Keith Wall]

I tested rc9, +1.

- deployed on openshift (3.11)
- created an address space
- created and delete address types
- delete an address space
- generally kicked the tyres in the console

I did notice an error in the enmasse-operator pod log, but this
appears to be not impactful.  The oauthclient does get created and the
error does not affect the operator's continued operation.

"Error creating oauth client,
ignoring","error":"oauthclients.oauth.openshift.io
\"enmasse-oauthclient-enmasse-infra\" already exists"".


On Tue, Mar 26, 2019 at 10:30 PM Ulf Lilleengen <lulf at redhat.com> wrote:
>
> Tagged another rc which fixes the issues I found: https://github.com/EnMasseProject/enmasse/releases/tag/0.27.0-rc9
>
> On Tue, Mar 26, 2019 at 9:19 PM Ulf Lilleengen <lulf at redhat.com> wrote:
>>
>> On Tue, Mar 26, 2019 at 5:49 PM Keith Wall <kwall at redhat.com> wrote:
>>>
>>> Hi all,
>>>
>>> EnMasse version 0.27.0 rc7 is available for testing[1]
>>> Here are the changes since 0.26.5.
>>>
>>> * Support for deploying via Operator Lifecycle Manager
>>> * Experimental support for integrated IoT service based on Eclipse Hono
>>> * Support for creating authentication services via CRDs
>>> * Support for affinity, tolerations and priority classes for messaging
>>> infrastructure
>>> * Support for exporting endpoint info to configmap, secret or service
>>> * Support for PATCH operation for AddressSpace, Address and
>>> MessagingUser resources
>>> * Upgrade to Apache ActiveMQ Artemis 2.6.4
>>> * Upgrade to Apache Qpid Dispatch Router 1.6.0
>>> * Upgrade to Keycloak 4.8.3
>>>
>>> More details can be found on the release page:
>>>
>>> [1] https://github.com/EnMasseProject/enmasse/releases/tag/0.27.0-rc7
>>>
>>> Best regards,
>>>
>>> Keith
>>>
>>
>> -1
>>
>> Found a couple of issues:
>>
>> * Router liveness probe is waiting for the router to be configured and may kill the router if it doesn't happen. Only the readiness probe should require configuration, while liveness should only require that it runs. Regression was introduced when changing to use http probes. Fixed in PR 2532
>> * With kubectl 1.13, the api-server openapi v2 schema is missing some definition of an array type and the client is unable to create address. Fixed in PR 2530
>> * With OCP4, a few typos in the operator CSV prevents EnMasse from being deployed. Fixed on master.
>>
>> Best regards,
>>
>> Ulf