Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

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

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

Environment

None

Activity

Show:

Former user March 13, 2019 at 2:01 PM
Edited

- Agree to Donald's comment, there should not be any conflict. Although we could remove the mirrorNodePort: 88 from dcae-pnda-bootstrap/values.yaml to avoid confusion.  The priority of this can be lowered.

Former user March 13, 2019 at 12:58 AM

() - Is there a current status on this high priority bug. Can it be closed based per comments from 1 week ago?

Former user March 6, 2019 at 3:25 PM

() - Can this item be closed per update from Donald?

Former user March 5, 2019 at 4:38 PM

Just taken a look at this and I don't think there is any issue, other than a spurious unused setting in values.yaml.

dcae-pnda-mirror is configured to use 30400 as its nodeport in https://git.onap.org/oom/tree/kubernetes/pnda/charts/dcae-pnda-mirror/values.yaml

dcae-pnda-bootstrap then dynamically looks up the mirror nodeport so the settings in dcae-pnda-bootstrap values.yaml are not used.

Former user March 5, 2019 at 1:50 PM

Good morning , - Is there any progress on this item?

Done

Details

Assignee

Reporter

Labels

Sprint

Fix versions

Affects versions

Priority

Created December 3, 2018 at 5:31 AM
Updated August 12, 2023 at 4:10 AM
Resolved April 9, 2019 at 5:13 PM