Re: [onap-discuss] [oom] helm install local/onap fails - fix for #clamp #aaf #pomba
Hi George, Unfortunately you got caught up in a nodeport conflict. Nodeports provide the mechanism for external access to ports within an ONAP deployment and management of nodeport allocation is manual which resulted in this conflict. The OOM team is looking at alternative solutions to exposing all of these ports and in the short term Michael has generously re-allocated some ports to try to resolve the issue. Unless one deploys all of ONAP a nodeport conflict may not be seen after what seems like a simple fix so extra caution is advised when changing node ports. Thanks for raising the issue. Cheers, Roger From: on behalf of George Clapp Reply-To: "onap-discuss@lists.onap.org" , "georgehcl...@gmail.com" Date: Wednesday, September 5, 2018 at 6:23 PM To: "onap-discuss@lists.onap.org" Subject: Re: [onap-discuss] [oom] helm install local/onap fails - fix for #clamp #aaf #pomba I tried to install again after another “helm delete –purge,” but there were a lot of residual components left after the failed earlier installation and then the delete. I went into an etcd container and deleted all of the related entries and tried again, but got that same error. Error: release onap failed: Service "dmaap-dr-prov" is invalid: spec.ports[0].nodePort: Invalid value: 30259: provided port is already allocated I’ll revert to Beijing for the time being. George From: onap-discuss@lists.onap.org On Behalf Of George Clapp Sent: Wednesday, September 05, 2018 12:14 PM To: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [OOM] helm install local/onap fails - fix for #clamp #aaf #pomba I tried again to do a complete installation. I checked out the master branch and did a pull to update and then entered: sudo helm delete --purge development (the name I had used) There were some residual deployments that survived the delete, most of them related to DMaaP. I deleted them manually and then upgraded helm from 2.8.2 to 2.9.1, removed and rebuilt the helm repo local, and did a ‘make all’ in oom/kubernetes. I then entered: sudo helm install local/onap -n onap --namespace onap But got this error: Error: release onap failed: Service "dmaap-dr-prov" is invalid: spec.ports[0].nodePort: Invalid value: 30259: provided port is already allocated I’m pretty sure that I had deleted all of the residual DMaaP deployments. Any suggestions? Thanks, George From: Michael O'Brien mailto:frank.obr...@amdocs.com>> Sent: Tuesday, September 04, 2018 6:32 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; gary.i...@huawei.com<mailto:gary.i...@huawei.com>; James MacNider mailto:james.macni...@amdocs.com>>; georgehcl...@gmail.com<mailto:georgehcl...@gmail.com>; sd3...@intl.att.com<mailto:sd3...@intl.att.com> Subject: RE: [onap-discuss] [OOM] helm install local/onap fails - fix for #clamp #aaf #pomba Team, AAF, CLAMP, POMBA, Integration, OOM, As James has iterated – when you add/change a nodeport – do a full helm install/upgrade of your onap deployment – with “all” pods on – not just the vFW subset where several pods are disabled via –set .enabled=false – use the default/inferred deployment with no -f override. Running a subset of onap for development, to fit in a 64g vm or to reduce the pod count is OK but when submitting run the full system if possible or at least your change with onap-minimal (the traditional vFW pods) – and then a 2nd deploy with the rest of ONAP for vCPE/vVOLTE (the parts that are normally disabled for vFW) I put a fix in for clamp where they now have nodeport 58 (previously reserved for log/logdemonode) in https://wiki.onap.org/display/DW/OOM+NodePort+List instead of the conflicted port with pomba – 34. I’ll fix my ELK/log RI container to use 304xx later – it is not part of the requirements.yaml (it only shares the namespace) – so there is no conflict there until I bring up the 2nd deployment. https://gerrit.onap.org/r/#/c/64545/ Tested and ready for merge. Some background on 63235 - as we need a 304xx nodeport - this jira is really 2 parts (logging and exposing a new port) - we failed to test the conflict with pomba because my AWS CD system was temporarily not running - after the AAF/CLAMP merge for OOM-1174 in https://gerrit.onap.org/r/#/c/63235/ https://gerrit.onap.org/r/#/c/63235/1/kubernetes/clamp/values.yaml https://git.onap.org/oom/tree/kubernetes/clamp/values.yaml#n98 reproduction: amdocs@ubuntu:~/_dev/oom/kubernetes$ sudo helm upgrade -i onap local/onap --namespace onap -f dev.yaml Error: UPGRADE FAILED: failed to create resource: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated See AAF enablement in CLAMP https://jira.onap.org/browse/OOM-1174 https://jira.onap.org/browse/OOM-1364 duped to https://jira.onap.org/browse/OOM-1366
Re: [onap-discuss] [oom] helm install local/onap fails - fix for #clamp #aaf #pomba
I tried to install again after another “helm delete –purge,” but there were a lot of residual components left after the failed earlier installation and then the delete. I went into an etcd container and deleted all of the related entries and tried again, but got that same error. Error: release onap failed: Service "dmaap-dr-prov" is invalid: spec.ports[0].nodePort: Invalid value: 30259: provided port is already allocated I’ll revert to Beijing for the time being. George From: onap-discuss@lists.onap.org On Behalf Of George Clapp Sent: Wednesday, September 05, 2018 12:14 PM To: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] [OOM] helm install local/onap fails - fix for #clamp #aaf #pomba I tried again to do a complete installation. I checked out the master branch and did a pull to update and then entered: sudo helm delete --purge development (the name I had used) There were some residual deployments that survived the delete, most of them related to DMaaP. I deleted them manually and then upgraded helm from 2.8.2 to 2.9.1, removed and rebuilt the helm repo local, and did a ‘make all’ in oom/kubernetes. I then entered: sudo helm install local/onap -n onap --namespace onap But got this error: Error: release onap failed: Service "dmaap-dr-prov" is invalid: spec.ports[0].nodePort: Invalid value: 30259: provided port is already allocated I’m pretty sure that I had deleted all of the residual DMaaP deployments. Any suggestions? Thanks, George From: Michael O'Brien mailto:frank.obr...@amdocs.com> > Sent: Tuesday, September 04, 2018 6:32 PM To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> ; gary.i...@huawei.com <mailto:gary.i...@huawei.com> ; James MacNider mailto:james.macni...@amdocs.com> >; georgehcl...@gmail.com <mailto:georgehcl...@gmail.com> ; sd3...@intl.att.com <mailto:sd3...@intl.att.com> Subject: RE: [onap-discuss] [OOM] helm install local/onap fails - fix for #clamp #aaf #pomba Team, AAF, CLAMP, POMBA, Integration, OOM, As James has iterated – when you add/change a nodeport – do a full helm install/upgrade of your onap deployment – with “all” pods on – not just the vFW subset where several pods are disabled via –set .enabled=false – use the default/inferred deployment with no -f override. Running a subset of onap for development, to fit in a 64g vm or to reduce the pod count is OK but when submitting run the full system if possible or at least your change with onap-minimal (the traditional vFW pods) – and then a 2nd deploy with the rest of ONAP for vCPE/vVOLTE (the parts that are normally disabled for vFW) I put a fix in for clamp where they now have nodeport 58 (previously reserved for log/logdemonode) in https://wiki.onap.org/display/DW/OOM+NodePort+List instead of the conflicted port with pomba – 34. I’ll fix my ELK/log RI container to use 304xx later – it is not part of the requirements.yaml (it only shares the namespace) – so there is no conflict there until I bring up the 2nd deployment. https://gerrit.onap.org/r/#/c/64545/ Tested and ready for merge. Some background on 63235 - as we need a 304xx nodeport - this jira is really 2 parts (logging and exposing a new port) - we failed to test the conflict with pomba because my AWS CD system was temporarily not running - after the AAF/CLAMP merge for OOM-1174 in https://gerrit.onap.org/r/#/c/63235/ https://gerrit.onap.org/r/#/c/63235/1/kubernetes/clamp/values.yaml https://git.onap.org/oom/tree/kubernetes/clamp/values.yaml#n98 reproduction: amdocs@ubuntu:~/_dev/oom/kubernetes$ sudo helm upgrade -i onap local/onap --namespace onap -f dev.yaml Error: UPGRADE FAILED: failed to create resource: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated See AAF enablement in CLAMP https://jira.onap.org/browse/OOM-1174 https://jira.onap.org/browse/OOM-1364 duped to https://jira.onap.org/browse/OOM-1366 To speed this up - and not have to goto 304/306xx - Giving aaf/clamp my last 302 - 30258 https://git.onap.org/logging-analytics/tree/reference/logging-kubernetes/logdemonode/charts/logdemonode/values.yaml#n76 That I was using for the logging RI container (reserved on july 26) - I will use a 304xx port for logging instead https://wiki.onap.org/pages/viewpage.action?pageId=38112900 adjusting page https://wiki.onap.org/display/DW/OOM+NodePort+List Also note that for any hanging PV or secret when using Helm 2.9.1 under Kubernetes 1.10.x (via Rancher 1.6.18) use the following https://wiki.onap.org/display/DW/Logging+Developer+Guide#LoggingDeveloperGuide-Deployingdemopod normal bounding of a pod /oom/kubernetes$ sudo helm install local/onap -n onap --namespace onap -f onap/resources/environments/disable-allcharts.yaml --set l
Re: [onap-discuss] [OOM] helm install local/onap fails - fix for #clamp #aaf #pomba
I tried again to do a complete installation. I checked out the master branch and did a pull to update and then entered: sudo helm delete --purge development (the name I had used) There were some residual deployments that survived the delete, most of them related to DMaaP. I deleted them manually and then upgraded helm from 2.8.2 to 2.9.1, removed and rebuilt the helm repo local, and did a ‘make all’ in oom/kubernetes. I then entered: sudo helm install local/onap -n onap --namespace onap But got this error: Error: release onap failed: Service "dmaap-dr-prov" is invalid: spec.ports[0].nodePort: Invalid value: 30259: provided port is already allocated I’m pretty sure that I had deleted all of the residual DMaaP deployments. Any suggestions? Thanks, George From: Michael O'Brien Sent: Tuesday, September 04, 2018 6:32 PM To: onap-discuss@lists.onap.org; gary.i...@huawei.com; James MacNider ; georgehcl...@gmail.com; sd3...@intl.att.com Subject: RE: [onap-discuss] [OOM] helm install local/onap fails - fix for #clamp #aaf #pomba Team, AAF, CLAMP, POMBA, Integration, OOM, As James has iterated – when you add/change a nodeport – do a full helm install/upgrade of your onap deployment – with “all” pods on – not just the vFW subset where several pods are disabled via –set .enabled=false – use the default/inferred deployment with no -f override. Running a subset of onap for development, to fit in a 64g vm or to reduce the pod count is OK but when submitting run the full system if possible or at least your change with onap-minimal (the traditional vFW pods) – and then a 2nd deploy with the rest of ONAP for vCPE/vVOLTE (the parts that are normally disabled for vFW) I put a fix in for clamp where they now have nodeport 58 (previously reserved for log/logdemonode) in https://wiki.onap.org/display/DW/OOM+NodePort+List instead of the conflicted port with pomba – 34. I’ll fix my ELK/log RI container to use 304xx later – it is not part of the requirements.yaml (it only shares the namespace) – so there is no conflict there until I bring up the 2nd deployment. https://gerrit.onap.org/r/#/c/64545/ Tested and ready for merge. Some background on 63235 - as we need a 304xx nodeport - this jira is really 2 parts (logging and exposing a new port) - we failed to test the conflict with pomba because my AWS CD system was temporarily not running - after the AAF/CLAMP merge for OOM-1174 in https://gerrit.onap.org/r/#/c/63235/ https://gerrit.onap.org/r/#/c/63235/1/kubernetes/clamp/values.yaml https://git.onap.org/oom/tree/kubernetes/clamp/values.yaml#n98 reproduction: amdocs@ubuntu:~/_dev/oom/kubernetes$ sudo helm upgrade -i onap local/onap --namespace onap -f dev.yaml Error: UPGRADE FAILED: failed to create resource: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated See AAF enablement in CLAMP https://jira.onap.org/browse/OOM-1174 https://jira.onap.org/browse/OOM-1364 duped to https://jira.onap.org/browse/OOM-1366 To speed this up - and not have to goto 304/306xx - Giving aaf/clamp my last 302 - 30258 https://git.onap.org/logging-analytics/tree/reference/logging-kubernetes/logdemonode/charts/logdemonode/values.yaml#n76 That I was using for the logging RI container (reserved on july 26) - I will use a 304xx port for logging instead https://wiki.onap.org/pages/viewpage.action?pageId=38112900 adjusting page https://wiki.onap.org/display/DW/OOM+NodePort+List Also note that for any hanging PV or secret when using Helm 2.9.1 under Kubernetes 1.10.x (via Rancher 1.6.18) use the following https://wiki.onap.org/display/DW/Logging+Developer+Guide#LoggingDeveloperGuide-Deployingdemopod normal bounding of a pod /oom/kubernetes$ sudo helm install local/onap -n onap --namespace onap -f onap/resources/environments/disable-allcharts.yaml --set log.enabled=false /oom/kubernetes$ sudo helm upgrade -i onap local/onap --namespace onap -f onap/resources/environments/disable-allcharts.yaml --set log.enabled=true Mitigation commands to completely clean the system sudo helm delete --purge onap kubectl delete namespace onap tested https://wiki.onap.org/display/DW/OOM+NodePort+List#OOMNodePortList-VerifyNoPortConflictsduringfullONAPHelmDeploy sudo helm delete --purge onap kubectl delete namespace onap sudo make all sudo helm install local/onap -n onap --namespace onap -f dev.yaml amdocs@ubuntu:~/_dev/oom/kubernetes$ kubectl get services --all-namespaces NAMESPACE NAME TYPECLUSTER-IP EXTERNAL-IP PORT(S) AGE default kubernetes ClusterIP 10.43.0.1 443/TCP 29d kube-system heapster ClusterIP 10.43.42.68 80/TCP
Re: [onap-discuss] [OOM] helm install local/onap fails - fix for #clamp #aaf #pomba
NodePort10.43.56.153 9520:30268/TCP 27s onap aai-elasticsearch ClusterIP None 9200/TCP27s onap aai-modelloaderNodePort10.43.148.57 8080:30210/TCP,8443:30229/TCP 27s onap aai-resources ClusterIP None 8447/TCP,5005/TCP 27s onap aai-search-dataClusterIP None 9509/TCP27s onap aai-sparky-be NodePort10.43.204.78 9517:30220/TCP 27s onap aai-traversal ClusterIP None 8446/TCP,5005/TCP 27s onap cdash-es ClusterIP 10.43.159.150 9200/TCP27s onap cdash-es-tcp ClusterIP 10.43.80.11 9300/TCP27s onap cdash-kibana NodePort10.43.188.64 5601:30290/TCP 27s onap cdash-ls ClusterIP 10.43.37.108 9600/TCP27s onap clamp NodePort10.43.199.87 8080:30295/TCP,8443:30258/TCP 27s onap clampdbClusterIP 10.43.117.156 3306/TCP27s onap log-es NodePort10.43.123.176 9200:30254/TCP 27s onap log-es-tcp ClusterIP 10.43.204.70 9300/TCP27s onap log-kibana NodePort10.43.138.201 5601:30253/TCP 27s onap log-ls NodePort10.43.184.100 5044:30255/TCP 26s onap log-ls-httpClusterIP 10.43.166.10 9600/TCP27s onap pomba-aaictxbuilderClusterIP 10.43.114.84 9530/TCP26s onap pomba-data-router NodePort10.43.150.81 9502:30249/TCP 26s onap pomba-es ClusterIP 10.43.44.189 9200/TCP26s onap pomba-es-tcp ClusterIP 10.43.16.122 9300/TCP26s onap pomba-kibana NodePort10.43.74.233 5601:30234/TCP 26s onap pomba-networkdiscovery ClusterIP 10.43.217.33 9531/TCP26s onap pomba-networkdiscoveryctxbuilder ClusterIP 10.43.136.187 9530/TCP26s onap pomba-sdcctxbuilderClusterIP 10.43.54.138 9530/TCP26s onap pomba-search-data ClusterIP 10.43.141.203 9509/TCP26s onap pomba-servicedecomposition ClusterIP 10.43.208.23 9532/TCP26s onap pomba-validation-service ClusterIP 10.43.163.9 9529/TCP26s onap robot NodePort10.43.158.247 88:30209/TCP26s /michael From: onap-discuss@lists.onap.org On Behalf Of Gary Wu Sent: Tuesday, September 4, 2018 3:36 PM To: onap-discuss@lists.onap.org; James MacNider ; georgehcl...@gmail.com; sd3...@intl.att.com Subject: Re: [onap-discuss] [OOM] helm install local/onap fails I logged a Jira ticket on this issue a few days ago: https://jira.onap.org/browse/OOM-1364 Thanks, Gary From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> [mailto:onap-discuss@lists.onap.org] On Behalf Of James MacNider Sent: Tuesday, September 04, 2018 5:23 AM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; georgehcl...@gmail.com<mailto:georgehcl...@gmail.com>; sd3...@intl.att.com<mailto:sd3...@intl.att.com> Subject: Re: [onap-discuss] [OOM] helm install local/onap fails Hi George, After a bit of digging, it looks like a recent merge in the Clamp helm chart (https://gerrit.onap.org/r/#/c/63235) has created a nodePort conflict with Pomba. Until this is resolved, the workaround is to disable one of them if don’t require both components. As a reminder to all, when adding new nodePorts to charts, ensure that they are properly reserved and unique: https://wiki.onap.org/display/DW/OOM+NodePort+List Thanks, James From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org&g
Re: [onap-discuss] [OOM] helm install local/onap fails
I logged a Jira ticket on this issue a few days ago: https://jira.onap.org/browse/OOM-1364 Thanks, Gary From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of James MacNider Sent: Tuesday, September 04, 2018 5:23 AM To: onap-discuss@lists.onap.org; georgehcl...@gmail.com; sd3...@intl.att.com Subject: Re: [onap-discuss] [OOM] helm install local/onap fails Hi George, After a bit of digging, it looks like a recent merge in the Clamp helm chart (https://gerrit.onap.org/r/#/c/63235) has created a nodePort conflict with Pomba. Until this is resolved, the workaround is to disable one of them if don’t require both components. As a reminder to all, when adding new nodePorts to charts, ensure that they are properly reserved and unique: https://wiki.onap.org/display/DW/OOM+NodePort+List Thanks, James From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org>> On Behalf Of George Clapp Sent: Monday, September 3, 2018 7:31 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [OOM] helm install local/onap fails I am attempting for the first time to install ONAP using the instructions at “ONAP on Kubernetes with Rancher” and “OOM User Guide” in an OpenStack environment. I got to the point of the command: helm install local/onap --name development And got these error messages: % helm install local/onap --name development Error: release development failed: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated % helm install local/onap --name development Error: release development failed: secrets "development-aaf-cs" already exists I searched but nothing came up about this error. I would greatly appreciate any suggestions. Thanks, George “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12233): https://lists.onap.org/g/onap-discuss/message/12233 Mute This Topic: https://lists.onap.org/mt/25172114/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] helm install local/onap fails
I removed the failed “helm install” with the command: helm delete --purge development And tried again, and it worked! 411 containers and counting. Thanks, George From: FREEMAN, BRIAN D Sent: Tuesday, September 04, 2018 9:55 AM To: onap-discuss@lists.onap.org; georgehcl...@gmail.com Subject: RE: [onap-discuss] [OOM] helm install local/onap fails Thats probably a problem with cleaning up keys. Also dont do a full onap install. –set enabled=false for a few components if you can. https://wiki.onap.org/pages/viewpage.action?pageId=29787124 scroll down to the section on the reduced size install: helm upgrade -i dev local/onap --namespace onap -f /root/integration-override.yaml --set log.enabled=false --set clamp.enabled=false --set pomba.enabled=false --set vnfsdk.enabled=false From: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org> > On Behalf Of George Clapp Sent: Tuesday, September 04, 2018 12:53 PM To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> Subject: Re: [onap-discuss] [OOM] helm install local/onap fails James, Thanks for taking the time. I was working with the master branch of OOM, so I checked out Beijing and tried again. The port conflict didn’t happen, but I got the same error message about “development-aaf-cs.” Error: release development failed: secrets "development-aaf-cs" already exists This was after an earlier attempt that had failed because I was using a later version of helm (2.9.1 rather than 2.8.2). I installed helm 2.8.2 and tried again and got this error. Any suggestions? George From: James MacNider mailto:james.macni...@amdocs.com> > Sent: Tuesday, September 04, 2018 5:23 AM To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> ; georgehcl...@gmail.com <mailto:georgehcl...@gmail.com> ; sd3...@intl.att.com <mailto:sd3...@intl.att.com> Subject: RE: [onap-discuss] [OOM] helm install local/onap fails Hi George, After a bit of digging, it looks like a recent merge in the Clamp helm chart (https://gerrit.onap.org/r/#/c/63235 <https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_-23_c_63235=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XWiIVP8LK6lYakx4CVz0RLhMux7jMLrvVkLGYpBzPp4=hZowjw7k9jTU24zwZQjfuC30VwOjW9xE-8UMiZ8ckWQ=> ) has created a nodePort conflict with Pomba. Until this is resolved, the workaround is to disable one of them if don’t require both components. As a reminder to all, when adding new nodePorts to charts, ensure that they are properly reserved and unique: https://wiki.onap.org/display/DW/OOM+NodePort+List <https://urldefense.proofpoint.com/v2/url?u=https-3A__wiki.onap.org_display_DW_OOM-2BNodePort-2BList=DwMFaQ=LFYZ-o9_HUMeMTSQicvjIg=e3d1ehx3DI5AoMgDmi2Fzw=XWiIVP8LK6lYakx4CVz0RLhMux7jMLrvVkLGYpBzPp4=v4Sn3cNN9oOhOtp1H3LPS61mPhpcQSSyUgqSy-kiXN8=> Thanks, James From: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org> > On Behalf Of George Clapp Sent: Monday, September 3, 2018 7:31 PM To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [OOM] helm install local/onap fails I am attempting for the first time to install ONAP using the instructions at “ONAP on Kubernetes with Rancher” and “OOM User Guide” in an OpenStack environment. I got to the point of the command: helm install local/onap --name development And got these error messages: % helm install local/onap --name development Error: release development failed: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated % helm install local/onap --name development Error: release development failed: secrets "development-aaf-cs" already exists I searched but nothing came up about this error. I would greatly appreciate any suggestions. Thanks, George “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12228): https://lists.onap.org/g/onap-discuss/message/12228 Mute This Topic: https://lists.onap.org/mt/25172114/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] helm install local/onap fails
James, Thanks for taking the time. I was working with the master branch of OOM, so I checked out Beijing and tried again. The port conflict didn’t happen, but I got the same error message about “development-aaf-cs.” Error: release development failed: secrets "development-aaf-cs" already exists This was after an earlier attempt that had failed because I was using a later version of helm (2.9.1 rather than 2.8.2). I installed helm 2.8.2 and tried again and got this error. Any suggestions? George From: James MacNider Sent: Tuesday, September 04, 2018 5:23 AM To: onap-discuss@lists.onap.org; georgehcl...@gmail.com; sd3...@intl.att.com Subject: RE: [onap-discuss] [OOM] helm install local/onap fails Hi George, After a bit of digging, it looks like a recent merge in the Clamp helm chart (https://gerrit.onap.org/r/#/c/63235) has created a nodePort conflict with Pomba. Until this is resolved, the workaround is to disable one of them if don’t require both components. As a reminder to all, when adding new nodePorts to charts, ensure that they are properly reserved and unique: https://wiki.onap.org/display/DW/OOM+NodePort+List Thanks, James From: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org> > On Behalf Of George Clapp Sent: Monday, September 3, 2018 7:31 PM To: onap-discuss@lists.onap.org <mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [OOM] helm install local/onap fails I am attempting for the first time to install ONAP using the instructions at “ONAP on Kubernetes with Rancher” and “OOM User Guide” in an OpenStack environment. I got to the point of the command: helm install local/onap --name development And got these error messages: % helm install local/onap --name development Error: release development failed: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated % helm install local/onap --name development Error: release development failed: secrets "development-aaf-cs" already exists I searched but nothing came up about this error. I would greatly appreciate any suggestions. Thanks, George “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12225): https://lists.onap.org/g/onap-discuss/message/12225 Mute This Topic: https://lists.onap.org/mt/25172114/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] [OOM] helm install local/onap fails
Hi George, After a bit of digging, it looks like a recent merge in the Clamp helm chart (https://gerrit.onap.org/r/#/c/63235) has created a nodePort conflict with Pomba. Until this is resolved, the workaround is to disable one of them if don't require both components. As a reminder to all, when adding new nodePorts to charts, ensure that they are properly reserved and unique: https://wiki.onap.org/display/DW/OOM+NodePort+List Thanks, James From: onap-discuss@lists.onap.org On Behalf Of George Clapp Sent: Monday, September 3, 2018 7:31 PM To: onap-discuss@lists.onap.org Subject: [onap-discuss] [OOM] helm install local/onap fails I am attempting for the first time to install ONAP using the instructions at "ONAP on Kubernetes with Rancher" and "OOM User Guide" in an OpenStack environment. I got to the point of the command: helm install local/onap --name development And got these error messages: % helm install local/onap --name development Error: release development failed: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated % helm install local/onap --name development Error: release development failed: secrets "development-aaf-cs" already exists I searched but nothing came up about this error. I would greatly appreciate any suggestions. Thanks, George “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will be processed and stored using such system and are accessible by third party providers of such system on a limited basis. Your sending of emails to Amdocs evidences your consent to the use of such system and such processing, storing and access”. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12215): https://lists.onap.org/g/onap-discuss/message/12215 Mute This Topic: https://lists.onap.org/mt/25172114/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[onap-discuss] [OOM] helm install local/onap fails
I am attempting for the first time to install ONAP using the instructions at "ONAP on Kubernetes with Rancher" and "OOM User Guide" in an OpenStack environment. I got to the point of the command: helm install local/onap --name development And got these error messages: % helm install local/onap --name development Error: release development failed: Service "pomba-kibana" is invalid: spec.ports[0].nodePort: Invalid value: 30234: provided port is already allocated % helm install local/onap --name development Error: release development failed: secrets "development-aaf-cs" already exists I searched but nothing came up about this error. I would greatly appreciate any suggestions. Thanks, George -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12209): https://lists.onap.org/g/onap-discuss/message/12209 Mute This Topic: https://lists.onap.org/mt/25172114/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
