Description of problem: heketi-cli topology info Error: Id not found Logs: [negroni] Started GET /volumes/1819834f5be2c3dce81b36e14ea440c0 [negroni] Completed 200 OK in 761.725µs [negroni] Started GET /nodes/410b2c68b6df188f88a69003cb8a757b [negroni] Completed 500 Internal Server Error in 6.36837ms 500 when fetching node information. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: Run volume creation and topology info concurrently Actual results: heketi-cli topology info Error: Id not found Expected results: Should list info Additional info: Upstream bug https://github.com/heketi/heketi/issues/382
Weird bug. Good find.
# heketi-cli node info 3f705907e431acef2cb44991f3e5103c Error: Id not found # heketi-cli device info c551a279f983e2ebd8a1bdb3b5478848 Error: Id not found don;t see this when fetching cluster info
*** Bug 1395042 has been marked as a duplicate of this bug. ***
A miniature version of this bug is documented at https://bugzilla.redhat.com/show_bug.cgi?id=1395042. That said, When Heketi is servicing requests like 'volume create', it fails to respond ( It returns "Err: Id not found) on requests like 'node info', 'device info' , however other requests for ex: 'cluster info' works. In 'topology info' (https://github.com/heketi/heketi/pull/285/) we internally call/use 'node info', so RC of this and https://bugzilla.redhat.com/show_bug.cgi?id=1395042 should be same. As this bug existed before bz#1395042, we closed the latest and tracking the fix in this bz.
Hi, In progress of RCA, We found that in when volume create is in progress, topology info, node info and device info is failing. During volume create, Brick entries are being added and device info throws "Id not found". If the added Brick Id has no value yet, this issue is hit. Node Info internally calling Device Info causes it to suffer too. As far as i see after discussing with Humble on provisioner bits, Issue affecting provisioner is only the bit where node info is failing. We are working towards brick addition not failing node info because node info is does not use brick information. -- Ashiq, Rtalur
Hi, I have a patch(PR https://github.com/heketi/heketi/pull/575) upstream under review which makes node info work even in volume create progression. -- Ashiq
https://github.com/heketi/heketi/pull/579 has been merged upstream to address this BZ.
(In reply to Mohamed Ashiq from comment #12) > Hi, > > I have a patch(PR https://github.com/heketi/heketi/pull/575) upstream under > review which makes node info work even in volume create progression. > > -- Ashiq This PR is deferred and PR(579) is decided as complete solution.
Verified as fixed in the latest version. Topology info and volume creation works concurrently now without any issues.
(In reply to Prasanth from comment #15) > Verified as fixed in the latest version. Topology info and volume creation > works concurrently now without any issues. Glad to hear DP works perfectly now . Thanks Prasanth for the verification!!!
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://rhn.redhat.com/errata/RHEA-2017-0148.html