[MXS-4220] config_sync sometimes fails on startup Created: 2022-07-27  Updated: 2022-09-13  Resolved: 2022-09-13

Status: Closed
Project: MariaDB MaxScale
Component/s: test
Affects Version/s: None
Fix Version/s: N/A

Type: Task Priority: Major
Reporter: markus makela Assignee: markus makela
Resolution: Incomplete Votes: 0
Labels: None

Sprint: MXS-SPRINT-165, MXS-SPRINT-166

 Description   

The first test case fails with the following error from time to time:

16:02:35   0.0s: 1. test_config_parameters
 
16:02:36   0.4s: Disabling and then enabling config_sync_cluster should not increment version
 
16:02:36   0.7s: TEST_FAILED! "config_sync" should be null after toggling config_sync_cluster: {"checksum": "cf5161fe8e36d98dfefd25a11f09248da4d1cbe5", "nodes": {"maxscale": "OK", "maxscale2": "OK"}, "origin": "maxscale", "status": "OK", "version": 2}
 
16:02:38   2.6s: TEST_FAILED! Expected version 1, got 3 from MaxScale 1
 
16:02:38   2.6s: TEST_FAILED! Expected version 1, got 3 from MaxScale 2



 Comments   
Comment by markus makela [ 2022-09-13 ]

The past 200 or so tests seem to only have failed due to VM related problems. I think this isn't a relevant problem and only happens when ran locally.

Generated at Thu Feb 08 04:27:04 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.