Bug 2181416
| Summary: | Can the default port for noobaa-mgmt 31054 be changed to use a different port? | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat OpenShift Data Foundation | Reporter: | Anjali <amenon> |
| Component: | documentation | Assignee: | Anjana Suparna Sriram <asriram> |
| Status: | NEW --- | QA Contact: | Neha Berry <nberry> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 4.10 | CC: | bkunal, dzaken, nbecker, odf-bz-bot, tmanor |
| Target Milestone: | --- | Flags: | bkunal:
needinfo?
(amenon) |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | Type: | Bug | |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Hello Danny and Nimrod Thank you for all the help on this bug. Can you please help out with the above query? I'll paste it below: Cu was able to change the default node port for the noobaa-mgmt service, however saw the following message when they saved the change: Managed resource This resource is managed by NooBaaNB noobaa and any modifications may be overwritten. Edit the managing resource to preserve changes. Cu is concerned the change will be reverted by the controlling object at a later date? Is it safe to go ahead and edit the managing resource to make this persistent? If yes, what is the controlling object for noobaa-mgmt that we should edit? Thanks and regards Anjali Converting to a doc bz |
Description of problem (please be detailed as possible and provide log snippests): - Cu is installing Azure Arc software and the ports being used for that are 31053 and 31054 for logs and metrics. Is it possible to change the port for noobaa-mgmt? - These ports are being used by noobaa-mgmt service as shown below: [1] noobaa-mgmt service yaml snip ~~~~ ports: - name: mgmt nodePort: 32416 port: 80 protocol: TCP targetPort: 8080 - name: mgmt-https nodePort: 31523 port: 443 protocol: TCP targetPort: 8443 - name: bg-https nodePort: 31004 port: 8445 protocol: TCP targetPort: 8445 - name: hosted-agents-https nodePort: 31054 port: 8446 protocol: TCP targetPort: 8446 ~~~ - We tried to test this in lab, but the issue is that we tried to edit the service and remove all entries for NodePort from noobaa-mgmt but the operator automatically puts them back. Version of all relevant components (if applicable): ODF Version is 4.10.5. Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? Yes Steps to Reproduce: - In lab there is no NodePort for the service noobaa-mgmt [1] backup the service in a yaml file: # oc get -o yaml svc noobaa-mgmt >backup-noobaa-mgmt-svc.yaml [2] edit the service # oc edit svc noobaa-mgmt [3] remove all lines with nodePort, for example: nodePort: 32416 - But it is automatically added back by operator. - Need help from engineering on how we can change these ports. Additional info: - We have also started a prio-list thread for the same [ODF 4.10][Case 03457767][Sev 4] is there any dependency on the specific nodePorts assigned for noobaa services