Bug #9859
closed
"Migrate" button is displayed for deprecated techniques even if all version are deprecated
Added by Dmitry Svyatogorov almost 8 years ago.
Updated over 7 years ago.
Category:
Web - Config management
Description
1. Technique "Package management for Debian / Ubuntu / APT systems version 4.0" is deprecated since 4.0
2. Press "Migrate now", modify e.g. "Description", result stays in "Package management for Debian…". No error report, at least in UI.
3. Below lays the dump of one of deprecated directives.
# cat ./directives/applications/aptPackageInstallation/7a5c6e13-e604-44b0-a15d-e64eca3097d4.xml
<directive fileFormat="6">
<id>7a5c6e13-e604-44b0-a15d-e64eca3097d4</id>
<displayName>Dell srvadmin-storageservices</displayName>
<techniqueName>aptPackageInstallation</techniqueName>
<techniqueVersion>4.0</techniqueVersion>
<section name="sections">
<section name="Debian/Ubuntu packages">
<var name="APT_PACKAGE_ALLOW_UNTRUSTED">false</var>
<var name="APT_PACKAGE_DEBACTION">add</var>
<var name="APT_PACKAGE_DEBLIST">srvadmin-storageservices</var>
<section name="Package version">
<var name="APT_PACKAGE_VERSION"></var>
<var name="APT_PACKAGE_VERSION_CRITERION">==</var>
<var name="APT_PACKAGE_VERSION_DEFINITION">default</var>
</section>
</section>
</section>
<shortDescription>Install srvadmin-storageservices</shortDescription>
<longDescription>x</longDescription>
<priority>5</priority>
<isEnabled>true</isEnabled>
<isSystem>false</isSystem>
<policyMode>default</policyMode>
</directive>
Technique "Package management" v1.0 has no directives at this moment.
I think there is no way to migrate from the old package technique to the new one :( but it should definitely be possible ...
- Assignee set to François ARMAND
Maybe we should remove the migrate button if it's not possible (or find a way to achieve this)
Right now I'm playing with Rudder's API, one of auxiliary goals is to implement on-the-fly translation for such case.
As far as there exists both left and right structure descriptions, left set might be mapped to the right (in case of "conformal mapping", but it seems to be true for next generation of the same technique).
I'll publish the code since I'll find it usable.
So, to sum up a little: the whole old package technique (rpm, deb) were depreciated in 4.0 in favor of the new os-independant package technique. There is no automatic migration possible between the two - even if playing with api / jq can certainly automate most of it - we would love to see such a contribution :))
The problem here is that we are displaying the "migrate now" notice which is only dedicated to migrating to a newer version of the same technique. In that case, there is none, and so it's a bug to display the notice.
Hope it's clearer ?
- Status changed from New to In progress
- Assignee changed from François ARMAND to Vincent MEMBRÉ
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/1510
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.0.3 and 4.1.0~beta3 which were released today.
Wow, thank you so much Dimitri.
Benoit, could you take a look to that one? Do you think we can add it in tools repos, to help people migrate to new package techniques ?
Alexis, do you have an idea where we could document the existence and use case of that script?
- Found in version (s) 4.0.2 added
- Found in version(s) old deleted (
4.0.2)
- Subject changed from Broken directive migration in Rudder 4.0.2 to "Migrate" button is displayed for deprecated techniques even if all version are deprecated
- Related to User story #10276: I Can not migrate from old "package technique" to new one automatically added
For information, I opened a dedicated ticket about the migration for package techniques here: http://www.rudder-project.org/redmine/issues/10276
I put a link to Dimitry script, hope it would helps people having the same problem to discover it more easily.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by