Yup you will see that bug more frequently when not using the default object_build. I believe this bug is the reason the dayzmod team added all these constraints to where you can place a tent in the first place. You will definitely see it if you move a tents worldspace because you haven't update its uid to go with the new worldspace.
The objectUID from the database is calculated based on the position of an object. It is nothing more than a different representation of worldspace coordinates. It's used for all the keycodes in basebuilding 1.2. This is the unique identifier used by a client to update a tents inventory etc. The clients cannot read the database they pass the uid based on the objects position, if that uid doesnt match the uid that was originally inserted into the database (because something has caused its position to shift, like another object being close to it) then no database updates are possible. Even if you pack it it will respawn after a restart afaik.
I suggest staying on the default object_build and deleting all tents an stashes that have not been updated recently in the database if you are having problems. In basebuilding 1.3 rosska stores and reads the uid for BB objects differently so it cannot change over time, this wouldn't be possible for tents without a lot of work changing more dayzmod files though. You will see this bug on any dayzmod server but obviously basebuilding makes it more likely an objects position can shift slightly after it was originally built.
That all makes total sense! So I had not seen a release for Rosska's v1.3 of Base Building posted in the Release section. Is it released somewhere? If so, is there a migration guide for anyone already up on v1.2, or would it be a wipe of the PBOs and database and everyone would have to start over?