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

NodePort conflict between Clamp and Pomba

    XMLWordPrintable

Details

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

    Description

      Clamp recently made a change to their chart which added a nodePort that was already claimed by Pomba:  https://gerrit.onap.org/r/#/c/63235

       

      This issue was first observed by George Clapp:  https://lists.onap.org/g/onap-discuss/message/12209

       

      It looks like the entire 302XX node port range is in use, so Clamp will probably need to move over to one of the other prefixes.

      Attachments

        Issue Links

          blocks

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. LOG-642 Move log 30258 nodeport to 304xx - as I gave 30258 to clamp for OOM-1364

          • 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
          is blocked by

          Bug - A problem which impairs or prevents the functions of the product. OOM-1364 CLAMP uses already reserved pomba-kibana nodePort 30234 - causing helm install failure

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed
          relates to

          Task - A task that needs to be done. OOM-1174 Integrate AAF to Clamp

          • 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

          Sub-task - The sub-task of the issue SO-984 Fix 30258 nodeport conflict with clamp - use 304xx reservation

          • Highest - Catastrophic defect that causes total failure of the software or unrecoverable data loss with no available workaround. Complete shut-down of the process, nothing can proceed further. Blocks testing of the product / feature. Must be fixed in the next build.
          • Closed

          Sub-task - The sub-task of the issue OOM-1383 Add minimal automated nodeport conflict script to end of helm verify job

          • 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
          links to

          Web Link https://lists.onap.org/g/onap-discuss/topic/oom_helm_install_local_onap/25193376?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,25193376

          Wiki Page

          Wiki 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
              jmac James MacNider
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: