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

MySQL slave nodes don't deploy when mysql.replicaCount > 1

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Medium
    • Resolution: Done
    • Affects Version/s: Beijing Release
    • Fix Version/s: Beijing Release
    • Labels:
      None
    • Sprint:
      OOM Sprint 10 - Integration

      Description

      If I try to configure an application like SDN-C to have more than one MySQL datastore ( for local redundancy ), the master MySQL instance comes up fine, but slaves do not.

      $ kubectl get pods -n onap
      NAME READY STATUS RESTARTS AGE
      onap-sdnc-0 0/2 Init:0/1 0 8m
      onap-sdnc-db-0 2/2 Running 0 8m
      onap-sdnc-db-1 0/2 Init:CrashLoopBackOff 5 4m
      onap-sdnc-dgbuilder-7bcdf594b4-t8v2t 1/1 Running 0 8m
      onap-sdnc-dmaap-listener-54f7bd6f4f-mnnvp 0/1 Init:0/1 0 8m
      onap-sdnc-nfs-provisioner-87b5cb7f9-rnqcq 1/1 Running 0 8m
      onap-sdnc-portal-5c4ff95c84-sv8zw 0/1 Init:0/1 0 8m
      onap-sdnc-ueb-listener-656bf4888d-vhzzf 0/1 Init:0/1 0 8m

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            • Assignee:
              jmac James MacNider
              Reporter:
              jmac James MacNider
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: