Forum Discussion

ahmedpasic's avatar
ahmedpasic
New Contributor
4 months ago

Registry API issue

I am running SwaggerHub in an airgapped Kubernetes cluster. I deployed everything using KOTS and with a lot of adjustments and after setting the configuration all of the services are up, except swaggerhub-registry-api. I get the following error message:

======================
Full classname legend:
======================
PermittedUrlsChecker:     "io.swagger.v3.parser.urlresolver.PermittedUrlsChecker"
RegistryApiModule:        "com.smartbear.swaggerhub.registry.dropwizard.RegistryApiModule"
========================
End of classname legend:
========================

    at com.google.inject.internal.Errors.throwCreationExceptionIfErrorsExist(Errors.java:568)
    at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:190)
    at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:113)
    at com.google.inject.Guice.createInjector(Guice.java:87)
    at com.smartbear.commons.dropwizard.GuiceBundle.run(GuiceBundle.java:46)
    at com.smartbear.commons.dropwizard.GuiceBundle.run(GuiceBundle.java:27)
    at io.dropwizard.core.setup.Bootstrap.run(Bootstrap.java:199)
    at io.dropwizard.core.cli.EnvironmentCommand.run(EnvironmentCommand.java:65)
    at io.dropwizard.core.cli.ConfiguredCommand.run(ConfiguredCommand.java:98)
    at io.dropwizard.core.cli.Cli.run(Cli.java:78)
    at io.dropwizard.core.Application.run(Application.java:94)
    at com.smartbear.swaggerhub.registry.dropwizard.RegistryApiServer.main(RegistryApiServer.java:50)
Caused by: java.lang.IllegalArgumentException: Empty label is not a legal name
    at java.base/java.net.IDN.toASCIIInternal(Unknown Source)
    at java.base/java.net.IDN.toASCII(Unknown Source)
    at io.swagger.v3.parser.urlresolver.matchers.UrlPatternMatcher.lambda$new$0(UrlPatternMatcher.java:24)
    at java.base/java.lang.Iterable.forEach(Unknown Source)
    at io.swagger.v3.parser.urlresolver.matchers.UrlPatternMatcher.<init>(UrlPatternMatcher.java:20)
    at io.swagger.v3.parser.urlresolver.PermittedUrlsChecker.<init>(PermittedUrlsChecker.java:27)
    at com.smartbear.swaggerhub.registry.dropwizard.RegistryApiModule.getPermittedUrlsChecker(RegistryApiModule.java:475)
    at com.smartbear.swaggerhub.registry.dropwizard.RegistryApiModule$$FastClassByGuice$$1895918.GUICE$TRAMPOLINE(<generated>)
    at com.smartbear.swaggerhub.registry.dropwizard.RegistryApiModule$$FastClassByGuice$$1895918.apply(<generated>)
    at com.google.inject.internal.ProviderMethod$FastClassProviderMethod.doProvision(ProviderMethod.java:260)
    at com.google.inject.internal.ProviderMethod.doProvision(ProviderMethod.java:171)
    at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.provision(InternalProviderInstanceBindingImpl.java:185)
    at com.google.inject.internal.InternalProviderInstanceBindingImpl$CyclicFactory.get(InternalProviderInstanceBindingImpl.java:162)
    at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
    at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:169)
    at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:45)
    at com.google.inject.internal.InternalInjectorCreator.loadEagerSingletons(InternalInjectorCreator.java:213)
    at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:186)
    ... 10 more
stream closed EOF for data-swaggerhub-prod/swaggerhub-registry-api-78999ffbf7-6dqz9 (swaggerhub-registry-api)

Any help is appreciated.

1 Reply

  • Hi,

    Key Areas to Investigate for swaggerhub-registry-api Not Starting

    1. Check Pod Status

    2. Image Pull Issues in Airgapped Environment

     Fix: Re-import and retag the image or fix the internal registry address in your KOTS configuration (Config.yaml or Admin Console).

    3. Configuration and Secrets

    4. Database Connectivity

     Fix:

    Ensure DB pod is running

    Ensure the correct internal service name and port is used

    Validate the DB_URI or similar values

    5. Readiness and Health Probes

    Fix:

    Check the Swagger Hub documentation for correct health check paths and ports

    Adjust readiness Probe in the deployment YAML

    6. KOTS Admin Console & Support Bundle

     

    Thanks, Regards

    Kamal Hinduja Geneva, Switzerland