ḹet's enable migration for pinned VMs, required HP VMs migration - bug 1571024
the option is not effective anyway as there are other frontend validations
This seems to be a RFE (but lacks correct keywords), on the wrong component?
no, that's just a removal of annoying/useless config option in rhvm-setup-plugins blocking the actual RFE for HP VM live migration
This BZ solution was changed to totally removing the "CpuPinMigrationEnabled" config value from vdc_options table for upstream & downstream. This config value is not needed anymore due to supporting bug 1457250.
Verified on: ovirt-engine-4.2.6.4-0.0.master.20180823141941.gitb3a5b18.el7.noarch ovirt-engine-setup-base-4.2.6.4-0.0.master.20180823141941.gitb3a5b18.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-4.2.6.4-0.0.master.20180823141941.gitb3a5b18.el7.noarch ovirt-engine-setup-plugin-ovirt-engine-common-4.2.6.4-0.0.master.20180823141941.gitb3a5b18.el7.noarch Steps: 1. Connect to the engine via SSH 2. Run: # su - postgres # psql -d engine engine=# select * from vdc_options where option_name = 'CpuPinMigrationEnabled'; Results: option_id | option_name | option_value | version -----------+-------------+--------------+--------- (0 rows)
QE verification bot: the bug was verified upstream