Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-11043

[2.9.4] Submariner 0.17 Installation is failing using OCP4.15 & ACM 2.10 on VMware

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • ACM 2.10.0
    • None
    • Submariner Sprint 2024-21, Submariner Sprint 2024-22, Submariner Sprint 2024-23, Submariner Sprint 2024-24
    • No

      Description of problem:

      Submariner 0.17 Installation is failing using OCP4.15 & ACM 2.10 on VMware

      Version-Release number of selected component (if applicable):

      OCP 4.15.3
      ACM 2.10.0
      Submariner 0.17.0

      How reproducible:

      100%

      Steps to Reproduce:

      1. Install ACM 2.10 on hub cluster on OCP4.15+VMware and import 2 OCP4.15+VMware  managed cluster on VMware
      2. Create new ClusterSet with 2 managed clusters
      3. Using ACM submariner addon UI install submariner

      Actual result:

      Only the submariner-addon pod is created in the submariner-operator project on managed clusters.

      Expected results:

      All submariner pods are created in the submariner-operator project on managed clusters and ACM submariner UI shows Healthy status.

      Additional info:

      Hub addon for submariner messages show missing secret perf2 and perf3:

      I0321 00:58:13.624959 1 event.go:364] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"open-cluster-management", Name:"submariner-addon", UID:"f8eb4929-452d-4ad0-8bf8-cbcb8bf80f7c", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'RoleBindingCreated' Created RoleBinding.rbac.authorization.k8s.io/submariner-k8s-broker-cluster-perf3 -n submariner-broker because it was missing 2024-03-21T00:58:13.634Z INF ..agent/controller.go:705 ..nerAgentController Globalnet is disabled in the managedClusterSet namespace "submariner-broker"

      I0321 00:58:13.669816 1 event.go:364] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"open-cluster-management", Name:"submariner-addon", UID:"f8eb4929-452d-4ad0-8bf8-cbcb8bf80f7c", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'BrokerConfigApplied' Configuration applied from brokers.submariner.io object in "submariner-broker" namespace

      E0321 00:58:13.698843 1 base_controller.go:266] "SubmarinerAgentController" controller failed to sync "perf3", err: failed to create submariner brokerInfo of cluster perf3 : secrets "perf3" not found I0321 00:58:14.069685 1 event.go:364] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"open-cluster-management", Name:"submariner-addon", UID:"f8eb4929-452d-4ad0-8bf8-cbcb8bf80f7c", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Normal' reason: 'BrokerConfigApplied' Configuration applied from brokers.submariner.io object in "submariner-broker" namespace

      E0321 00:58:14.099083 1 base_controller.go:266] "SubmarinerAgentController" controller failed to sync "perf2", err: failed to create submariner brokerInfo of cluster perf2 : secrets "perf2" not found

      E0321 00:58:14.471103 1 base_controller.go:266] "SubmarinerAgentController" controller failed to sync "perf3", err: failed to create submariner brokerInfo of cluster perf3 : secrets "perf3" not found

              rh-ee-vthapar Vishal Thapar
              aclewett Annette Clewett
              Maxim Babushkin Maxim Babushkin
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: