Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-13601

[camel-api example] getting `NO Content` on /api-doc endpoint

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Critical
    • fuse-next-TP1-GA
    • fuse-next-TP1-GA
    • Camel-K
    • None

    Description

      ➜  kamel get     
NAME    PHASE   KIT
api     Running kit-bqhfdnesooi0thmdgebg

➜  echo $URL/api-doc
http://api-camel-api.apps.camel-k-43-dev.openshift-aws.rhocf-dev.com/api-doc


➜  curl -i $URL/api-doc
HTTP/1.1 204 No Content
Accept: */*
Forwarded: for=10.40.193.126;host=api-camel-api.apps.camel-k-43-dev.openshift-aws.rhocf-dev.com;proto=http;proto-version=""
User-Agent: curl/7.55.1
X-Forwarded-For: 10.40.193.126
X-Forwarded-Host: api-camel-api.apps.camel-k-43-dev.openshift-aws.rhocf-dev.com
X-Forwarded-Port: 80
X-Forwarded-Proto: http
Set-Cookie: d02cddd791e8cdeb48af03780ffe52b3=5bde13dd0d84fde8e296debedc4bfffd; path=/; HttpOnly
Cache-control: private

      Everything else works as expected but missing OpenAPI resource is a real problem for 3scale.

      Attachments

        Issue Links

          is caused by

          Sub-task - The sub-task of the issue ENTESB-13566 Camel-K-API quickstart testing

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Activity

            People

              nicolaferraro Nicola Ferraro (Inactive)
              jbouska@redhat.com Jan Bouska
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: