-
Bug
-
Resolution: Done
-
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
- is incorporated by
-
ENTMQBR-8069 Failure to create Route is not indicated in CR Status
- Verified