Closed dkelosky closed 5 years ago
Hello Dan, You have to configure zosmf in order to run the Catalog. The Catalog is not able to authenticate without zosmf. We are currently working on the dummy authentication which will resolve this problem.
[DS] 2019-07-12 17:00:48.824 <ZWEADS1:Thread-14:63920> dk635460 WARN (c.c.m.d.s.ServiceDefinitionProcessor,ServiceDefinitionProcessor.java:94) One of the instanceBaseUrl of zosmfserviceid is not defined. The instance will not be created.
Regards, Jirka
Thanks @JirkaAichler - I think I misunderstood "z/OSMF is required for the API Catalog login.". Sorry for the distracting issue!
Hi @JirkaAichler - is this the only thing that I need to set for the z/OSMF configuration? Or are there other places?: instanceBaseUrls: # list of base URLs for each instance
Try the following steps:
serviceId
and instanceBaseUrls
in the sample apiml:
security:
auth:
provider: zosmf
zosmfServiceId: zosmfca32 # Replace me with the correct z/OSMF service id
I hope this will help. We are currently working on the improvements and better documentation which should be available during the next sprint.
You can use the following zosmf definition from Broadcom internal repository.
Thanks @JirkaAichler - I seemed to have gotten past that specific error. The next piece that I get is:
DS] 2019-08-14 17:17:03.445 <ZWEADS1:DiscoveryClient-CacheRefreshExecutor-0:85100> myuser ERROR (c.n.d.DiscoveryClient,DiscoveryClient.java:972)
DiscoveryClient_DISCOVERY/localhost:discovery:10011 - was unable to refresh its cache! status = Cannot execute request on any known server
[DS] com.netflix.discovery.shared.transport.TransportException: Cannot execute request on any known server
[DS] at com.netflix.discovery.shared.transport.decorator.RetryableEurekaHttpClient.execute(RetryableEurekaHttpClient.java:112)
[DS] at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.getApplications(EurekaHttpClientDecorator.java:134)
[DS] at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator$6.execute(EurekaHttpClientDecorator.java:137)
[DS] at com.netflix.discovery.shared.transport.decorator.SessionedEurekaHttpClient.execute(SessionedEurekaHttpClient.java:77)
[DS] at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.getApplications(EurekaHttpClientDecorator.java:134)
[DS] at com.netflix.discovery.DiscoveryClient.getAndStoreFullRegistry(DiscoveryClient.java:1051)
[DS] at com.netflix.discovery.DiscoveryClient.fetchRegistry(DiscoveryClient.java:965)
[DS] at com.netflix.discovery.DiscoveryClient.refreshRegistry(DiscoveryClient.java:1473)
[DS] at com.netflix.discovery.DiscoveryClient$CacheRefreshThread.run(DiscoveryClient.java:1440)
[DS] at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
[DS] at java.util.concurrent.FutureTask.run(Unknown Source)
[DS] at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
[DS] at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
[DS] at java.lang.Thread.run(Unknown Source)
Any common reasons for that problem? I'll continue searching in the meantime.
Hello Dan, Is this error causing any problem? We are aware that our logs contain various Zuul and Eureka errors but we had no time to clean them. It is in our backlog for a very long time but unfortunately, there are stories with a higher priority (such as security).
Hi Jirka - I'm not sure if it's the cause of my error or not. I still haven't gotten the API catalog to run without errors yet. I'm trying to configure z/OSMF for authentication. I'll keep messing with this, and follow up when I am able to have the catalog start.
Dan, you can take Broadcom z/OSMF configuration from the internal repo.
I'll close this until I'm able to try it again. Thanks @JirkaAichler
Describe the bug When running the API ML from a fresh clone on my workstation, I get a message in the catalog UI that
The API Catalog is not running
.Steps to Reproduce
git clone https://github.com/zowe/api-layer
./gradlew build
npm run api-layer
Expected behavior The API Catalog is running 😄
Screenshots
Logs
API Catalog Web UI (in case of API Catalog issue):