Uploaded image for project: 'Data Collection, Analytics, and Events'
  1. Data Collection, Analytics, and Events
  2. DCAEGEN2-1012

PNDA Nodeport 30288 conflict with sniro-emulator - should be 30400

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • High
    • Resolution: Done
    • Casablanca Release
    • Dublin Release
    • None
    • DCAE R4 Sprint 3, DCAE R4 Sprint 4, DCAE R4 Sprint 5, DCAE R4 Sprint 6, DCAE R4 Sprint 7

    Description

       enabling pnda will experience a nodeport conflict with sniro

       fix is to add a 304 prefix and change the nodeport to 00 in the yaml below - to match the wiki

      https://git.onap.org/oom/tree/kubernetes/pnda/charts/dcae-pnda-bootstrap/values.yaml#n41

      https://wiki.onap.org/display/DW/OOM+NodePort+List 

      misnammed mirror in dcae-pnda-boostrap

      in conflict with

      onap          sniro-emulator                     NodePort       10.43.194.41    <none>                                 80:30288/TCP                                                  4h

      nodePort: 88

       

      disabled by default

      pnda:

        enabled: false

       

      missing from dev.yaml, disable-all-charts.yaml

       

      mirrorNodePort: 88

      Attachments

        Issue Links

          blocks

          Bug - A problem which impairs or prevents the functions of the product. OOM-1531 NodePort Adjustments

          • 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. VVP-128 VVP-EXT-HAPROXY node port is not fixed - was 30229 - then 30298 (taken from log - no more conflict)

          • 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. VVP-129 VVP needs to reserve/document their Kubernetes NodePorts

          • 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. OPTFRA-405 30223 used by DCAE not OOF - adjusted nodeport wiki

          • 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...

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

          Activity

            People

              michaelobrien Michael O'Brien
              michaelobrien Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: