Description of problem: When sysprepping a sealed Windows VM, the ProductKey is empty. The ProductKey* field is filled correctly in rhevm-setup and the engine has been restarted to pick up the changes. This is sort of regression of bug 873742 (RHEV doesn't fill ProductKey correctly) Version-Release number of selected component (if applicable): si16 / rhevm-backend-3.3.0-0.22.master.el6ev.noarch How reproducible: always Steps to Reproduce: 1. fill in appropriate ProductKey* fields in rhevm-config, restart engine 2. create Windows VM with correct OS Type set 3. run the VM with sysprep floppy attached 4. after the VM boots, open A:\sysprep.inf and look up ProductKey value Actual results: ProductKey is empty Expected results: ProductKey should match the value of ProductKey* set in rhevm-config Additional info:
Happened to me with XP and 7 32b guests so far.
The configuration of sysprep should be done in /etc/ovirt-engine/osinfo.conf.d directory. The database values are ignored. We have to decide if we should - deprecate database values, or - use database values as a default (in case os info value is empty).
patch 19743 merged upstream master.
release note flag?
merged ovirt-engine-3.3 branch as 087f4b5849be858d4fb86497ae93ff82d3cd5e18
Verified in rhevm-3.3.0-0.26.master.el6ev.noarch (is19). Verification steps: 1) Create new VM (OS type Windows 7 x64) with Win 7 x64 installed. 2) Following comment 3, set the product key in osinfo configuration file (not via rhevm-config): In /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties file set value of `os.windows_7x64.productKey.value` to `w7x64-abcde-12345-fghij-56789`. 3) Restart ovirt-engine service. 4) Run Once the VM with [sysprep] floppy attached. 5) In the guest VM, open A:\sysprep.inf and the value in <ProductKey> tag is <Key>w7x64-abcde-12345-fghij-56789</Key>.
Closing - RHEV 3.3 Released