Bugzilla – Bug 7193
tl-setup does not handle migration of removed or moved parameters
Last modified: 2018-06-05 10:29:28
You need to
before you can comment on or make changes to this bug.
When for example /vsmserver/allowed_shadowers is moved to
/shadowing/allowed_shadowers (like in bug 37) the administrator has to migrate
The same is true if a parameter is completely removed or renamed.
This has now been added as part of the 'parameters' migration choice in
tl-setup. As part of adding support for this feature, automatic migration for
/vsmserver/allowed_shadowers to /shadowing/allowed_shadowers have been added
(this config change was done on bug 37 for the 4.9.0 release).
Another change that is part of this is that we also have the ability to migrate
non-hiveconf configuration files when needed. No such example exists in recent
A crash in tl-setup migration and a failing python version test was fixed.
Should be all done now.
I started with generic tests of the refactored modules:
✓ System type
✓ Conf. migration
Everything worked fine except for the summary in GUI mode for an agent only
setup. In that case I got an almost blank page (just the heading).
Migration of an empty /vsmserver/allowed_shadowers (i.e. a default config) does
not remove the old value.
Otherwise the migration works well with the new value updated, the old removed
and nice logging. :)
Documentation and release notes both look good.
(In reply to comment #13)
> Everything worked fine except for the summary in GUI mode for an agent only
> setup. In that case I got an almost blank page (just the heading).
Fixed in r33392
(In reply to comment #14)
> Migration of an empty /vsmserver/allowed_shadowers (i.e. a default config) does
> not remove the old value.
The same was true for a corner case of /vsmserver/terminalservers where it's
value was empty prior to running the migration.
Fixed in r33393
Both issues now fixed and everything works fine.