Bug 980042 - Unable to restore DB when selinux is disabled.
Summary: Unable to restore DB when selinux is disabled.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.3.0
Assignee: Eli Mesika
QA Contact: movciari
URL:
Whiteboard: infra
Depends On: 976337
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-01 09:55 UTC by Ilanit Stein
Modified: 2016-02-10 19:14 UTC (History)
9 users (show)

Fixed In Version: is7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-21 22:16:59 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 16322 0 None None None Never

Description Ilanit Stein 2013-07-01 09:55:55 UTC
Description of problem:

Restore DB fail when selinux is disabled (see log bellow).
when switching to selinux enforced, the restore works.
 
Log:

[root@istein-32 ~]# /usr/share/ovirt-engine/dbscripts/restore.sh -u postgres -d engine -f /tmp/00579652_221211073824_pgdump.tar -r -o
Restore of database engine from /tmp/00579652_221211073824_pgdump.tar started...
/tmp/00579652_221211073824_pgdump.tar: tar archive
chcon: can't apply partial context to unlabeled file `/tmp/00579652_221211073824_pgdump.tar_dir'
Failed to restore SELinux default settings for /tmp/00579652_221211073824_pgdump.tar_dir.



Version-Release number of selected component (if applicable):
sf18.2
(The DB tar file is from 3.1 setup)

How reproducible:
always

Expected results:
Restore DB should succeed also for selinux disabled.

additional info:
This bug was found during verification of Bug 973275

Comment 1 Eli Mesika 2013-07-23 19:34:31 UTC
fixed in commit : e7f6fda

Comment 2 Itamar Heim 2014-01-21 22:16:59 UTC
Closing - RHEV 3.3 Released

Comment 3 Itamar Heim 2014-01-21 22:23:39 UTC
Closing - RHEV 3.3 Released


Note You need to log in before you can comment on or make changes to this bug.