Loading...

XML

Word

Printable

QE Test Coverage:
?
Workaround:

Workaround Exists
Workaround Description:
Hide

It is possible to workaround this issue manually till the scale-up/scale-down (which influences the services and their definitions) happens.

Edit the following snipped of code in services' yaml definitions and point it towards the correct pods.

selector: ActiveMQArtemis: ex-aao application: ex-aao-app statefulset.kubernetes.io/pod-name: ex-aao-ss-0

The ordinal number in pod name must correspond with ordinal nuber for that specific service. So for example if you have ex-aao-all-7-svc the statefulset.kubernetes.io/pod-name: ex-aao-ss-10 must be changed to statefulset.kubernetes.io/pod-name: ex-aao-ss-7
Show
It is possible to workaround this issue manually till the scale-up/scale-down (which influences the services and their definitions) happens. Edit the following snipped of code in services' yaml definitions and point it towards the correct pods. selector: ActiveMQArtemis: ex-aao application: ex-aao-app statefulset.kubernetes.io/pod-name: ex-aao-ss-0 The ordinal number in pod name must correspond with ordinal nuber for that specific service. So for example if you have ex-aao-all-7-svc the statefulset.kubernetes.io/pod-name: ex-aao-ss-10 must be changed to statefulset.kubernetes.io/pod-name: ex-aao-ss-7

Downstream operator 7.6 with default yamls when deployed with multiple instance, creates services and routes for every pod in the stateful set.

mapping of service to pod happens incorrectly, for example:

service " ex-aao-amqp-0-svc" should be mapped to pod "ex-aao-ss-0" and service "ex-aao-amqp-1-svc" should be linked to pod "ex-aao-ss-1".

In fact, both services are linked to same pod (ex-aao-ss-1).

is cloned by

ENTMQBR-3725 [LTS] Porting ENTMQBR-3516

Closed

Mikhail Krutov