Description of problem: Right now, we dump everything to stdout :-( On FAILURE dump reply.out to stderr On SUCCESS dump reply.out to stdout
# gluster-block create ... >file1.out 2>file2.err file1.out should capture only stdout, while file file2.err should capture stderr Basically, you need to simulate a Failure and a Success and see if the output msgs are dumped to stderr and stdout respectively.
(In reply to Prasanna Kumar Kalever from comment #8) > # gluster-block create ... >file1.out 2>file2.err > > file1.out should capture only stdout, while file file2.err should capture > stderr > > Basically, you need to simulate a Failure and a Success and see if the > output msgs are dumped to stderr and stdout respectively. Thanks for the steps Prasanna. Is there a way to validate this from oc or heketi side or do we need to go inside the gluster pod and verify with gluster-block create? Thanks, Neha
(In reply to Neha Berry from comment #9) > (In reply to Prasanna Kumar Kalever from comment #8) > > # gluster-block create ... >file1.out 2>file2.err > > > > file1.out should capture only stdout, while file file2.err should capture > > stderr > > > > Basically, you need to simulate a Failure and a Success and see if the > > output msgs are dumped to stderr and stdout respectively. > > Thanks for the steps Prasanna. > > Is there a way to validate this from oc or heketi side or do we need to go > inside the gluster pod and verify with gluster-block create? AFAIK, we have a way straight way to validate this in oc/heketi. Worth checking with cns-team though. Thanks! > > Thanks, > Neha
(In reply to Prasanna Kumar Kalever from comment #10) > (In reply to Neha Berry from comment #9) > > (In reply to Prasanna Kumar Kalever from comment #8) > > > # gluster-block create ... >file1.out 2>file2.err > > > > > > file1.out should capture only stdout, while file file2.err should capture > > > stderr > > > > > > Basically, you need to simulate a Failure and a Success and see if the > > > output msgs are dumped to stderr and stdout respectively. > > > > Thanks for the steps Prasanna. > > > > Is there a way to validate this from oc or heketi side or do we need to go > > inside the gluster pod and verify with gluster-block create? > > AFAIK, we have a way straight way to validate this in oc/heketi. Worth > checking with cns-team though. Thanks! > > > > > Thanks, > > Neha Putting a needinfo on Humble and Talur. The steps are verified in gluster pod and works as expected.
Answering in place of John/Talur/Humble, since we just discussed it: In order to verify this bug, you don't need to look at heketi, just test the gluster-block cli directly. After this fix, the consumer (heketi) can be improved (which is already done in the upstream). But not the concern of this BZ.
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:0285