Git and tag definition files being deleted on gateway start

Ignition
1

Hi all,

Regarding git and pushing changes from our development servers to production, hope someone can advise and help us with this.

What we do:

  • Stop the gateway
  • Pull changes on the current branch, this meaning adding tags.json and unary-resource.json files in their respective folders.
  • Starting the gateway

Then this happens:
Ignition deletes all the new files and starts the gateway without these tags.
We see nothing in the gateway log, but found migration.md files being created. Example below, don't know if related?

Also tried to stop, delete db/config.idb (as per https://forum.inductiveautomation.com/t/the-role-of-config-idb-in-ignition-8-3-and-migrations-from-8-1/115541/2) and restart. Same behaviour.

Running 8.3.7 in an redundant setup.

All advices is much appreciated. Thanks in advance!

Migration Log

Duration: 157 ms

Summary

1 migration strategies were unable to complete due to errors.3 tables remain to be migrated.

Migration Details

Strategies Executed

Image Migrator

Trigger table: IMAGES

Duration: 71 ms

Error: com.inductiveautomation.ignition.common.resourcecollection.PushConflictException: CREATE conflict: 'ResourceId{resourcePath=ignition/images/Builtin, collectionName=core}' already exists

Remaining Tables

AUTHPROFILEPROPERTIES_LOCALFALLBACKCACHE (missing migration strategy)

IMAGES

LOCALFALLBACKCACHE_ENTRY (missing migration strategy)
2

Also tested: Restored files, scanned file system from gateway UI, restart Ignition.

  • Deleted the files.
3

Adding more information as the quest goes on:

Tested with copying all my tag files to resources/external. They then show up in the designer, woho!

But: Adding another tag inside one of these folders does not affect the file system at all, neither in core or external, and Im not able to track changes with git. There is no easy way to choose where to store tag files in the designer either ?

4

Hello,

Is it only tags.json that is affected, or are the udts.json files being deleted too? I’m also assuming you’re referring to the tag-definition directory.

When you say you’re restoring the files, are you restoring the repository to the last commit, or are you selectively restoring only the deleted tags.json files?

5

Hi,

It probably has something to do with how you mount your files to Ignition.

You might want to have a look at this video for working with git and CI/CD:

And you can take a look at the repo that comes with it, so you can see how the volumes are setup to work well with git.

6

Hi Noah,

Thanks for replying. Its both tags and UDTs in tag-definition and tag-type-definition being deleted.

My theory is that tag import does something more than just creating the files. There is a difference between the files and the ignition engine even after scanning the file system. Just pulling files does not affect the engine, and it overwrites the changes at restart.

7

Hi Jasper,

Thanks for replying. I watched your video and I think we do very much the same. It works very well with gateway config and views, but we are struggeling with tags. Its like the gateway doesnt catch that these files are added. I could not see if any of your scripts do any import and export on the fly.

Cheers

8

No, no imports or exports, just moving those files, and doing a re-scan, so I don't know what it is that would be going wrong here in your setup.

9

Not sure what you mean by import and export. As Jasper alluded to, You should commit your tags, pull the changes, and rescan the configuration and the gateway should automatically update the tags and tag definitions.

In the meantime, I would reach out to support and reference this forum post. If you can attach anymore information like your compose file, environment setup etc, that would be helpful. Are you doing anything special for the tags specifically that is different from your other gateway resources?