Bug #3732
closed
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"
Added by Dennis Cabooter over 11 years ago.
Updated over 9 years ago.
Category:
Web - Config management
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.
- 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?
# 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.
- 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!
- Assignee set to François ARMAND
François is going to look into this.
- Status changed from 8 to In progress
Confirming that this bug is not present in 2.4 nor 2.5, the check for modification was added in 2.6
- 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
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- 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"
- 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"
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.3, which was released today.
Check out:
- Category changed from 14 to Web - Config management
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by 
Updated by 
Updated by Nicolas PERRON 
Updated by