Bug 2110237 - [Submariner] - Deployment of 0.12.2 does not create gateway nodes
Summary: [Submariner] - Deployment of 0.12.2 does not create gateway nodes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Submariner
Version: rhacm-2.5.z
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
: ---
Assignee: Mike Kolesnik
QA Contact: Noam Manos
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-24 19:14 UTC by Maxim Babushkin
Modified: 2022-10-03 20:23 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-03 20:23:57 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github https://github.com/stolostron submariner-addon pull 456 0 None None None 2022-07-26 16:59:06 UTC
Github stolostron backlog issues 24502 0 None None None 2022-07-24 21:30:44 UTC

Description Maxim Babushkin 2022-07-24 19:14:14 UTC
**What happened**:
ACM Hub: 2.5.2
Submariner: 0.12.2

During the deployment of submariner on AWS and GCP platforms, no gateway nodes were created on both of the platforms.

Output of the ManagedClusterAddon:
  conditions:
  - lastTransitionTime: "2022-07-24T17:57:14Z"
    message: manifest of addon applied successfully
    reason: AddonManifestApplied
    status: "True"
    type: ManifestApplied
  - lastTransitionTime: "2022-07-24T17:57:15Z"
    message: Registration of the addon agent is configured
    reason: RegistrationConfigured
    status: "True"
    type: RegistrationApplied
  - lastTransitionTime: "2022-07-24T17:57:18Z"
    message: ""
    reason: BrokerConfigApplied
    status: "True"
    type: SubmarinerBrokerConfigApplied
  - lastTransitionTime: "2022-07-24T17:57:24Z"
    message: There are no nodes to run the gateways
    reason: NoScheduledGateways
    status: "True"
    type: SubmarinerAgentDegraded
  - lastTransitionTime: "2022-07-24T17:57:24Z"
    message: There are no nodes with label "submariner.io/gateway"
    reason: SubmarinerGatewayNodesUnlabeled
    status: "False"
    type: SubmarinerGatewayNodesLabeled
  - lastTransitionTime: "2022-07-24T17:57:27Z"
    message: submariner add-on is available.
    reason: ManagedClusterAddOnLeaseUpdated
    status: "True"
    type: Available
  - lastTransitionTime: "2022-07-24T17:59:13Z"
    message: There are no connections on gateways
    reason: ConnectionsNotEstablished
    status: "True"
    type: SubmarinerConnectionDegraded


I didn't find any meaningful error logs on the addon pods for both hub and managed clusters.

Found this log error on the hub addon pod:
0724 12:52:55.079755       1 reflector.go:138] k8s.io/client-go.0+incompatible/tools/cache/reflector.go:167: Failed to watch *v1.ManagedCluster: failed to list *v1.ManagedCluster: the server could not find the requested resource (get managedclusters.cluster.open-cluster-management.io)
E0724 12:52:55.340159       1 reflector.go:138] k8s.io/client-go.0+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.ManagedClusterAddOn: failed to list *v1alpha1.ManagedClusterAddOn: the server could not find the requested resource (get managedclusteraddons.addon.open-cluster-management.io)
E0724 12:52:55.415860       1 reflector.go:138] k8s.io/client-go.0+incompatible/tools/cache/reflector.go:167: Failed to watch *v1.ManagedCluster: failed to list *v1.ManagedCluster: the server could not find the requested resource (get managedclusters.cluster.open-cluster-management.io)
E0724 12:52:55.420543       1 reflector.go:138] k8s.io/client-go.0+incompatible/tools/cache/reflector.go:167: Failed to watch *v1alpha1.ClusterManagementAddOn: failed to list *v1alpha1.ClusterManagementAddOn: the server could not find the requested resource (get clustermanagementaddons.addon.open-cluster-management.io)
E0724 12:52:55.443018       1 reflector.go:138] k8s.io/client-go.0+incompatible/tools/cache/reflector.go:167: Failed to watch *v1beta1.ManagedClusterSet: failed to list *v1beta1.ManagedClusterSet: the server could not find the requested resource (get managedclustersets.cluster.open-cluster-management.io)
E0724 12:52:55.584961       1 reflector.go:138] k8s.io/client-go.0+incompatible/tools/cache/reflector.go:167: Failed to watch *v1.ManifestWork: failed to list *v1.ManifestWork: the server could not find the requested resource (get manifestworks.work.open-cluster-management.io)
E0724 12:52:55.695632       1 reflector.go:138] k8s.io/client-go.0+incompatible/tools/cache/reflector.go:167: Failed to watch *v1.ManifestWork: failed to list *v1.ManifestWork: the server could not find the requested resource (get manifestworks.work.open-cluster-management.io)


Environment logs attached.

Comment 2 Mike Kolesnik 2022-07-25 08:25:39 UTC
Please attach all relevant logs (hub + spoke addon logs)

Comment 3 Maxim Babushkin 2022-07-25 09:31:43 UTC
Mike,

All the logs already attached as an archive file.

Comment 5 Maxim Babushkin 2022-07-28 10:47:53 UTC
The working state has been verified on the last downstream build.


Note You need to log in before you can comment on or make changes to this bug.