Description of problem: $Subject. So it's regenerated after restore. Didn't analyze full implications - probably it's at least annoying (user has to confirm the new key), might break stuff. Version-Release number of selected component (if applicable): 3.6 How reproducible: Always Steps to Reproduce: 1. setup an engine with vmconsole 2. backup 3. restore on another machine 4. engine-setup Actual results: vmconsole pki is regenerated Expected results: vmconsole pki is backed up and restored Additional info:
(In reply to Yedidyah Bar David from comment #0) > Description of problem: > > $Subject. > > So it's regenerated after restore. > > Didn't analyze full implications - probably it's at least annoying (user has > to confirm the new key), might break stuff. QE: Please check this. If significant, we should probably add doc text. To test: 1. setup a 3.6.5 engine+host+VM, configure vmconsole, make sure you can access the VM's serial console using ovirt-vmconsole. 2. Take a backup with engine-backup. 3. engine-cleanup 4. rm -rf /etc/pki/ovirt-vmconsole/* 5. restore the backup. 6. Try accessing the VM's serial console the same way. Please document here the errors/warnings/etc you get. For verification, repeat above with fixed build (3.6.6), and you should get no errors/warnings. Thanks.
Verified with: rhevm-3.6.6.2-0.1.el6.noarch Successfully connected via vmconsole after restore without warnings.