Bug #12232
closed
Missing or invalid migration for techniques generated by technique editor from 4.2 to 4.3
Added by Nicolas CHARLES over 6 years ago.
Updated over 6 years ago.
Description
Upgrading from 4.2 to 4.3 breaks report on techniques created by technique editor
We are missing the component key and value
- Assignee set to Vincent MEMBRÉ
Should work now.
We need to check again
We need to do a full rewrite of technique from technique editor on migration, a little like what is done when installing the DSC agent.
touching file /opt/rudder/etc/force_ncf_technique_update does not solve the issue (even if triggering a full policy regeneration afterwards)
this file disapear after a restart of web interface, but there is no log about what it does
- Target version changed from 4.3.0~rc2 to 4.3.0~rc3
I do have commits in configuration-repository, but it empty:
commit cfff44f5b553127df8bf2e627954f39edc3f4b39
Author: Rudder system account <email not set>
Date: Fri Mar 30 14:16:24 2018 +0200
Commiting Technique 'test' metadata
commit 1ee13b8c9d20d48f870d0d5129ae204408fd2e46
Author: Rudder system account <email not set>
Date: Fri Mar 30 14:16:24 2018 +0200
Commiting Technique 'test' file for agent
# git diff a590317668568ae1b6d1ffba9c889538b3ab5fc6
root@server:/var/rudder/configuration-repository/techniques#
- Status changed from New to In progress
- Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder-packages/pull/1562
- Status changed from Pending technical review to Pending release
- Target version changed from 4.3.0~rc3 to 4.3.0~rc2
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.3.0~rc2 which was released today.
Also available in: Atom
PDF