-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ACM-8232] call addonMgr.start asynchronously #1263
[ACM-8232] call addonMgr.start asynchronously #1263
Conversation
Signed-off-by: Subbarao Meduri <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm as far as I understand this.
os.Exit(1) | ||
} | ||
go func() { | ||
ctx := context.TODO() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably needs some centralized context, in the future
The lint check is fixed by #1262 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: saswatamcode, subbarao-meduri The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
The |
Fixed in #1262! Just needs to be rebased for check to pass. |
@subbarao-meduri I think we no longer need this change. stolostron/multiclusterhub-operator#1169 is enough to fix the issue. |
If we indeed don't need this, as @elgnay says, I prefer to avoid the change. 😬 |
Closing this PR, as confirmed not needed. |
A workaround suggested by @elgnay is to call
addonMgr.start()
asynchronously.Together with fix stolostron/multiclusterhub-operator#1169 should resolve the issue.
I have verified that this works in my local env.