Automatic systemvmtemplate seeding in new zone create duplicates

[yadvr]

problem

I added another zone in ACS 4.22 which already had 4.22 x86 and arm64 systemvmtempaltes added in first zone (but sorted to be end of the templates list). After new zone was added the automatic seeder logic kicked in but created new systemvmtemplate rule but downloaded file (with new template ID 136, instead of re-using existing ID 135) for the new zone. This created issue as the template was only donwloaded to new zone's secondary storage and not the others/existing.

I had to hack the db, remove the new entry and rename the folder on new zone's secondary storage to 135 to get it working.

versions

ACS 4.22, new zone with arm64 host

The steps to reproduce the bug

...

What to do about it?

No response

[yadvr]

cc @shwstppr