Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-30545

(8.1.z) Scale up/down no longer work if label is added into the WildFlyServer

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • 8.1.0.GA-CR7
    • Operator
    • False
    • Hide

      None

      Show
      None
    • False
    • Known Issue
    • Hide

      Deploy EAP using operator like:

      apiVersion: wildfly.org/v1alpha1
kind: WildFlyServer
metadata:
  name: example
  namespace: rosa-demo
spec:
  applicationImage: 'image-registry.openshift-image-registry.svc:5000/rosa-demo/helloworld:latest'
  replicas: 1

      and then add label:

        labels:
    my-cool-label: hi

      and change number of replicas. No change will happen.

      Show
      Deploy EAP using operator like: apiVersion: wildfly.org/v1alpha1 kind: WildFlyServer metadata: name: example namespace: rosa-demo spec: applicationImage: 'image-registry.openshift-image-registry.svc:5000/rosa-demo/helloworld:latest' replicas: 1 and then add label: labels: my-cool-label: hi and change number of replicas. No change will happen.

      EAP operator is not able to scale up/down EAP pods if label is added into the existing WildFlyServer yaml like:

      apiVersion: wildfly.org/v1alpha1
kind: WildFlyServer
metadata:
  name: example
  namespace: rosa-demo
  labels:
    my-cool-label: hi
spec:
  applicationImage: 'image-registry.openshift-image-registry.svc:5000/rosa-demo/helloworld:latest'
  replicas: 1

      Expected result: Pods will be redeployed with updated labels.
      Actual result: Any changes to number of replicas are not reflected and number of pods stay the same.

              yborgess1@redhat.com Yeray Borges Santana
              mnovak1@redhat.com Miroslav Novak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: