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

Ulf Lilleengen lulf at redhat.com
Tue Oct 15 07:35:10 UTC 2019 

Hi Bob,

The agent/console appears to be aware of the addresses and they exist, so
thats good.

Could you try to grant your user (assuming this is 'aloxy')  the
tenant-edit role? (i.e. oc adm policy add-role-to-user enmasse.io:tenant-edit
aloxy -n <namespace of your address space>)

If you open your browser developer tools, are there any errors?

Could you try with a different browser or use private mode to make sure
there is no cached data?

Best regards,

Ulf

On Tue, Oct 15, 2019 at 9:18 AM Bob Claerhout <bob.claerhout at aloxy.io>
wrote:

> Hi Ulf,
>
> Attached to this mail, you can find the logs of the pod.
> The following screenshot is the response on the given command:
>
>
> Best regards,
> Bob
>
> On 10/14/19 1:45 PM, Ulf Lilleengen wrote:
>
> Hi Bob,
>
> For the console, could you provide the following:
>
> * logs from the agent container in the admin pod
> * oc policy who-can get addresses -n <namespace of address space>
>
> Best regards,
>
> Ulf
>
>
>
> On Mon, Oct 14, 2019 at 1:11 PM Bob Claerhout <bob.claerhout at aloxy.io>
> wrote:
>
>> Ulf,
>>
>> In the upgraded environment I was able to get the addresses before.
>> Just to be sure, I restarted the api-server as well but I'm still unable
>> to retrieve the addresses via the console.
>>
>> Best regards,
>> Bob
>>
>> On 10/14/19 12:20 PM, Ulf Lilleengen wrote:
>>
>> Hi Bob,
>>
>> Does this fix the upgrade problem as well?
>>
>> Best regards,
>>
>> Ulf
>>
>> On Mon, Oct 14, 2019 at 10:31 AM Bob Claerhout <bob.claerhout at aloxy.io>
>> wrote:
>>
>>> Hi Ulf,
>>>
>>> Your hint on looking into the api-server was the thing I needed (for
>>> 0.26).
>>> I was getting following log continuously:
>>>
>>> GC(19) Pause Young (Allocation Failure)
>>>
>>> After rebooting this server, the allocation failures were gone (at least
>>> most of the time) and I was able to get the addresses again.
>>> Thanks for you help and time!
>>> Best regards,
>>> Bob
>>>
>>> On 10/14/19 9:29 AM, Ulf Lilleengen wrote:
>>>
>>> Hi Bob,
>>>
>>> You can use `oc get addresses` to get addresses in 0.26.x as well. If
>>> that is not working, then check `oc get apiservices | grep enmasse` to make
>>> sure the api service exists. If the service exists, then get its output (-o
>>> yaml) to see if it is able to talk to the api-server. Also the api-server
>>> logs may give an indication of the failure if the apiservice is registered.
>>>
>>> In you already upgraded 0.29, try oc get configmaps -l
>>> type=address-space -n enmasse-infra and oc get configmaps -l
>>> type=address-config -n enmasse-infra to verify that the configuration is
>>> actually there.
>>>
>>> Best regards,
>>>
>>> Ulf
>>>
>>> On Mon, Oct 14, 2019 at 9:12 AM Bob Claerhout <bob.claerhout at aloxy.io>
>>> wrote:
>>>
>>>> Hi Ulf,
>>>>
>>>> I'm using the bundles downloaded from
>>>> https://github.com/EnMasseProject/enmasse/releases/tag/0.29.1
>>>> I have indeed installed the other bundles as well. Although I did not
>>>> include them in my previous email.
>>>> Regarding the UI: I'm able to get the addresses using the same user and
>>>> password using the command line (kubectl get address) while the console UI
>>>> is still empty.
>>>>
>>>> Besides the upgrade towards 0.29, do you have any idea on how to be
>>>> able to use the command line to get the addresses in my "old" install? The
>>>> address resource seems to be gone and I rather not update Enmasse right now
>>>> (because of customers).
>>>> Do you see a way to get the address resource working again in an
>>>> existing installation?
>>>>
>>>> Best regards,
>>>> Bob
>>>>
>>>> On 10/11/19 3:28 PM, Ulf Lilleengen wrote:
>>>>
>>>> Hi Bob,
>>>>
>>>> What plans are you using for the addresses?
>>>>
>>>> Which bundles did you apply on 0.29? In addition to
>>>> install/bundles/enmasse , you need to apply
>>>> install/components/example-plans to get the updated plans, and
>>>> install/components/example-roles to get the updated roles so that users
>>>> will be able to view addresses in the console.
>>>>
>>>> Regarding the UI, on 0.29 the console authenticates users using RBAC
>>>> instead of keycloak users, so you must log in with the openshift user who
>>>> has access to the address resources.
>>>>
>>>> Best regards,
>>>>
>>>> Ulf
>>>>
>>>> On Fri, Oct 11, 2019 at 2:53 PM Bob Claerhout <bob.claerhout at aloxy.io>
>>>> wrote:
>>>>
>>>>> Hi Ulf,
>>>>>
>>>>> Thanks for the quick response. Attached to this mail you can find the
>>>>> yaml setup files I used. We are using both topics and queues. We are using
>>>>> hono which publishes the messages on a queue while our business application
>>>>> communicates using topics.
>>>>> The addresses were indeed gone when running "oc get addresses" as
>>>>> well. After the upgrade, when adding the addresses using the yaml files,
>>>>> the addresses showed up in the UI but have disappeared again.  They are
>>>>> still showing up as a response to "oc get addresses" however and are also
>>>>> available for our application (so are they in the production environment).
>>>>> Thanks for the hint on the application service. We are indeed using
>>>>> the standard auth service.
>>>>>
>>>>> Best regards,
>>>>> Bob
>>>>> On 10/11/19 2:32 PM, Ulf Lilleengen wrote:
>>>>>
>>>>> 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/20191015/a8a52462/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jfhjclhdobbppman.png
Type: image/png
Size: 26606 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/enmasse/attachments/20191015/a8a52462/attachment.png>
-------------- 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/20191015/a8a52462/attachment-0001.png>

More information about the enmasse mailing list