Temporary fix to let CouchDB replications go through the standard port - wmagent branch#10453
Merged
amaltaro merged 1 commit intodmwm:1.4.7_wmagentfrom Apr 19, 2021
Merged
Conversation
Contributor
Author
|
@todor-ivanov FYI |
Contributor
|
Thanks @amaltaro , I am working on the issue for figuring out what's wrong with the initial solution. |
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Temporary workaround for #10452
Status
ready
Description
Rollback changes that affect CouchDB replication, provided in this PR: #10330
Thus, keep using the standard SSL port for replication between WMAgents and central CouchDB in CMSWEB.
NOTE: pushing these changes only in the wmagent branch. A proper fix for the replication and port 8443 still need to be made against master branch.
Is it backward compatible (if not, which system it affects?)
yes
Related PRs
none
External dependencies / deployment changes
none