Lost config change after version update - KBH

HI, I had a version update available in KBH (sequence 20 over the existing deploy sequence 19). meanwhile i made a config change which created a sequence 21.

In the version history tab, it showed the required update as sequence 21 (naturally since it was same version - just config change) so i deployed it.
post which i deployed sequence 20 (it was showing as available update).
I cannot see the config change of sequence 20 in this newly deployed version.

did i do something wrong ? what should have been the correct order of execution ?

Hello harshdesai,

welcome to our community!

It appears that KOTS does not sync newly added config changes to newer sequences that already exist in the cluster. To have these changes reflected in the available versions under the Version History tab, please first click on Check for Updates or let the auto-update run, then deploy the new versions.

1 Like