Bug 1328036

Summary:	ovirt-vmconsole conf and pki are not backed up
Product:	[oVirt] ovirt-engine	Reporter:	Yedidyah Bar David <didi>
Component:	Backup-Restore.Engine	Assignee:	Yedidyah Bar David <didi>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Gonza <grafuls>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.6.1	CC:	bugs, mgoldboi, sbonazzo
Target Milestone:	ovirt-3.6.6	Flags:	rule-engine: ovirt-3.6.z+ mgoldboi: planning_ack+ sbonazzo: devel_ack+ pnovotny: testing_ack+
Target Release:	3.6.6
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: ovirt-vmconsole pki and conf were not backed up by engine-backup. Consequence: When restoring such a backup, engine-setup recreated the pki (and conf, which should have been identical by default). TODO fill in other consequences after QE try this. Fix: engine-backup was fixed to include these files in backups. Result: On restore, same conf and pki are used as in the backed up system.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-30 10:55:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yedidyah Bar David 2016-04-18 09:24:13 UTC

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:

Comment 1 Yedidyah Bar David 2016-04-19 09:27:34 UTC

(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.

Comment 3 Gonza 2016-05-16 17:01:15 UTC

Verified with:
rhevm-3.6.6.2-0.1.el6.noarch

Successfully connected via vmconsole after restore without warnings.