Skip to content

CTA taped fails on catalogue version updates

We have decided to separate catalogue update releases from software update releases (as seen with version v4.7.8, for example, which is a catalogue schema-only upgrade).

With this new process, we decided to decouple catalogue schema versions from CTA software versions (currently we are at catalogue v11.0, while CTA version is v4.8.9). All new catalogue versions will increment the MAJOR number, which makes the MAJOR/MINOR distinction less relevant.

This is causing some issues on CTA taped, right after each upgrade:

The origin of the problem is this check, that restricts the taped to a single catalogue schema MAJOR version:

Since we always update the catalogue schema before updating the taped daemons (each schema-only release should be done in a way that it stays compatible with the previous CTA software version), then this check should not cause the process to fail.

Edited by Volodymyr Yurchenko