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

Non-ASCII AMQ Acceptor names put SS into stuck 0/1 state with no feedback on CR Status

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • AMQ 7.11.0.GA
    • None
    • None
    • False
    • None
    • False

      1. Create a CR including a non-ascii named acceptor
      2. Wait for deployment
      Expected:
      CR Status responds with "invalid cr" as non-ascii characters in Acceptor name lead to attempt to create a non-ascii named Service, which is not supported
      Real: no feedback, just pod / ss stuck in 0/1 state with "Valid: true".

      Example of CR to be attached

              dbruscin Domenico Francesco Bruscino
              mkrutov Mikhail Krutov
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: