Bug #3732
closedMigration of some Directives version does not work if no modification are made in the parameters with the message "There are no modification to save"
Description
If I migrate a directive (in this case I tried to migrate user management from 1.0 to 2.0) I'm required to save the form afterwards. However, the message " There are no modification to save" appears and the directive hasn't been migrated. Workaround is to change anything in the form, migrate, save and then change it back.
Updated by Jonathan CLARKE about 11 years ago
- Category set to 14
- Priority changed from N/A to 2
Ouch, this sounds pretty bad. At least we have a workaround, so setting priority to 2.
However, I haven't been able to reproduce this on Rudder 2.6. It works for me, even without changing anything in the form. What version of Rudder, and which Technique/version are you seeing this on?
Updated by Dennis Cabooter about 11 years ago
# dpkg -l |grep rudd | grep tech ii rudder-techniques 2.6.2-precise0 Configuration management and audit tool - techniques
I tried to upgrade the User Management technique from 1.0 to 2.0.
Updated by Jonathan CLARKE about 11 years ago
- Status changed from New to 8
OK, confirmed. This doesn't happen with all Techniques, but it does with user management. We'll have to figure out why!
Updated by Jonathan CLARKE about 11 years ago
- Assignee set to François ARMAND
François is going to look into this.
Updated by François ARMAND about 11 years ago
- Status changed from 8 to In progress
Updated by François ARMAND about 11 years ago
Confirming that this bug is not present in 2.4 nor 2.5, the check for modification was added in 2.6
Updated by François ARMAND about 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/279
Updated by François ARMAND about 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 77b66fc649df6940dce4cd03e3d6a5bd2030a149.
Updated by Nicolas CHARLES about 11 years ago
Applied in changeset bfb16cca0875ad7b5f187a49353bacdfa2098f2d.
Updated by Nicolas PERRON about 11 years ago
- Subject changed from Migrate directive: There are no modification to save to Migration of Directives version does not work if no modification are made in the parameters with the message "There are no modification to save"
Updated by Nicolas PERRON about 11 years ago
- Subject changed from Migration of Directives version does not work if no modification are made in the parameters with the message "There are no modification to save" to Migration of some Directives version does not work if no modification are made in the parameters with the message "There are no modification to save"
Updated by Nicolas PERRON about 11 years ago
- Status changed from Pending release to Released
Updated by Nicolas PERRON about 11 years ago
This bug has been fixed in Rudder 2.6.3, which was released today.
Check out:
- The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2013-July/000036.html
- The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog26
- Download information: http://www.rudder-project.org/foswiki/Download/
Updated by Benoît PECCATTE over 9 years ago
- Category changed from 14 to Web - Config management