Describe the bug
When you upgrade the main Cacti Data Collector, attempting to access the remote Data Collectors will essentially stay in an upgrade loop. This is due to the version table being stuck at the prior version in the version table and not matching the version in the core database.
This is tricky, and is a timing issue since if the replication has not started and succeeded, this replication may cause the tables to be moved ahead of the files. So, maybe instead, as a part of the replicate out, we might want to detect a version change, and perform the full sync automatically for the remote collectors that are online.
To Reproduce
Steps to reproduce the behavior:
- Upgrade a main cacti server
- Wait for a file sync, which includes the cacti_version file
- After file sync is completed, attempt to login to the remote data collector
- Note you are stuck in an install loop
Expected behavior
Either upgrade should happen including a full sync, or the upgrade of the main server should include the full sync.
Describe the bug
When you upgrade the main Cacti Data Collector, attempting to access the remote Data Collectors will essentially stay in an upgrade loop. This is due to the version table being stuck at the prior version in the version table and not matching the version in the core database.
This is tricky, and is a timing issue since if the replication has not started and succeeded, this replication may cause the tables to be moved ahead of the files. So, maybe instead, as a part of the replicate out, we might want to detect a version change, and perform the full sync automatically for the remote collectors that are online.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Either upgrade should happen including a full sync, or the upgrade of the main server should include the full sync.