Bug 1667797

Summary: pendingoperations total count is always zero in "heketi-cli db check" output
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nitin Goyal <nigoyal>
Component: heketiAssignee: John Mulligan <jmulligan>
Status: CLOSED ERRATA QA Contact: Nitin Goyal <nigoyal>
Severity: unspecified Docs Contact:
Priority: medium    
Version: ocs-3.11CC: akrishna, hchiramm, jmulligan, kramdoss, madam, rcyriac, rhs-bugs, rtalur, sankarshan, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: OCS 3.11.z Batch Update 2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: heketi-8.0.0-9.el7rhgs Doc Type: Bug Fix
Doc Text:
Previously, the "heketi-cli db check" diagnostic command failed to update the total number of pending operations. With this fix, the total pending operations count is reported correctly.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-27 04:55:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Nitin Goyal 2019-01-21 06:23:41 UTC
Description of problem:
Total count is not coming in pendingoperations section of "heketi-cli db check" command output.


Version-Release number of selected component (if applicable):
heketi-8.0.0-8.el7rhgs.x86_64

How reproducible:


Steps to Reproduce:
1. create volumes
# for i in {1..8}; do heketi-cli volume create --size 1 & done
2. check the output of "heketi-cli db check"
# heketi-cli db check

Actual results:
"pendingoperations": {
        "total": 0,
        "pending": 0,
        "ok": 8,
        "notok": 0,
        "inconsistencies": null
    },

Expected results:
total count should be there

Additional info:

Comment 2 Nitin Goyal 2019-01-21 06:24:29 UTC
# heketi-cli db check
{
    "clusters": {
        "total": 1,
        "pending": 0,
        "ok": 1,
        "notok": 0,
        "inconsistencies": null
    },
    "volumes": {
        "total": 9,
        "pending": 8,
        "ok": 8,
        "notok": 1,
        "inconsistencies": [
            "Volume 4963e5e6e0b617514935b7554e0bb958 mount hosts list([10.70.47.31 10.70.46.99 10.70.46.7]) is not same as list of all nodes of the cluster([48dac2c26112c558da055e2494101aa0 db67763501c3f6645d9a08a201f71fcc e3dd0582f004eada2f0017cf1138ea8f f19fdd1c652de2f1d6f4672829dffe02])"
        ]
    },
    "bricks": {
        "total": 27,
        "pending": 24,
        "ok": 27,
        "notok": 0,
        "inconsistencies": null
    },
    "nodes": {
        "total": 4,
        "pending": 0,
        "ok": 4,
        "notok": 0,
        "inconsistencies": null
    },
    "devices": {
        "total": 4,
        "pending": 0,
        "ok": 4,
        "notok": 0,
        "inconsistencies": null
    },
    "blockvolumes": {
        "total": 0,
        "pending": 0,
        "ok": 0,
        "notok": 0,
        "inconsistencies": null
    },
    "dbattributes": {
        "total": 0,
        "pending": 0,
        "ok": 0,
        "notok": 0,
        "inconsistencies": null
    },
    "pendingoperations": {
        "total": 0,
        "pending": 0,
        "ok": 8,
        "notok": 0,
        "inconsistencies": null
    },
    "totalinconsistencies": 1
}

Comment 3 John Mulligan 2019-01-21 14:35:18 UTC
I can confirm this issue. The "Total" counter is not being updated when looping over the pending ops while the "Ok" and "NotOk" counters are.

Comment 12 Raghavendra Talur 2019-02-13 22:16:46 UTC
upstream url https://github.com/heketi/heketi/pull/1505

Comment 15 Anjana KD 2019-03-15 02:54:46 UTC
Hi John,
I have updated the doc text. Kindly review.

Comment 16 John Mulligan 2019-03-15 15:01:14 UTC
I would not capitalize 'heketi-cli' since that is the command name rather than a reference to the Heketi project or Heketi system. Users who want to copy and paste the capitalized version would need to fix the command as well.

Comment 18 errata-xmlrpc 2019-03-27 04:55:35 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0663