Bug 2015106

Summary: [DR] ODF Multicluster setup ignore already labeled node with submariner.io/gateway=true and starts new one instead
Product: Red Hat Advanced Cluster Management for Kubernetes Reporter: Elvir Kuric <ekuric>
Component: SubmarinerAssignee: Aswin Suryanarayanan <asuryana>
Status: CLOSED DEFERRED QA Contact: Eveline Cai <ecai>
Severity: unspecified Docs Contact: Christopher Dawson <cdawson>
Priority: unspecified    
Version: rhacm-2.4CC: jespy, madam, muagarwa, nyechiel, ocs-bugs, srangana
Target Milestone: ---Flags: ming: rhacm-2.4+
Target Release: rhacm-2.4   
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: 2022-03-29 10:18:13 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:
Attachments:
Description Flags
node none

Description Elvir Kuric 2021-10-18 12:14:53 UTC 
Created attachment 1834211 [details]
node

Description of problem (please be detailed as possible and provide log
snippests):
When installing ODF with support for DR/rbd mirroring  ( eg. document [1] 

https://red-hat-storage.github.io/ocs-training/training/ocs4/odf4-multisite-ramen.html#_install_acm_and_multiclusterhub 

we can label node(s) on both clusters with label

submariner.io/gateway=true 

to signalize submariner which node to use as gateway. 

However, installer will start new node and label it with "submariner.io/gateway=true" even there is already labeled node ( with public IP ) which is planned to be used as gateway. 


Version of all relevant components (if applicable):
OCP v4.8
ODF v4.9 ( latest ) 
ODF operators - Openshift DR Cluster/Hub v4.9 , and ODF Multicluster Orchestration v4.9  


Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No


Is there any workaround available to the best of your knowledge?

NA 

Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
3 


Can this issue reproducible?
Yes


Can this issue reproduce from the UI?
Yes


If this is a regression, please provide more details to justify this:


Steps to Reproduce:
1. Install OCP + ACM + ODF 
2. Label node with public ip submariner.io/gateway=true  to signalize to use that node for gateway.
3. at submariner section ( via web interface as operator installation ) install submariner and its addons. 
4. Check that new node will be added and labeled with submariner.io/gateway=true  


Actual results:
It installs one more node


Expected results:

to use node labeled with "submariner.io/gateway=true" as submariner gateway

Additional info:
Node is recognized to have submariner.io/gateway=true  label, but still new node will be added
Comment 5 Nir Yechiel 2022-03-29 10:18:13 UTC 
Closing old bugs. Please reopen if this is still relevant and can be reproduced with the latest release.