Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Major
Fix Version/s: AMQ 7.11.0.OPR.1.GA
Affects Version/s: None
Component/s: container image, operator, security
Labels:
- CR
- failed_qa
- security

Blocked:
False
Blocked Reason:
None
Ready:
False
GSS Priority:
Target Release:

AMQ 7.11.0.OPR.1.GA
Workaround:

Workaround Exists
Workaround Description:

Hide

The workaround is to use broker.properties to create the address resources in the broker CR.

Show
The workaround is to use broker.properties to create the address resources in the broker CR.

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

ActiveMQArtemisSecurity is not applied when the broker is not Ready (0/1 Running).

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

010-message-broker-amq.yaml
1 kB
2022/05/11 3:48 PM
020-message-broker-amq-readiness-queue.yaml
0.4 kB
2022/05/11 3:48 PM
030-message-broker-amq-security.yaml
2 kB
2022/05/11 3:48 PM

is documented by

ENTMQBR-7819 [Docs] Clarify what the status means for brokerProperties and JAAS properties login modules

Closed

relates to

ENTMQBR-6126 Utilize new broker health checks for Readiness and Liveness probes

Backlog

ENTMQBR-6878 [Operator] Address/Queue cannot be created if the "applyToCrNames" is used

Closed

ENTMQBR-6689 Deploy security CR to existing broker sometimes causes failure

Closed

ENTMQBR-6841 SS can not recover itself after reaching a failure state

Closed

Assignee:: Gary Tully

Reporter:: Abel Bouchama

Tester:: Tiago Bueno

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2022/05/11 3:47 PM

Updated:: 2023/04/11 11:10 AM

Resolved:: 2023/04/03 11:48 AM