Description of problem: There was patch deprecating vdc_options values. In given patch there's problem with applying upgrade scripts. In one of upgrade scripts, values is read from vdc_options table and stored elsewhere, rendering this vdc_options row useless. However, if we remove this value from vdc_options table in 0000_config.sql, upgrade script won't find it and won't persist it elsewhere. Therefore we need to remove these values only after it's useless, ie. in upgrade script. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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.
Fixed bug tickets must have version flags set prior to fixing them. Please set the correct version flags and move the bugs back to the previous status after this is corrected.
please provide Steps to Reproduce.
Steps to reproduce — this is probably not that easy. Let me elaborate. There was incorrect sequence of db statements, which produced state, that during upgrade was first removed row from vdc_options table and following script was reading this row, to fill in some another db table. Anyways, unability to start up server was caused by badly filled db, due to given issue in upgrade process. If you want to reproduce it, you probably have to init db using ovirt version preceding merging of this patch, then get newest ovirt version and try to update db. If table mac_pool_ranges is not empty after that ugprade, you can state that this bug is gone.
*** Bug 1294091 has been marked as a duplicate of this bug. ***