Uploaded image for project: 'Service Orchestrator'
  1. Service Orchestrator
  2. SO-707 Merge the ATT 1806 code to the main branch after testing and validation
  3. SO-984

Fix 30258 nodeport conflict with clamp - use 304xx reservation

    XMLWordPrintable

Details

    • Sub-task
    • Status: Closed
    • Highest
    • Resolution: Done
    • None
    • Casablanca Release
    • Casablanca SO Sprint 0, Casablanca SO Sprint 2

    Description

      Team,
      the 30258 port was reserved for logdemonode (another release but same onap namespace) on the wiki
      yesterday it was given to clamp because they also used the port for one of their containers
      going forward you will need to reserve a port before taking it - and doing the usual full onap deployment to check for conflicts - which it looks like you did but had a timing conflict with the clamp merge

      https://gerrit.onap.org/r/#/c/59757/15/kubernetes/so/values.yaml
      nodePort: 58
      same as
      https://git.onap.org/oom/tree/kubernetes/clamp/values.yaml#n101

      reproduction: 20180906:12000

      make[1]: Leaving directory '/home/ubuntu/oom/kubernetes'
Error: release onap failed: Service "so" is invalid: spec.ports[0].nodePort: Invalid value: 30258: provided port is already allocated

      Attachments

        Issue Links

          blocks

          Task - A task that needs to be done. INT-717 Update vCPE test scripts for Casablanca

          • 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 duplicated by

          Sub-task - The sub-task of the issue SO-983 blocking nodeport conflict with clamp reported

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

          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

          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

          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

          Bug - A problem which impairs or prevents the functions of the product. OOM-1366 NodePort conflict between Clamp and Pomba

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

          Bug - A problem which impairs or prevents the functions of the product. USECASEUI-149 UUI oom nodeport prefix 303 instead of 302?

          • 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
          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              mkhinda Mandeep Khinda
              michaelobrien Michael O'Brien
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: