Created attachment 789569 [details] remove-info-message.patch If using some options like -s one more info message is printed and logged in journal. rlRun "snmptable -c public -v 2c 127.0.0.1 dskTable" produces following log: :: [ INFO ] :: rlRun: command = 'snmptable -c public -v 2c 127.0.0.1 dskTable'; exitcode = 0; expected = 0 :: [ PASS ] :: Running 'snmptable -c public -v 2c 127.0.0.1 dskTable' (Expected 0, got 0) I don't think that the info message is somehow useful. If it is useful, it should be definitely a debug message. Attached patch completely remove the message.
(In reply to Dalibor Pospíšil from comment #0) > rlRun "snmptable -c public -v 2c 127.0.0.1 dskTable" this has to be rlRun -s "snmptable -c public -v 2c 127.0.0.1 dskTable"
fixed by https://git.fedorahosted.org/cgit/beakerlib.git/commit/?id=d82647458b18dadb0320f673327f5c125de67527
beakerlib-1.9-1.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/beakerlib-1.9-1.fc20
Package beakerlib-1.9-1.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing beakerlib-1.9-1.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-7442/beakerlib-1.9-1.fc20 then log in and leave karma (feedback).
beakerlib-1.9-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/beakerlib-1.9-2.fc20
Please consider the package fixing this bug available in Fedora stable repos once bz1116308 is closed and RHEL stable repos once bz1116317 is closed. Fixed in: beakerlib-1.9-2.fc19 beakerlib-1.9-2.fc20 beakerlib-1.9-2.fc21 beakerlib-1.9-3.el5 beakerlib-1.9-2.el6 beakerlib-1.9-2.el7
beakerlib-1.9-3.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/beakerlib-1.9-3.fc20
beakerlib-1.9-3.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.