[EnMasse] the server doesn't have a resource type "address"

[Ulf Lilleengen]

Hi Bob,

Could you could share the existing YAML setup you use for 0.26.x ? Also the
address types you use would be useful. We have run tests for upgrade from
0.26.x to 0.28, 0.29 and master so this should work.

I'm surprised that addresses were gone, were they not available when
running oc get addresses at all? Or were the just gone from the console?

The the authentication service upgrade may require some precautions when
upgrading, in particular if you are using the standard authservice. In
0.29, there is an AuthenticationService CRD, and when upgrading, you must
create an instance of this resource so that it will take ownership of the
existing:

apiVersion: admin.enmasse.io/v1beta1
kind: AuthenticationService
metadata:
  name: standard-authservice
  labels:
    app: enmasse
spec:
  type: standard
  standard:
    routeName: keycloak
    serviceName: standard-authservice
    deploymentName: keycloak
    credentialsSecret:
      name: keycloak-credentials
    storage:
      type: persistent-claim
      claimName: keycloak-data
      size: 1Gi

This should prevent the authentication service from being deleted.

Best regards,

Ulf

On Fri, Oct 11, 2019 at 2:14 PM Bob Claerhout <bob.claerhout at aloxy.io>
wrote:

> Hi,
>
> I'm getting this strange error after running Enmasse for several months:
>
> the server doesn't have a resource type "address"
>
> This is when I'm trying to get the address using
>
> oc/kubectl get address
>
>
> I'm using following environment:
>
>    - Enmasse version 0.26 (is there somewhere I can double check this?)
>    - OKD 3.11
>
> In our test environment this happened as well (which is strange to be
> happening at the same time). Last week we were still able to create and get
> the addresses in this environment.
> In an attempt to fix this issue, I upgraded to the newest 0.29 (using yaml
> bundles). The update succeeded after which I was able to get the addresses
> again.
> However, during this upgrade, I lost all addresses and authentication
> information which I would like to prevent from happening in our production
> environment. Also, the console (web gui) does not show the existing
> addresses and connections.
>
> Any hints on where to look in order to fix this?
> --
> Best regards,
> *Bob Claerhout*
> Software developer
> M +32 479 34 84 92
> The Beacon, Sint-Pietersvliet 7, 2000
> Antwerp
> bob.claerhout at aloxy.io | www.aloxy.io
> _______________________________________________
> enmasse mailing list
> enmasse at redhat.com
> https://www.redhat.com/mailman/listinfo/enmasse
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/enmasse/attachments/20191011/c150f056/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dhcngknppmelbbhi.png
Type: image/png
Size: 6330 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/enmasse/attachments/20191011/c150f056/attachment.png>