Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

lvol module state=absent fails (with error) if the volume group doesn't exist #3714

Closed
pol opened this issue Jul 31, 2013 · 2 comments
Closed

lvol module state=absent fails (with error) if the volume group doesn't exist #3714

pol opened this issue Jul 31, 2013 · 2 comments
Labels
bug This issue/PR relates to a bug.

Comments

@pol
Copy link
Contributor

pol commented Jul 31, 2013

The following task:

- name: remove legacy logical volume if present
  lvol: lv=live vg=store state=absent

This will fail if the "store" volume group doesn't exist. I think the expected result is that if the volume group is not present, then clearly the logical volume is also not present (the task should be successful).
@jimi-c jimi-c mentioned this issue Aug 3, 2013
Merged
mpdehaan pushed a commit that referenced this issue Aug 3, 2013
@jimi-c
Set result to skipped when vol group is missing and lv state=absent
d98ad7b 
Fixes issue #3714 - lvol module state=absent fails (with error) if
the volume group doesn't exist
@srgvg
Copy link
Contributor

srgvg commented Aug 8, 2013

I guess PR #3745 fixed this, so this may be closed?

$ ansible --version
ansible 1.3 (devel 0089ecfa7e) last updated 2013/08/07 11:14:11 (GMT +200)
$ ansible -m lvol -a "vg=whatever lv=something state=absent" localhost
localhost | success >> {
    "changed": false, 
    "stderr": false, 
    "stdout": "Volume group whatever does not exist."
}

@jimi-c
Copy link
Member

jimi-c commented Sep 10, 2013

Yep, closing this now.

@jimi-c jimi-c closed this as completed Sep 10, 2013
@ansibot ansibot added bug This issue/PR relates to a bug. and removed bug_report labels Mar 6, 2018
@ansible ansible locked and limited conversation to collaborators Apr 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug This issue/PR relates to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@pol @jimi-c @srgvg @ansibot