#1753 iTop 2.6.1 data synchro ignoring the full load interval, not obsoleting the replica

[sonicblind]

I have just install iTop 2.6.1 and testing the data synchronization.
But even the very basic setup seems not to work.

I setup basic synchro data source for class Printer.
Full Load Interval is set to 1 minute and Delete Policy is set to Delete.
Screenshot - itopA.png

So I am expecting the synchro process to delete an entry from iTop if I do not "touch" the synchro data/replica for longer than 1 minute.

I create an entry in synchro_data_table which is assigned to Printer data source and then run synchro_exec.php, object is now created in iTop and synchronized, as expected.

Then I wait for more than 1 minute and re-run synchro_exec.php and I am expecting the object to be obsoleted and deleted because within that waiting interval I haven't updated (touched) the data source entry.

Here comes the problem. The synchro_exec.php reports that the replica has indeed been touched since last synchro. See screenshot itopB.png.

In screenshot itopC.png, we can see that I ran synchro_exec at 16:01:30, and that 1 existing replica has been unchanged.

Screenshot itopD.png shows the details of mentioned replica. It says replica has been created at 15:54:27 and last seen 15:54:51.

So last seen is 15:54:51, full load interval is 1 minute and policy set to delete, but at 16:01:30 the process did not delete the object and instead thought it's still not obsoleted.

In previous versions of iTop I had no problems with synchronization, so I believe I am doing the setup and run correctly.

So to me it looks like iTop 2.6.1 is misbehaving.

Could you please clarify this issue?

Thanks,
Martin

[sonicblind]

I actually found potential problem in the code and posted my findings on GitHub:
https://github.com/Combodo/iTop/commit/75737b4ffee536eaebf3d5cd22a535e67ead7410?_pjax=%23js-repo-pjax-container#commitcomment-33560429

[Guillaume Lajarige]

Hello Sonicblind,

I saw that Pierre is discussing with you on GitHub about this, I let you see with him then.

[sonicblind]

Yes Guillaume, he is. Thank you.

[Pierre Goiffon]

Hello,
The 2.6.2 tag has been created in the GitHub repo, including this fix (corresponding commits are referenced with "N°2211"), so I'm closing this ticket as fixed.
There are no plan to release a 2.6.2 package for the community yet.