Description of problem (please be detailed as possible and provide log snippests): There is no option to change the configuration of "Public Network Interface" and "Cluster Network Interface" For Example: I configured the "Cluster Network Interface" with the wrong param. I cannot change the configuration and only go back to "ODF operator details" page [re-create again the storagecluster] **Attached screen record Version of all relevant components (if applicable): OCP4.13 ODF4.13 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)? 1 Can this issue reproducible? Can this issue reproduce from the UI? yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Deploy OCP 4.13 2. Install ODF 4.13 operator 3. Create NetworkAttachmentDefinition --- apiVersion: k8s.cni.cncf.io/v1 kind: NetworkAttachmentDefinition metadata: name: public-net namespace: default labels: {} annotations: {} spec: config: '{ "cniVersion": "0.3.1", "type": "macvlan", "master": "br-ex", "mode": "bridge", "ipam": { "type": "whereabouts", "range": "192.168.20.0/24" } }' --- apiVersion: k8s.cni.cncf.io/v1 kind: NetworkAttachmentDefinition metadata: name: cluster-net namespace: default labels: {} annotations: {} spec: config: '{ "cniVersion": "0.3.1", "type": "macvlan", "master": "br-ex", "ipam": { "type": "whereabouts", "range": "192.168.30.0/24" } }' 4. Create a storage cluster [via UI] 5. Enable Multus 6. Trying to change the wrong configuration of multus [Failed] **Attached screen record Actual results: There is no option to change the multus configuration after we configured the relevant params ["Public Network Interface" and "Cluster Network Interface"] Expected results: There is an option to change "Public Network Interface" and "Cluster Network Interface" configuration via UI. Additional info: attached screen record https://drive.google.com/drive/folders/1Dj6YV0VL277-sly-jNwri_8CJjU5I1Dz
The initial configuration includes the CLUSTER-NET and the PUBLIC-NET. Expecting that we will configure only one component ["Public Network Interface" or "Cluster Network Interface"] In addition, we need to find a method not to set the same NAD in "Public Network Interface" and "Cluster Network Interface". Attached screen record Setup: OCP Version: 4.13.0-0.nightly-2023-05-25-001936 ODF Version: odf-operator.v4.13.0-206.stable Platform: Vsphere
attached screen record https://drive.google.com/drive/u/0/folders/1dsmheQEbG0YlwpwTWOfGI2zMXfnMykbd
(In reply to Oded from comment #8) > The initial configuration includes the CLUSTER-NET and the PUBLIC-NET. > Expecting that we will configure only one component ["Public Network > Interface" or "Cluster Network Interface"] > > > In addition, we need to find a method not to set the same NAD in "Public > Network Interface" and "Cluster Network Interface". > Attached screen record > > > Setup: > OCP Version: 4.13.0-0.nightly-2023-05-25-001936 > ODF Version: odf-operator.v4.13.0-206.stable > Platform: Vsphere As per our discussions with PM and UX this is what we want. Because by default(internally) Cluster Network Interface will be set to what Public Network Interface is set if it's not selected. By selecting it automatically we are making this behavior apparent to users. Regarding the actual issue of not being to change the initial selection we have removed filtering altogether.
In this method, there is no option to configure cluster-net only... I must delete NAD object...
Bug Fixed: ODF Version: odf-operator.v4.13.0-207.stable OCP Version: 4.13.0-0.nightly-2023-06-01-050820 Platform: Vsphere There is an option to change public-net and cluster-net dynamically... Attached a screen record: https://drive.google.com/drive/u/0/folders/1oyhC-PDBhpdbuj2oAPerRZP24o4pVCFO
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenShift Data Foundation 4.13.0 enhancement and bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:3742