Bug 8329

Summary: lvm2-monitor service fails to start.
Product: Mageia Reporter: Dave Hodgins <davidwhodgins>
Component: RPM PackagesAssignee: Thomas Backlund <tmb>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal Keywords: PATCH
Version: 2   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: lvm2-2.02.95-1.mga2.src.rpm CVE:
Status comment:
Attachments: Patch to drop the config parameter

Description Dave Hodgins 2012-12-08 03:23:12 CET
After upgrading a system using lvm from Mageia 1 to 2, the lvm2-monitor
service fails to start.

Running ...
SYSTEMCTL_SKIP_REDIRECT=1 bash -x -v /etc/init.d/lvm2-monitor start
shows ...
+ GPRINTF_REST='/sbin/vgchange --monitor y --poll y --config log{command_names=0 prefix="  "} bk'
+ echo -n 'Starting monitoring for VG bk: '
Starting monitoring for VG bk: + /sbin/vgchange --monitor y --poll y --config 'log{command_names=0' 'prefix="' '"}' bk
  Parse error at byte 20 (line 1): unexpected token
  Failed to set overridden configuration entries.
  Run `vgchange --help' for more information.
+ failure 'Starting monitoring for VG bk:'

The above is generated from the script line ...
action "Starting monitoring for VG %s:" "$vg" $VGCHANGE --monitor y --poll y --config 'log
{command_names=0 prefix="  "}' $vg || ret=$?

The problem appears to be caused by the dropping of the single quotes around
the parameter being passed to the config parameter, by the action function.

The config parameter doesn't appear to be needed, so the easiest fix is to
simply drop the config parm.  I'll attach a patch.
Comment 1 Dave Hodgins 2012-12-08 03:25:42 CET
Created attachment 3213 [details]
Patch to drop the config parameter

With the attached patch applied, the lvm2-monitor service starts and stops ok.
Manuel Hiebel 2012-12-08 18:33:07 CET

Keywords: (none) => PATCH

Comment 2 Manuel Hiebel 2013-10-22 12:11:54 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 3 Manuel Hiebel 2013-11-23 16:15:02 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD