Description of problem: the lookup algorithem for a derived value by version is naive and rely on making the default version-less values. this doesn't scale when features update and have a default set in a later version os.base.k.value = X os.derived.k.value.3.2 = Y os.derived.k.value.3.3 = ? - this should be Y. instead it X to overcome that we duplicate a property and bump the version value os.derived.k.value.3.3 = Y Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: we be able to get Y for os.derived.k.value.3.3 without adding an entry Additional info:
Setting target release to current version for consideration and review. please do not push non-RFE bugs to an undefined target release to make sure bugs are reviewed for relevancy, fix, closure, etc.
Roy, you need to revive and finish the patch I think
Roy? I think it's really worth finishing this one eventually, it's a great enhancement
nothing going on so far, pushing out of 3.5
the out of the box default values is good enough so there is no need for that change. see the merged https://gerrit.ovirt.org/#/c/39077/ or https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=829815c6a245c4ace32a248123c13fb37e8bb14e