+++ This bug was initially created as a clone of Bug #1019848 +++ Description of problem: hwcert-backend plan is stuck on 'Local Hardware Certification Test Server: ' Version-Release number of selected component (if applicable): hwcert-client-1.7.0-61.el7.noarch, in R60 as well How reproducible: 100% Steps to Reproduce: 1. installl hwcert-client 2. hwcert-backend plan 3. Enter, Enter, Enter, Enter, "Server", "none" Actual results: Hardware: empty empty empty OS: Maipo 7 Please verify the hardware product information: vendor:empty make:empty model:empty product-url: category (Desktop/Workstation|Laptop|Component/Peripheral|Server) Server What certification is this system being tested for? (new|existing|none) none response: none Local Hardware Certification Test Server: Expected results: planning is finished Additional info: --- Additional comment from Greg Nichols on 2013-10-16 09:45:03 EDT --- Is --mode set to "auto" ? if not, did you enter anything for the test server? --- Additional comment from Petr Beňas on 2013-10-16 10:06:21 EDT --- I have used no --mode or --server arguments, just "hwcert-backend plan". I was not asked for the server either. But it looks like when --auto is used, this problem does not happen. --- Additional comment from Greg Nichols on 2013-10-16 11:47:53 EDT --- I'm not clear on what the problem is then. You should be able to enter the server host name, or leave it blank, and continue. --- Additional comment from Petr Beňas on 2013-10-17 05:48:39 EDT --- I am terribly sorry, notabug. The hwcert is not stuck, but asking for the server. I was confused by wording of "Local Hardware Certification Test Server: " because it does not contain something like "Please enter" or a question mark. So my apologies, it is not a bug. --- Additional comment from Greg Nichols on 2013-10-17 09:13:42 EDT --- If it confused you, it's a bug. Let's leave it open - perhaps we could make the prompt a bit more clear with "Please enter". --- Additional comment from Dong Zhu on 2013-12-17 00:51:02 EST ---
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. http://rhn.redhat.com/errata/RHBA-2014-0532.html