Unable to start LVM agent due to a syntax error

Bug #1614529 reported by EOLE team
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
resource-agents (Ubuntu)
Fix Released
Undecided
Unassigned
Xenial
Won't Fix
Medium
Unassigned
Yakkety
Won't Fix
Medium
Unassigned

Bug Description

Hello,

I try to configure an ocf:heartbeat:LVM ressource but I got an “invalid parameter” error message and an exit status “2”.

Adding ”set -x” to the RA, I found the following log:

Aug 18 15:11:22 [11355] nebula4 lrmd: notice: operation_finished: p_vg-one_start_0:14672:stderr [ + options=-aly --monitor y ]
Aug 18 15:11:22 [11355] nebula4 lrmd: notice: operation_finished: p_vg-one_start_0:14672:stderr [ + echo -aly --monitor y ]
Aug 18 15:11:22 [11355] nebula4 lrmd: notice: operation_finished: p_vg-one_start_0:14672:stderr [ + local vgchange_options=-aly --monitor y ]
Aug 18 15:11:22 [11355] nebula4 lrmd: notice: operation_finished: p_vg-one_start_0:14672:stderr [ /usr/lib/ocf/resource.d/heartbeat/LVM: 416: local: --monitor: bad variable name ]
Aug 18 15:11:22 [11355] nebula4 lrmd: debug: operation_finished: p_vg-one_start_0:14672:stdout [ -- empty -- ]
Aug 18 15:11:22 [11358] nebula4 crmd: notice: process_lrm_event: Operation p_vg-one_start_0: invalid parameter (node=nebula4, call=155, rc=2, cib-update=241, confirmed=true)

Regards.

Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

Tags: patch xenial
Revision history for this message
EOLE team (eole-team) wrote :
Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

The attachment "LVM.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

I'm clearing out bugs that were dormant for too long.

This was fixed upstream in 1:4.0.0~rc1-1, that is already in Zesty and later.
So this is about fixing it in Xenial/Yakkety which is on 3.9.7

I beg your pardon this idled so long, but we'd need some help for the SRU. Especially how to reproduce to test and verify.
If you could add a template for the SRU [1] here that would be great.

Triage-note: once SRU template is complete this is server-next.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

Changed in resource-agents (Ubuntu):
status: New → Fix Released
Changed in resource-agents (Ubuntu Xenial):
status: New → Triaged
Changed in resource-agents (Ubuntu Yakkety):
status: New → Triaged
Changed in resource-agents (Ubuntu Xenial):
importance: Undecided → Medium
Changed in resource-agents (Ubuntu Yakkety):
importance: Undecided → Medium
Revision history for this message
Bryce Harrington (bryce) wrote :

[Standard support has ended for Trusty]

Changed in resource-agents (Ubuntu Xenial):
status: Triaged → Won't Fix
Changed in resource-agents (Ubuntu Yakkety):
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.