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

SO so-mariadb readinessCheck fails for local MariaDB instance

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Low Low
    • Istanbul Release
    • Guilin Release
    • charts
    • Hide

      SUMMARY

      In the values.yaml of so-mariadb the MariaDB instance name is defined in the Global section and used as container name for the Readiness probe:

        mariadbGalera:
    nameOverride: &mariadbName mariadb-galera
    serviceName: mariadb-galera
    servicePort: "3306"
  migration:
    enabled: false
    dbHost: mariadb-galera
    dbPort: 3306
    dbUser: root
    dbPassword: secretpassword

readinessCheck:
  wait_for:
    - *mariadbName

      In case you choose a local MariaDB instance in the parent SO values.yaml, the name should be changed to "so-mariadb-galera" and need to be also changed in this chart.

      Otherwise the Readiness Check in the created Job within this chart will fail.

      So either a note in the SO values.yaml should be added to change so-mariadb as well or the value should be automatically overwritten within so-mariadb (which I was not able to manage....).

       

      OS / ENVIRONMENT

      • Helm version:
        v3.3
        *
      Show
      SUMMARY In the values.yaml of so-mariadb the MariaDB instance name is defined in the Global section and used as container name for the Readiness probe: mariadbGalera: nameOverride: &mariadbName mariadb-galera serviceName: mariadb-galera servicePort: "3306" migration: enabled: false dbHost: mariadb-galera dbPort: 3306 dbUser: root dbPassword: secretpassword readinessCheck: wait_for: - *mariadbName In case you choose a local MariaDB instance in the parent SO values.yaml, the name should be changed to "so-mariadb-galera" and need to be also changed in this chart. Otherwise the Readiness Check in the created Job within this chart will fail. So either a note in the SO values.yaml should be added to change so-mariadb as well or the value should be automatically overwritten within so-mariadb (which I was not able to manage....).   OS / ENVIRONMENT Helm version: v3.3 *

          sdesbure sdesbure
          andreasgeissler Andreas Geissler
          Votes:
          2 Vote for this issue
          Watchers:
          3 Start watching this issue

            Created:
            Updated:
            Resolved: