Bug 2124219
| Summary: | Submariner gateway node does not get deployed after applying ManagedClusterAddOn on Openstack | ||
|---|---|---|---|
| Product: | Red Hat Advanced Cluster Management for Kubernetes | Reporter: | Rahul Lepakshi <rlepaksh> |
| Component: | Submariner | Assignee: | Aswin Suryanarayanan <asuryana> |
| Status: | CLOSED ERRATA | QA Contact: | Noam Manos <nmanos> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | rhacm-2.5 | CC: | asuryana, maafried, mdockery, nyechiel, sgaddam, skitt |
| Target Milestone: | --- | Keywords: | OtherQA |
| Target Release: | --- | Flags: | nyechiel:
rhacm-2.7+
nyechiel: rhacm-2.7.z+ rlepaksh: needinfo- rlepaksh: needinfo- |
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-02-07 17:24:38 UTC | 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: | |||
|
Comment 1
Nir Yechiel
2022-09-05 14:22:35 UTC
(In reply to Nir Yechiel from comment #1) > Sridhar, can you please clarify what needs to be fixed in the docs? > > Thanks! This looks like a bug in addon and is not a documentation issue which i was thinking initially. Changed the component back to Submariner. @rlepaksh could you try deleting only the submariner add-on pod? It should then be re-created and be able to use the secret. @rlepaksh Could you try deleting the machineset if any is created( it should have -submariner-gw in its name ) after deleting SubmarinerConfig and try creating SubmarinerConfig again. I get an error when I try to apply the SubmrinerConfig above, did you face the same? $ kubectl apply --kubeconfig kubeconfig1 -f submariner-config.yaml error: error validating "submariner-config.yaml": error validating data: ValidationError(SubmarinerConfig.spec.gatewayConfig): unknown field "rhos" in io.open-cluster-management.submarineraddon.v1alpha1.SubmarinerConfig.spec.gatewayConfig; if you choose to ignore these errors, turn validation off with --validate=false The CRD seems to be missing the field. Need to check. @asuryana No, I did not get the error you see above and I did not use kubectl commands, used openshift CLI but that should not matter. Thanks @rlepaksh We seems to have a bug in Submariner , where it always passes the default value and ignores user passed one[1]. Could you try editing the image in the machineset(the one has submariner in name) that got created as a work around, while we fix the issue? if editing does not work you can save the contents to a yaml edit the image and apply it after deleting the existing machineset [1]`https://github.com/stolostron/submariner-addon/blob/main/pkg/cloud/rhos/rhos.go#L97 @asuryana thanks. I applied workaround through saving contents to YAML as I could not see changes getting applied after machineset YAML edition from UI. oc get nodes NAME STATUS ROLES AGE VERSION ceph-c2-6x-tkg4z-master-0 Ready control-plane,master,worker 14d v1.24.0+ed93380 ceph-c2-6x-tkg4z-master-1 Ready control-plane,master,worker 14d v1.24.0+ed93380 ceph-c2-6x-tkg4z-master-2 Ready control-plane,master,worker 14d v1.24.0+ed93380 ceph-c2-6x-tkg4z-submariner-gw-0-g47g4 Ready worker 53m v1.24.0+ed93380 Removing the test blocker flag as we have a workaround. This has been fixed for ACM 2.7, and also backported to 2.6 and 2.5. 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 (Moderate: RHSA: Submariner 0.14 - bug fix and security updates), 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/RHSA-2023:0631 |