Still got "Whitelabel Error Page" when opening the UI server in the UI Asset Lab

[TakumiHaruta]

I read #3892 and understood that this error happened because the UI server couldn't reach the static contents. Then, the new docker image of egeria-ui has already added to uistatic in the docker compose file.

https://github.com/odpi/egeria/blob/V2.9/open-metadata-resources/open-metadata-deployment/compose/tutorials/egeria-tutorial.yaml#L147

But I still got the same error when I execute ui-asset-search.ipynb and open https://localhost:18443/

Whitelabel Error Page
This application has no explicit mapping for /error, so you are seeing this as a fallback.

Fri May 07 11:51:38 GMT 2021
There was an unexpected error (type=Not Found, status=404).

How can I fix this or are there any additional steps before getting in the UI Asset Lab?

Environment and Procedure

• macOS Catalina 10.15.7
• Docker Desktop 3.3.1
• Egeria 2.9

1. Download the resources via https://github.com/odpi/egeria/releases/tag/V2.9
2. Execute docker-compose -f ./egeria-tutorial.yaml up -d at egeria-2.9/open-metadata-resources/open-metadata-deployment/compose/tutorials
3. Open the Jupyter Lab
4. Execute all codes in Configuring Egeria Servers Lab for the initial setup
5. Execute %run common/environment-check.ipynb and make sure all servers are configured and active like logs below
6. Execute all codes in UI Asset Search Lab
7. Open https://localhost:18443/ and get the error

%run ../common/environment-check.ipynb

Checking OMAG Server Platform availability...
    Core Platform is active
        Checking OMAG Server cocoMDS2
           ... cocoMDS2 is configured
           ... cocoMDS2 is active - ready to begin
        Checking OMAG Server cocoMDS3
           ... cocoMDS3 is configured
           ... cocoMDS3 is active - ready to begin
        Checking OMAG Server cocoMDS5
           ... cocoMDS5 is configured
           ... cocoMDS5 is active - ready to begin
        Checking OMAG Server cocoMDS6
           ... cocoMDS6 is configured
           ... cocoMDS6 is active - ready to begin
    Data Lake Platform is active
        Checking OMAG Server cocoMDS1
           ... cocoMDS1 is configured
           ... cocoMDS1 is active - ready to begin
        Checking OMAG Server cocoMDS4
           ... cocoMDS4 is configured
           ... cocoMDS4 is active - ready to begin
        Checking OMAG Server cocoView1
           ... cocoView1 is configured
           ... cocoView1 is active - ready to begin
    Dev Platform is active
        Checking OMAG Server cocoMDSx
           ... cocoMDSx is configured
           ... cocoMDSx is active - ready to begin
Done.

[planetf1]

Hi, You need to go to https://localhost:10443 in the docker-compose environment. This is now referred to in open-metadata-resources/open-metadata-deployment/compose/tutorials/README.md . We did add a reference in the 2.8 release notes, but it probably could have been clearer sorry.

The notebook itself at open-metadata-resources/open-metadata-labs/ui-labs/ui-asset-search.ipynb refers the user to the UI by the expression

"uiURL = os.environ.get('uiExternalURL', 'https://localhost:8443')\n"

• which for compose is set to

  egeria-tutorial.yaml:            - uiExternalURL=https://localhost:18443

  Similarly in the k8s environment as at open-metadata-resources/open-metadata-deployment/charts/odpi-egeria-lab/templates/jupyter.yaml we find

          - name: uiExternalURL
             value: "https://localhost:18443"

  So that I agree is confusing, and needs to be updated with the correct port name. That being said the ui-labs hasn't really been developed yet & needs further work

  Can you confirm if that URL works? Can you check the docs and either comment here or raise a PR if you think it could be clearer in other places

  cc: @sarbull

[planetf1]

Further, it's worth noting that in the k8s environment, accessing the UI or indeed any service is very depending on what port forwarding/ingress rules have been set up, and from within the notebook it's not possible to be sure any URL given is correct in terms of external accessibility.

[planetf1]

I've opened a PR to fix the URL that is presented to the user, which should at least make it clearer for compose. @sarbull over to you to determine if you feel anything else is needed

[TakumiHaruta]

@planetf1 Thank you for explaining in detail. I could enter the UI via https://localhost:10443, but it doesn't show any data. (The lab of Egeria 2.4 could show the sample data.)

Some part of the lab haven't actually updated as you said. I'll try to find other ways for understanding the system.

[planetf1]

@TakumiHaruta The polymer UI will show certain asset types - for example if you run the 'creating a data catalog' app, and do a search in that UI by asset, and use a search string of 'week' , it should show some csv filesets. @sarbull and @bogdan-sava work on this UI and can elaborate more on this business-oriented UI.

If you want to explore the assets in the system at a more technical level, you can use the React Based UI at https://localhost:18091 (for docker-compose) - I would login as garygeeke/admin . Then you can go to 'repository explorer' and perform searches there. There's some more detail on this UI at https://github.com/odpi/egeria-react-ui/blob/main/docs/RepositoryExplorer/RepositoryExplorerGuide.md

[sarbull]

@TakumiHaruta please also check the odpi/egeria-ui project and check the README on how to start the User Interface. They are two separate projects now, API and UI approach.

[sarbull]

@TakumiHaruta @planetf1 the simplest way to start Egeria is to start the backend/API separately a given PORT and enable CORS from application.properties and then start the egeria-ui project with npm run start --api-url=http://api:PORT linking the UI to backend data or npm run build --api-url=http://api:PORT and serve it with nginx or any other static server