Loading...

XML

Word

Printable

Details

Type: Bug
Resolution: Done
Priority: Undefined
Fix Version/s: None
Affects Version/s: AMQ 7.10.0.OPR.1.GA
Component/s: operator
Labels:
None

Blocked:
False
Blocked Reason:
None
Ready:
False
Estimated Difficulty:
Medium
Target Release:

Future GA
Workaround:

Workaround Exists
Workaround Description:
Hide

manaually change

the service label

the service pod selector label

from rht.comp_ver=7.10.0 and rht.prod_ver=2022.Q2

to rht.comp_ver=7.10.1 and rht.prod_ver=2022.Q3
Show
manaually change the service label the service pod selector label from rht.comp_ver=7.10.0 and rht.prod_ver=2022.Q2 to rht.comp_ver=7.10.1 and rht.prod_ver=2022.Q3
Git Pull Request:
https://github.com/rh-messaging/amq-docs/pull/1488
Steps to Reproduce:
Hide

oc new-project case03389160 oc create -f amq710-og.yaml oc create -f amq710-sub.yaml

since this is manually, approve the installplan for installing 7.10.0-opr1 csv and operator

Once the operator is up and running, install the AMQ7.10 instance

oc create -f amq710-cr.yaml

Once the pods is up, check the service

$ oc get svc -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR ex-aao-acceptor-0-svc ClusterIP 172.30.60.200 <none> 61616/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0 ex-aao-hdls-svc ClusterIP None <none> 8161/TCP,61616/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application ex-aao-ping-svc ClusterIP None <none> 8888/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application ex-aao-wconsj-0-svc ClusterIP 172.30.137.35 <none> 8161/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0

Now, approval all installplans from opr-1..4 and 7.10.1-opr1

you will find the service not change but the pods label has updated.

Notice both ex-aao-hdls-svc and ex-aao-ping-svc are updated but not acceptor and wconsj

$ oc get svc -owide -w NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR ex-aao-acceptor-0-svc ClusterIP 172.30.60.200 <none> 61616/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0 ex-aao-hdls-svc ClusterIP None <none> 8161/TCP,61616/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app ex-aao-ping-svc ClusterIP None <none> 8888/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app ex-aao-wconsj-0-svc ClusterIP 172.30.137.35 <none> 8161/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0
Show
oc new -project case03389160 oc create -f amq710-og.yaml oc create -f amq710-sub.yaml since this is manually, approve the installplan for installing 7.10.0-opr1 csv and operator Once the operator is up and running, install the AMQ7.10 instance oc create -f amq710-cr.yaml Once the pods is up, check the service $ oc get svc -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR ex-aao-acceptor-0-svc ClusterIP 172.30.60.200 <none> 61616/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0 ex-aao-hdls-svc ClusterIP None <none> 8161/TCP,61616/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application ex-aao-ping-svc ClusterIP None <none> 8888/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application ex-aao-wconsj-0-svc ClusterIP 172.30.137.35 <none> 8161/TCP 21s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0 Now, approval all installplans from opr-1..4 and 7.10.1-opr1 you will find the service not change but the pods label has updated. Notice both ex-aao-hdls-svc and ex-aao-ping-svc are updated but not acceptor and wconsj $ oc get svc -owide -w NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR ex-aao-acceptor-0-svc ClusterIP 172.30.60.200 <none> 61616/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0 ex-aao-hdls-svc ClusterIP None <none> 8161/TCP,61616/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app ex-aao-ping-svc ClusterIP None <none> 8888/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app ex-aao-wconsj-0-svc ClusterIP 172.30.137.35 <none> 8161/TCP 9m32s ActiveMQArtemis=ex-aao,application=ex-aao-app,com.company=Red_Hat,rht.comp=Broker_AMQ,rht.comp_ver=7.10.0,rht.prod_name=Red_Hat_Integration,rht.prod_ver=2022.Q2,rht.subcomp=broker-amq,rht.subcomp_t=application,statefulset.kubernetes.io/pod-name=ex-aao-ss-0

SFDC Cases Counter:
SFDC Cases Links:

Description

When upgrade from amq-broker-operator.v7.10.0-opr-1 .. amq-broker-operator.v7.10.1-opr-1, the service will have the wrong pod selector

Starting from amq-broker-operator.v7.10.0-opr-3 or 4 won't reproduce this issue.

Attachments

Issue Links

clones

ENTMQBR-7534 [Operator] When upgrade from amq-broker-operator.v7.10.0-opr-1 .. amq-broker-operator.v7.10.1-opr-1, the service will have the wrong pod selector

Closed

Activity

People

Assignee:: John Clifford

Reporter:: Roger Hui

Votes:: 0 Vote for this issue

Watchers:: 1 Start watching this issue

Dates

Created:: 2023/02/14 1:04 PM

Updated:: 2023/04/27 9:38 AM

Resolved:: 2023/04/27 9:38 AM