Bug 1480567 - backend-setup fails while changing the attributes of the logical volume
backend-setup fails while changing the attributes of the logical volume
Status: NEW
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: gdeploy (Show other bugs)
3.3
x86_64 Linux
unspecified Severity medium
: ---
: ---
Assigned To: Sachidananda Urs
SATHEESARAN
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-11 08:04 EDT by SATHEESARAN
Modified: 2017-08-11 08:11 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
console output while creating bricks (14.03 KB, application/octet-stream)
2017-08-11 08:06 EDT, SATHEESARAN
no flags Details
gdeploy configuration file used (135 bytes, application/octet-stream)
2017-08-11 08:09 EDT, SATHEESARAN
no flags Details

  None (edit)
Description SATHEESARAN 2017-08-11 08:04:55 EDT
Description of problem:
------------------------
While creating gluster bricks, using backend-setup of gdeploy, I observed that gdeploy failed in the step to change attributes of the logical volume. 

Note:
This happens consistently with RHEL 7.4 platform, and works well with RHEL 7.3

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
RHEL 7.4
gdeploy-2.0.2-14

How reproducible:
------------------
Always

Steps to Reproduce:
-------------------
1. Create bricks using backend-setup module of gdeploy with RHGS node based on RHEL 7.4 

Actual results:
---------------
gdeploy throws error while changing attributes of the logical volume

Expected results:
------------------
All the steps for backend-setup should work successfully and should not fail


Additional info:
-----------------
Here is the conf file used to create bricks:

[hosts]
host1.example.com
host2.example.com
host3.example.com

[backend-setup]
devices=vdb,vdc

Here is the error snip
<snip>
TASK [Change the attributes of the logical volume] *****************************
failed: [dhcp37-77.lab.eng.blr.redhat.com] (item={u'lv': u'GLUSTER_lv1', u'pool': u'GLUSTER_pool1', u'vg': u'GLUSTER_vg1'}) => {"failed": true, "item": {"lv": "GLUSTER_lv1", "pool": "GLUSTER_pool1", "vg": "GLUSTER_vg1"}, "msg": "  \"GLUSTER_vg1/GLUSTER_vg1/GLUSTER_pool1\": Invalid path for Logical Volume.\n", "rc": 5}
failed: [dhcp37-214.lab.eng.blr.redhat.com] (item={u'lv': u'GLUSTER_lv1', u'pool': u'GLUSTER_pool1', u'vg': u'GLUSTER_vg1'}) => {"failed": true, "item": {"lv": "GLUSTER_lv1", "pool": "GLUSTER_pool1", "vg": "GLUSTER_vg1"}, "msg": "  \"GLUSTER_vg1/GLUSTER_vg1/GLUSTER_pool1\": Invalid path for Logical Volume.\n", "rc": 5}
failed: [dhcp37-209.lab.eng.blr.redhat.com] (item={u'lv': u'GLUSTER_lv1', u'pool': u'GLUSTER_pool1', u'vg': u'GLUSTER_vg1'}) => {"failed": true, "item": {"lv": "GLUSTER_lv1", "pool": "GLUSTER_pool1", "vg": "GLUSTER_vg1"}, "msg": "  \"GLUSTER_vg1/GLUSTER_vg1/GLUSTER_pool1\": Invalid path for Logical Volume.\n", "rc": 5}
...ignoring
failed: [dhcp37-77.lab.eng.blr.redhat.com] (item={u'lv': u'GLUSTER_lv2', u'pool': u'GLUSTER_pool2', u'vg': u'GLUSTER_vg2'}) => {"failed": true, "item": {"lv": "GLUSTER_lv2", "pool": "GLUSTER_pool2", "vg": "GLUSTER_vg2"}, "msg": "  \"GLUSTER_vg2/GLUSTER_vg2/GLUSTER_pool2\": Invalid path for Logical Volume.\n", "rc": 5}
...ignoring
failed: [dhcp37-214.lab.eng.blr.redhat.com] (item={u'lv': u'GLUSTER_lv2', u'pool': u'GLUSTER_pool2', u'vg': u'GLUSTER_vg2'}) => {"failed": true, "item": {"lv": "GLUSTER_lv2", "pool": "GLUSTER_pool2", "vg": "GLUSTER_vg2"}, "msg": "  \"GLUSTER_vg2/GLUSTER_vg2/GLUSTER_pool2\": Invalid path for Logical Volume.\n", "rc": 5}
...ignoring
failed: [dhcp37-209.lab.eng.blr.redhat.com] (item={u'lv': u'GLUSTER_lv2', u'pool': u'GLUSTER_pool2', u'vg': u'GLUSTER_vg2'}) => {"failed": true, "item": {"lv": "GLUSTER_lv2", "pool": "GLUSTER_pool2", "vg": "GLUSTER_vg2"}, "msg": "  \"GLUSTER_vg2/GLUSTER_vg2/GLUSTER_pool2\": Invalid path for Logical Volume.\n", "rc": 5}

</snip>
Comment 1 SATHEESARAN 2017-08-11 08:06:44 EDT
Created attachment 1312106 [details]
console output while creating bricks
Comment 2 SATHEESARAN 2017-08-11 08:09:04 EDT
Created attachment 1312108 [details]
gdeploy configuration file used
Comment 3 SATHEESARAN 2017-08-11 08:10:55 EDT
With the testing that I did, I could not estimate the consequence of this issue.
Sac will investigating, what had failed, why it had failed and its consequence.

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