|
Bugzilla – Full Text Bug Listing |
| Summary: | lvm2 systemd incorrectly uses dependencies on Fedora services (fedora-storage-init.service fedora-storage-init-late.service) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 13.1 | Reporter: | Forgotten User o5N6HWuMhD <forgotten_o5N6HWuMhD> |
| Component: | Basesystem | Assignee: | Dong Mao Zhang <dmzhang> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | arvidjaar |
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE 13.1 | ||
| Whiteboard: | |||
| Found By: | Community User | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User o5N6HWuMhD
2013-11-22 05:36:54 UTC
Looking at systemd units, looks like a combination of udev & raid (dm/md) service dependencies -- and, perhaps system.init? -- need to be added. dependency order needs to accommodate both LVM-on-RAID, and RAID-on-LVM. poking around to see what/how. fwiw, upgrades of 12.3 -> 13.1 with /boot + other-on-LVM -- *NO* RAID, boot without issue. so far, the 'problem boxes' all have raid in the mix. @nfbrown, does this look like an mdadm 3.3 - related issue to you? fyi, from https://forums.opensuse.org/english/get-technical-help-here/install-boot-login/492403-server-upgraded-12-3-13-1-lvm-raid-fails-boot-timeout-waiting-boot-device.html#post2600471 bit more detail re: hang at an LVM2/Dbus timeout waiting for the /boot device that's on RAID: http://pastebin.com/KcNPriuV this may be relevant: Bug 849752 - 13.1RC2 Cannot boot from RAID1 volume(s) https://bugzilla.novell.com/show_bug.cgi?id=849752#c9 this may be relevant: Bug 849752 - 13.1RC2 Cannot boot from RAID1 volume(s) https://bugzilla.novell.com/show_bug.cgi?id=849752#c9 I suspect there may be two issues here, (1) the lvm2 unit's references to *fedora (2) hang @ boot when /boot is on RAID leaving (1) here, splitting off (2) to: https://bugzilla.novell.com/show_bug.cgi?id=851993 (In reply to comment #7) > (1) the lvm2 unit's references to *fedora Ordering dependency on non-existent unit is noop. This is just minor cosmetic issue at most which probably is not worth extra patch to maintain. Re: noop on non-existent, understood.
But those Fedora units imply SOME sort of dependency -- in Fedora-land.
Is there an equivalent required dependency in Opensuse-land? SPecifically, which -- if any -- units in Opensuse are dealing with the same startup deps as:
fedora-storage-init.service
fedora-storage-init-late.service
and do they need to be included?
(In reply to comment #9) > > Is there an equivalent required dependency in Opensuse-land? lvm2-monitor.service just starts monitoring, which is optional anyway. If it is started it is ordered after lvm2-activation.service which does the real job. lvm2-activation.service is generated dynamically based on actual lvm.conf. The upstream code has commits 360c569ce8f0bfe936d59ca91de2716958550524 to remove this deps.. This is an autogenerated message for OBS integration: This bug (851741) was mentioned in https://build.opensuse.org/request/show/214084 Factory / lvm2 openSUSE-RU-2014:0186-1: An update that has 5 recommended fixes can now be installed. Category: recommended (moderate) Bug References: 779965,837954,851741,854076,854413 CVE References: Sources used: openSUSE 13.1 (src): lvm2-2.02.98-0.28.5.1 Update released for openSUSE 13.1. Resolved fixed. |