Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1539

Container URL is not shown in Business central server management page

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Minor Minor
    • None
    • 7.1.0.GA
    • Business Central, Cloud
    • OpenShift

    • CR1
    • Hide

      Deploy Kie server to OpenShift, connect it to local Business central (Business central can be deployed on OpenShift too).
      Deploy container into the Kie server.
      Open Server management page.
      Select deployed container - container URL is not shown.

      Show
      Deploy Kie server to OpenShift, connect it to local Business central (Business central can be deployed on OpenShift too). Deploy container into the Kie server. Open Server management page. Select deployed container - container URL is not shown.

      The issue happens just in case when managed Kie server is located on OpenShift. In case Kie server is placed locally (localhost) then it works.

      When Kie server is connected to the Business central it can be managed using server management page. If user clicks on server under Remote servers list then correct URL is shown in server page. However if user clicks on container listed under Deployment units then its URL is not shown - see screenshot.
      I have tried to analyze request sent by Business central to check that container URL is working and it seems that expected response is returned (401 Unauthorized).

      karreiro_ I am assigning it to you as you were an author of PR implementing URL disabling functionality - https://github.com/kiegroup/kie-wb-common/pull/1888. If you need to simulate this by placing Kie server to OpenShift I can help you.

              rhn-support-fspolti Filippe Spolti
              ksuta Karel Suta
              Karel Suta Karel Suta
              Karel Suta Karel Suta
              Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: