Description of problem: Up to now when a config entry was deprecated, we had to remove it in the pre-upgrade step calling fn_db_delete_config_value from 0000_config.sql. This may be problematic if a reference to the deleted entry exists in one of the upgrade scripts, in such case the entry will be removed in the pre-upgrade step and then the upgrade script referring this key will fail and cause all the upgrade process to fail. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Attempt to delete a config key that exists in one of the upgrade scripts 2. run upgrade Actual results: Upgrade process fails on the script that refers the removed config key Expected results: Upgrade scripts succeeds Additional info: all deprecated config entries should be moved to an upgrade script resolving this issue and adding additional benefit of executing all this mass removals only once instead doing that again and again on each upgrade.
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
In oVirt testing is done on single release by default. Therefore I'm removing the 4.0 flag. If you think this bug must be tested in 4.0 as well, please re-add the flag. Please note we might not have testing resources to handle the 4.0 clone.
ok, rhevm-dbscripts-3.6.2.5-0.1.el6.noarch no 'fn_db_delete_config*' in pre_upgrade scripts.