Uploaded image for project: 'AMQ Broker'
  1. AMQ Broker
  2. ENTMQBR-4127

Route name generated by operator might be too long for Openshift

    XMLWordPrintable

Details

    • Bug
    • Status: To Do
    • Minor
    • Resolution: Unresolved
    • AMQ 7.8.0.dev
    • None
    • documentation
    • None
    • Hide
      For each broker Pod in an Operator-based deployment, the default name of the Route that the Operator creates for access to the AMQ Broker management console includes the name of the Custom Resource (CR) instance, the name of the OpenShift project, and the name of the OpenShift cluster. For example, `my-broker-deployment-wconsj-0-svc-rte-my-openshift-project.my-openshift-domain`. If some of these names are long, the default Route name might exceed the limit of 63 characters that OpenShift enforces. In this case, in the OpenShift Container Platform web console, the Route shows a status of `Rejected`.

      To work around this issue, use the OpenShift Container Platform web console to manually edit the name of the Route. In the console, click the Route. On the *Actions* drop-down menu in the top-right corner, select `Edit Route`. In the YAML editor, find the `spec.host` property and edit the value.
      Show
      For each broker Pod in an Operator-based deployment, the default name of the Route that the Operator creates for access to the AMQ Broker management console includes the name of the Custom Resource (CR) instance, the name of the OpenShift project, and the name of the OpenShift cluster. For example, `my-broker-deployment-wconsj-0-svc-rte-my-openshift-project.my-openshift-domain`. If some of these names are long, the default Route name might exceed the limit of 63 characters that OpenShift enforces. In this case, in the OpenShift Container Platform web console, the Route shows a status of `Rejected`. To work around this issue, use the OpenShift Container Platform web console to manually edit the name of the Route. In the console, click the Route. On the *Actions* drop-down menu in the top-right corner, select `Edit Route`. In the YAML editor, find the `spec.host` property and edit the value.
    • Documented as Known Issue

    Description

      Given long enough cluster name and statefulset name, routes might not be created due to being too long.

       

      Example: web console URL for web console in our test run results in rejected URL:

       

      host name validation errors: spec.host: Invalid value: "authentication-wconsj-0-svc-rte-e2e-tests-broker-framework-bcmz2.apps.brokerteam.amq-broker-qe.psi.redhat.com": must be no more than 63 characters

      Attachments

        Activity

          People

            jbyrne@redhat.com John Byrne
            mkrutov Mikhail Krutov
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: