when moved to using conf.d structure, there is no reason why storing sysprep files in /etc as user can install his own osinfo config and overwrite product defaults reference with his own. this simplifies pushing product changes without the rpmsave/rpmnew hell and enables support to understand site customization. upgrade is comparing current install sysprep files and keep these that are different from product default at existing location, creating osinfo configuration for these. the move to osinfo neglected the ability of user to specify different setting for sysprep in database, we also fix that.
moving to 3.3.1 to get enough QA attention
(In reply to Michal Skrivanek from comment #1) > moving to 3.3.1 to get enough QA attention this is a packaging change that should not go to 3.3.0 to be able to maintain the 3.3.z without packaging changes.
(In reply to Alon Bar-Lev from comment #2) > (In reply to Michal Skrivanek from comment #1) > > moving to 3.3.1 to get enough QA attention > > this is a packaging change that should not go to 3.3.0 to be able to > maintain the 3.3.z without packaging changes. that should go to 3.3.0?
Verified on ovirt-engine-3.4.0-0.7.beta2.el6.noarch: There is no longer such directory: /etc/ovirt-engine/sysprep
Closing as part of 3.4.0