Bug 874062 - ExecStop= borked
Summary: ExecStop= borked
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lvm2
Version: 18
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
Assignee: Peter Rajnoha
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-07 12:03 UTC by Tomasz Torcz
Modified: 2012-12-20 16:15 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-20 16:15:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Tomasz Torcz 2012-11-07 12:03:48 UTC
Description of problem:
[/usr/lib/systemd/system/lvm2-monitor.service:15] Invalid executable path in command line, ignoring: "/usr/sbin/lvm vgchange --monitor n --config 'global{use_lvmetad=0}'"

Double quotes have to be dropped, apparently.

Version-Release number of selected component (if applicable):
lvm2-2.02.98-1.fc18.x86_64

Comment 1 Alasdair Kergon 2012-11-07 12:28:28 UTC
Was fixed in rawhide last week and will be propagated back into f18 builds too shortly.

Comment 2 Fedora Update System 2012-11-07 18:56:47 UTC
lvm2-2.02.98-2.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2012-17684/lvm2-2.02.98-2.fc18

Comment 3 Fedora Update System 2012-11-09 03:20:46 UTC
Package lvm2-2.02.98-2.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing lvm2-2.02.98-2.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-17684/lvm2-2.02.98-2.fc18
then log in and leave karma (feedback).

Comment 4 Fedora Update System 2012-12-20 16:15:03 UTC
lvm2-2.02.98-2.fc18 has been pushed to the Fedora 18 stable repository.  If problems still persist, please make note of it in this bug report.


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