Bug 2107907 - [Submariner] - Submariner addon version 0.13.0 unable to recognize Globalnet deployment
Summary: [Submariner] - Submariner addon version 0.13.0 unable to recognize Globalnet ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Advanced Cluster Management for Kubernetes
Classification: Red Hat
Component: Submariner
Version: rhacm-2.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Vishal Thapar
QA Contact: Noam Manos
Christopher Dawson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-17 14:31 UTC by Maxim Babushkin
Modified: 2022-10-03 20:23 UTC (History)
2 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 stolostron backlog issues 24349 0 None None None 2022-07-17 17:41:54 UTC

Description Maxim Babushkin 2022-07-17 14:31:20 UTC 
**What happened**:
ACM Hub: 2.6
Submariner: 0.13.0

With the deployment of submariner 0.13.0 with Globalnet from the acm hub 2.6, submariner addon couldn't recognize Globalnet deployment and Submariner Agent shows the following error message for the managedclusteraddon state: The submariner globalnet deployment does not exist

The actual globalnet state on the managed clusters is good.
By the subctl, globalnet state is recognized and e2e tests are passing.
Comment 6 Nir Yechiel 2022-07-19 07:21:16 UTC 
Fixed by https://github.com/stolostron/submariner-addon/pull/433
Note You need to log in before you can comment on or make changes to this bug.