[Bugs] [Bug 1269125] New: Data Tiering:Regression: automation blocker:vol status for tier volumes using xml format is not working

bugzilla at redhat.com bugzilla at redhat.com
Tue Oct 6 11:50:53 UTC 2015


https://bugzilla.redhat.com/show_bug.cgi?id=1269125

            Bug ID: 1269125
           Summary: Data Tiering:Regression: automation blocker:vol status
                    for tier volumes using xml format is not working
           Product: GlusterFS
           Version: 3.7.4
         Component: tiering
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
        QA Contact: bugs at gluster.org
                CC: bugs at gluster.org



Description of problem:
========================
Most of our automation scripts use xml formatting for parsing values.
But the xml o/p of vol status of a tier volume is not working. it was working
previously.
This is a serious blocker for automation runs


Version-Release number of selected component (if applicable):
==============================================================
Not working on 3.7.4-0.65 and 3.7.4-0.67
(was working on 3.7.4-0.63)


How reproducible:
===================
easily

Steps to Reproduce:
1.)create a tier volume and start it 
2.Now issue status of the vol using xml "vol status <vname> --xml"

Actual results:
===============
no o/p is displayed for tier volume, but works well for regular vol




Tier vol o/p:
============
[root at zod ~]# gluster v status bulgaria
Status of volume: bulgaria
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Hot Bricks:
Brick yarrow:/rhs/brick7/bulgaria_hot       49155     0          Y       8067 
Brick zod:/rhs/brick7/bulgaria_hot          49155     0          Y       30108
Brick yarrow:/rhs/brick6/bulgaria_hot       49154     0          Y       8087 
Brick zod:/rhs/brick6/bulgaria_hot          49154     0          Y       30126
Cold Bricks:
Brick zod:/rhs/brick1/bulgaria              49152     0          Y       30144
Brick yarrow:/rhs/brick1/bulgaria           49152     0          Y       8105 
Brick zod:/rhs/brick2/bulgaria              49153     0          Y       30162
Brick yarrow:/rhs/brick2/bulgaria           49153     0          Y       8127 
NFS Server on localhost                     2049      0          Y       1923 
Quota Daemon on localhost                   N/A       N/A        Y       30200
NFS Server on yarrow                        2049      0          Y       11924
Quota Daemon on yarrow                      N/A       N/A        Y       8234 

Task Status of Volume bulgaria
------------------------------------------------------------------------------
Task                 : Tier migration      
ID                   : 55803993-94aa-407b-b085-b2942c32a289
Status               : in progress         

[root at zod ~]# gluster vol status bulgaria  --xml






Regular vol o/p
================
[root at zod ~]# gluster v status testvol
Status of volume: testvol
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick zod:/rhs/brick1/testvol               49156     0          Y       1900 
Brick yarrow:/rhs/brick1/testvol            49156     0          Y       11883
NFS Server on localhost                     2049      0          Y       1923 
NFS Server on yarrow                        2049      0          Y       11924

Task Status of Volume testvol
------------------------------------------------------------------------------
There are no active volume tasks
[root at zod ~]# gluster vol status testvol --xml
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<cliOutput>
  <opRet>0</opRet>
  <opErrno>0</opErrno>
  <opErrstr/>
  <volStatus>
    <volumes>
      <volume>
        <volName>testvol</volName>
        <nodeCount>4</nodeCount>
        <node>
          <hostname>zod</hostname>
          <path>/rhs/brick1/testvol</path>
          <peerid>6aa15961-3ab6-4b6f-8412-8e084b7dfac7</peerid>
          <status>1</status>
          <port>49156</port>
          <ports>
            <tcp>49156</tcp>
            <rdma>N/A</rdma>
          </ports>
          <pid>1900</pid>
        </node>
        <node>
          <hostname>yarrow</hostname>
          <path>/rhs/brick1/testvol</path>
          <peerid>dcfd0e0f-ad37-4447-801c-5c201a4da70f</peerid>
          <status>1</status>
          <port>49156</port>
          <ports>
            <tcp>49156</tcp>
            <rdma>N/A</rdma>
          </ports>
          <pid>11883</pid>
        </node>
        <node>
          <hostname>NFS Server</hostname>
          <path>localhost</path>
          <peerid>6aa15961-3ab6-4b6f-8412-8e084b7dfac7</peerid>
          <status>1</status>
          <port>2049</port>
          <ports>
            <tcp>2049</tcp>
            <rdma>N/A</rdma>
          </ports>
          <pid>1923</pid>
        </node>
        <node>
          <hostname>NFS Server</hostname>
          <path>yarrow</path>
          <peerid>dcfd0e0f-ad37-4447-801c-5c201a4da70f</peerid>
          <status>1</status>
          <port>2049</port>
          <ports>
            <tcp>2049</tcp>
            <rdma>N/A</rdma>
          </ports>
          <pid>11924</pid>
        </node>
        <tasks/>
      </volume>
    </volumes>
  </volStatus>
</cliOutput>
[root at zod ~]#

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list