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

dmaap-dr-node deployment is failing - casablanca

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Medium
    • Resolution: Done
    • None
    • None
    • None

    Description

      it's the same "bug" than OOM-1559 but for dmaap-dr-node. Same solution should apply

       

      You can see it only when dr-prov is started

      20190104 michaelobrien dmaap is ok now - but requires a restart of the pod
      update: a 2nd sequenced deploy (11 min between components) - dmaap is fully up on 3.0.0-ONAP - 4 x 32g vms

      onap onap-dmaap-dbc-pg-0 1/1 Running 0 4h
      onap onap-dmaap-dbc-pg-1 1/1 Running 0 4h
      onap onap-dmaap-dbc-pgpool-c5f8498-8zbvh 1/1 Running 0 4h
      onap onap-dmaap-dbc-pgpool-c5f8498-njnhq 1/1 Running 0 4h
      onap onap-dmaap-dmaap-bus-controller-557dc8c59c-c4lpd 1/1 Running 0 4h
      onap onap-dmaap-dmaap-dr-db-576f7968b8-r5s5q 1/1 Running 0 4h
      onap onap-dmaap-dmaap-dr-node-7647f9d6d8-zrqfn 1/1 Running 0 4h
      onap onap-dmaap-dmaap-dr-prov-f4d84869f-5hxvf 1/1 Running 0 4h
      onap onap-dmaap-message-router-76f4799d-59nmp 1/1 Running 0 4h
      onap onap-dmaap-message-router-kafka-56c7c546c-bjhpt 1/1 Running 3 4h
      onap onap-dmaap-message-router-zookeeper-7d69b496bc-q55pg 1/1 Running 0 4h

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. DMAAP-949 dr-node/dr-prov deployment failure does not affect PASS healthcheck

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. OOM-1559 dmaap-dr-prov deployment is failing - master

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. DMAAP-964 [DMAAP] DMAAP deployment failures starting 20190115 on casablanca branch

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-898 ONAP Deployment Resiliency changes to deploy without POD failures

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. LOG-913 POMBA: 1 of 11 pods failing on sequenced startup on 3.0.0-ONAP - pomba is 22 on the order - looks timing related

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. OOM-1543 Helm deploy/undeploy adjustments for triage of failed/unlisted deployments

          • High - Severely impaired functionality. Erratic performance and reduced system availability. It may cause major components or features of the system to be unavailable although certain parts of the system remain functional. A workaround may exist but its use is unsatisfactory or at a high time cost (manual intervention required). Must be fixed in any of the upcoming builds and should be included in the current release.
          • Closed

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. OOM-1548 DMaaP support for multi-site applications

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1561 OOF Music Cassandra statefulset is failing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. OOM-1562 Contrib netbox app deployment is failing

          • Medium - Failure of non-critical aspects of the system but results in an inconvenient situation. It causes some undesirable behavior, but the system is still functional. There is a reasonably satisfactory workaround. It is still a valid defect that should be corrected May be fixed after the release or in the next release.
          • Closed
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          # Subject Branch Project Status CR V
          74972,1 Fix dmaap-dr-node deployment failing master oom Status: MERGED +2 +1

          Activity

            People

              melliott Mike Elliott
              sdesbure Sylvain Desbureaux
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: