Bug 806349

Summary:	/data not mounted after reboot
Product:	[Retired] oVirt	Reporter:	Mike Burns <mburns>
Component:	ovirt-node	Assignee:	Fabian Deutsch <fdeutsch>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	acathrow, dyasny, jboggs, mburns, mikom3, ovirt-bugs, ovirt-maint
Target Milestone:	---	Keywords:	Regression
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	2.4.0	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-06-11 08:58:01 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Burns 2012-03-23 14:01:24 UTC

Description of problem:
the /data partition is not mounted correctly after reboot.  This causes problems with local storage domains and upgrades triggered from ovirt engine.

Version-Release number of selected component (if applicable):
2.3.0

How reproducible:
Seem multiple times from multiple users

Steps to Reproduce:
1.configure and install
2.reboot
3.
  
Actual results:
/data is not mounted

Expected results:
/data should be mounted

Additional info:

Comment 1 Fabian Deutsch 2012-03-26 16:08:44 UTC

This also affects all other LV in HostVG except Config, which get's mounted using ovirt-early.

Comment 2 Fabian Deutsch 2012-03-26 19:38:29 UTC

systemd might not be mounting that mp, because it thinks that the underlying device is not yet started. Checked with systemctl show dev-disk-by-….device

Comment 3 Fabian Deutsch 2012-03-27 10:18:35 UTC

http://gerrit.ovirt.org/3117

The gerrit patch tries to given an explanation for this bug and suggest a hackish solution for now. See also bug #807203

Comment 4 Fabian Deutsch 2012-03-28 09:56:00 UTC

This patch doesn't work for all mount points. E.g. /var/log is mounted to late so already created log files are hidden.

My current plan is to add the HostVG mountpoints to the ro-image by either using it's path or labels.
Any objections?

Comment 5 Mike Burns 2012-03-28 12:24:52 UTC

(In reply to comment #4)
> This patch doesn't work for all mount points. E.g. /var/log is mounted to late
> so already created log files are hidden.
> 
> My current plan is to add the HostVG mountpoints to the ro-image by either
> using it's path or labels.
> Any objections?

There is (or at least was) a mount_logging function that was supposed to handle this problem.  I know it existed in the bash scripts, but not sure if still works or if it was ported to the python.  Since this is all init script setup, it might make sense to try this before the mount -a

I had thought that all the mount points already existed in the ro-image.  Is that not the case?  If they're not, how does pre-creating them help?

Moving this bug back to assigned since there is still work to be done and Modified implies that work is complete (except for final release)

Comment 6 Fabian Deutsch 2012-06-11 08:58:01 UTC

In recent F17 builds /dev/mapper/HostVG-Data is mounted to /data, as well as all other HostVG-* are mounted to their corresponding filesystem targets.