Open issues

Syncthing stops sync the cluster_statuses folder after the DB is down
CY-2269
cfy profiles use fail on sys test 'test_restore_snapshot_and_agents_upgrade_multitenant'
CY-2250
sys test - test_ssl - failed connecting to the manager
CY-2249
Cluster status widget does not display data in container all-in-one
CY-2242
db & broker node installation should require patch to be installed
CY-2223
Snapshot system tests fail after changes in profile
CY-2211
Component's extend topology button in stage does not show
CY-2195
External label placement not optimal in Cluster Status module in UI
CY-2185
System status icon not up to date in UI
CY-2184
When running cloudifyplatform/premium-cloudify-manager-aio container along with other container the cluster status shows failure
CY-2183
Links in help menu
CY-2168
when syncthing connection check fails - problem for the cluster LB to determine whether to send traffic to a manager
CY-2154
Status reporter update request fails slow
CY-2153
Send Cancel Task Operation Failed With KeyError for Rabbitmq UserName
CY-2141
General performance degradation on large managers
CY-2119
Timeout waiting for deployment environment creation
CY-2107
DB cluster initialisation can leave async node offline
CY-2105
`cfy logs download --all-nodes` not working
CY-2101
cfy_manager - does not configure ca path for the status reporter
CY-2066
Manager status reporter user fails snapshot restore
CY-2062
Blueprint examples in Blueprints Catalog widget not up to date
CY-2053
Updating a deployment with runtime-only-evaluation renders the values
CY-2049
Error when removing a RabbitMQ cluster node
CY-2012
Make standby site not be able to become sync replica
CY-1998
Upgrade from 4.6 to 5.0.5 cluster is not working
CY-1934
Make patchify able to work with 5.0.5
CY-1873
Syncthing unable to replicate all of stage/composer files
CY-1859
bump version - does not find all possible places to update
CY-1743
Large snapshot restore failure on Clustered Postgres DB
CY-2252
Custom workflow fails when using the node name as input
CY-1995
Operational testing - Patchify over cluster
CY-1964
Operational testing - Patchify over single box
CY-1963
HA testing - Database high availability
CY-1961
Upgrade testing - 4.6 to 5.0.5
CY-1954
When joining a cluster, replicate config files instead of creating them
CY-1870
Installation of the Cloudify CLI EXE on Windows 10 fails
CY-1753
Composer | plugins section | when uploading the utilities plugin it adds 11 identical rows.
CY-1678
Clicking on currently-active panel results in weird lag
CY-956
Improve UI patch delivery procedure
CY-2238
Optimize Deployments widget data fetching
CY-2237
Start tracking user activity in UI
CY-2236
Add detailed information about node instance status in task graph
CY-2235
Improve task graphs presentation
CY-2234
Cluster system tests fail after changes in profile
CY-2210
Secret import | unhandled collision in case of global visibility
CY-2051
Document geo-replication
CY-2008
Starting a clustered DB still attempts to run non-clustered postgres
CY-1987
Spire testing - Spire manager over Openstack
CY-1972
Installation testing - Single box (all-in-one) manager over openstack as an rpm - CentOS
CY-1948
The context passed in the node operations during a deployment update contains wrong information
CY-1863
issue 1 of 662

Syncthing stops sync the cluster_statuses folder after the DB is down

Description

First, we have a healthy cluster running.
I stop the patroni service on 2 of the DB nodes to simulate DB cluster failure.
Then I start the patroni service on those 2 DB nodes so the DB cluster will be healthy again.
The problem is that now the Syncthing service stops syncing the cluster_statuses folder after the DB is down.
The cluster_statuses folder includes that status report files of all the nodes and should be sync among the managers.
It cause weird behaviour of the GET cluster-status endpoint.

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------

Steps to reproduce:
------------------
1.
2.
3.

Expected result:
---------------

Actual result:
-------------

Why Propose Close?

None

Assignee

Inbal Amrani

Reporter

Inbal Amrani

Labels

None

Severity

Medium

Target Version

5.0.5

Premium Only

yes

Found In Version

5.0

QA Owner

None

Bug Type

new feature bug

Customer Encountered

No

Customer Name

None

Release Notes

no

Priority

None

Priority

Blocker
Configure