Uploaded image for project: 'ONAP Operations Manager'
  1. ONAP Operations Manager
  2. OOM-2800

ONAP fails to deploy while associating node affinity with mariadb-galera

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Medium Medium
    • None
    • Honolulu Release, Istanbul Release
    • charts
    • None
    • Hide

      SUMMARY

      when node affinity block is enabled for mariadb-galera in override config, ONAP fails to deploy the mariadb-galera chart

      OS / ENVIRONMENT

      • Kubernetes version:
        Client Version: v1.19.9
        Server Version: v1.19.9
      • Helm version:
        v3.5.2+g167aac7
      • Kubernetes mode of installation:
        rke version v1.2.7

      OOM VERSION

      Honolulu 8.0.1

      commit be3baadbcf424fab7c1dd1916a46558a6e9daeb1

      CONFIGURATION

      mariadb-galera:
  enabled: true
  affinity:
    podAntiAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
      - labelSelector:
          matchLabels:
            app.kubernetes.io/instance: dev
            app.kubernetes.io/name: mariadb-galera
        namespaces:
        - onap
        topologyKey: kubernetes.io/hostname
    nodeAffinity:
      requiredDuringSchedulingIgnoredDuringExecution:
        nodeSelectorTerms:
        - matchExpressions:
          - key: node-role.onap.org/database
            operator: Exists

      STEPS TO REPRODUCE

      deploy ONAP using above mentioned override config for mariadb-galera

      EXPECTED RESULTS

      mariadb-galera to run only on designated nodes with label "node-role.onap.org/database" and not to run more than one instance on the same node.

      ACTUAL RESULTS

      deployment fails

      Show
      SUMMARY when node affinity block is enabled for mariadb-galera in override config, ONAP fails to deploy the mariadb-galera chart OS / ENVIRONMENT Kubernetes version: Client Version: v1.19.9 Server Version: v1.19.9 Helm version: v3.5.2+g167aac7 Kubernetes mode of installation: rke version v1.2.7 OOM VERSION Honolulu 8.0.1 commit be3baadbcf424fab7c1dd1916a46558a6e9daeb1 CONFIGURATION mariadb-galera: enabled: true affinity: podAntiAffinity: requiredDuringSchedulingIgnoredDuringExecution: - labelSelector: matchLabels: app.kubernetes.io/instance: dev app.kubernetes.io/name: mariadb-galera namespaces: - onap topologyKey: kubernetes.io/hostname nodeAffinity: requiredDuringSchedulingIgnoredDuringExecution: nodeSelectorTerms: - matchExpressions: - key: node-role.onap.org/database operator: Exists STEPS TO REPRODUCE deploy ONAP using above mentioned override config for mariadb-galera EXPECTED RESULTS mariadb-galera to run only on designated nodes with label "node-role.onap.org/database" and not to run more than one instance on the same node. ACTUAL RESULTS deployment fails

          prabhjot prabhjot
          prabhjot prabhjot
          Votes:
          0 Vote for this issue
          Watchers:
          1 Start watching this issue

            Created:
            Updated:
            Resolved: